| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
When looking up a bar for a particular stream, special-case the input
and output bars/streams, as they will not be added to the "bars"
hashtable (which is, as per comment, only for applications and the sound
events bar).
https://bugzilla.gnome.org/show_bug.cgi?id=738869
|
|
|
|
|
|
|
|
|
|
|
| |
This results in crashes when switching inputs or outputs, as other parts
of the code expect only application bars being added to that hashtable.
The bar was destroyed when switching outputs (as the stream is removed before
a new one being added) but with the bar pointing to freed memory.
This reverts commit 22fa7f1292922621ab6099019f810c2b0a621c99.
https://bugzilla.gnome.org/show_bug.cgi?id=746227
|
|
|
|
|
|
|
|
|
|
|
|
| |
The airbrush tool has only one button, and the button mapping combo box
does not work.
We should not bail out if the widget has been removed, that means that
the stylus does not support the second button.
Check upfront the number of buttons to know if the top button parameter
is available.
https://bugzilla.gnome.org/show_bug.cgi?id=746263
|
|
|
|
|
|
|
|
|
|
|
|
| |
We currently install two signal handlers for button-press-event and
selection-changed. As the former also calls the latter, the two interact
in non-obvious ways that can lead to two alerts being played at the same
time under certain circumstances.
Avoid this problem by setting activate-on-single-click on the tree view
and listening to the row-activated signal to drive previews and model
changes.
https://bugzilla.gnome.org/show_bug.cgi?id=671446
|
|
|
|
|
|
|
|
| |
Remove the NetworkManager version checking altogether. The code was made
to check for now very old versions of NetworkManager, and anything newer
than ancient should degrade gracefully if we support newer features.
https://bugzilla.gnome.org/show_bug.cgi?id=741661
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=741413
Conflicts:
panels/universal-access/uap.ui
|
|
|
|
|
|
|
|
| |
Since GOA is still using WebKit1, we need to set the environment
variable ourself. We can stop setting it once we port to WebKit2
because the network process will handle it for us.
https://bugzilla.gnome.org/show_bug.cgi?id=739960
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The active input and output streams aren't added through add_stream()
so they weren't being mapped to their respective volume bars,
resulting in updates to the volume through other means not being
reflected in our UI.
Moving the mapping to bar_set_stream() which is called for every
stream fixes the problem. Also, there's no value in having a
helper function to do a g_hash_table_insert() and not doing the same
for the respective g_hash_table_remove()s so remove it.
https://bugzilla.gnome.org/show_bug.cgi?id=738869
|
|
|
|
|
|
| |
Last patch refers to nm_device instead of the actual variable device.
https://bugzilla.gnome.org/show_bug.cgi?id=723643
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=723643
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By stopping watching for WM changes when leaving the shortcuts panel.
#0 reload_sections
#1 wm_window_event_filter
#2 gdk_event_apply_filters at gdkeventsource.c:81
#3 gdk_event_source_translate_event at gdkeventsource.c:195
#4 _gdk_x11_display_queue_events at gdkeventsource.c:338
#5 gdk_display_get_event at gdkdisplay.c:313
#10 g_main_context_iteration at gmain.c:3766
#11 g_application_run at gapplication.c:1623
See https://bugzilla.redhat.com/show_bug.cgi?id=1094480
https://bugzilla.gnome.org/show_bug.cgi?id=736117
Conflicts:
panels/keyboard/keyboard-shortcuts.c
|
|
|
|
|
|
|
| |
As we don't want to be doing that anymore if we're not in the keyboard
panel anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=736117
|
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=735352
Conflicts:
panels/datetime/cc-datetime-panel.c
|
|
|
|
|
|
| |
The code is meant to work with NetworkManager of version 0.9.0+ or 0.8.992+
https://bugzilla.gnome.org/show_bug.cgi?id=733309
|
|
|
|
|
|
|
|
|
|
|
| |
network-wireless-signal-excellent and network-cellular-signal-excellent
don't exist in non-symbolic variants anymore, so use the fallback
names instead.
https://bugzilla.gnome.org/show_bug.cgi?id=695480
Conflicts:
panels/network/panel-common.c
|
|
|
|
|
|
|
|
| |
The list store contained the wrong values.
Spotted by the.viclim@gmail.com
https://bugzilla.gnome.org/show_bug.cgi?id=728880
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=699712
|
| |
|
| |
|
|
|
|
|
|
| |
g_strcmp0() == 0, or g_str_equal(), not g_str_equal() == 0...
https://bugzilla.gnome.org/show_bug.cgi?id=727161
|
|
|
|
| |
In French, the singular form should be used for 0.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Team support was only added in the 0.9.9.x branch for the 0.9.10
stable release. It's not available in any releases (beta or stable
ones) yet.
https://bugzilla.gnome.org/show_bug.cgi?id=723769
Conflicts:
configure.ac
panels/network/connection-editor/net-connection-editor.c
|
|
|
|
|
|
|
| |
It appears that this has always been the intention of the code,
but the check was incomplete.
https://bugzilla.gnome.org/show_bug.cgi?id=724312
|
|
|
|
|
|
|
|
|
|
| |
g_warning() is for environment errors, not user errors. Not being
able to click OK is enough to understand that something is wrong,
and if not we should highlight the faulty setting, not spam the logs,
expecially in the middle of digitation. Keep a log anyway, for
debugging.
https://bugzilla.gnome.org/show_bug.cgi?id=724312
|
|
|
|
| |
It is 'Identität', not 'Idendität'.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=708286
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If the user knows what it is, it's likely they'll know the
English word for it. This also allows us to add support for it
even though we're in a string freeze.
|