[Bug 1720745] Re: connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel

** Bug watch added: GNOME Bug Tracker #789231 https://bugzilla.gnome.org/show_bug.cgi?id=789231 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=789231 Importance: Unknown Status: Unknown -- You received this bug notification because you are a

[Bug 1720745] Re: connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel

** Tags added: artful ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720745 Title: connecting to a WPA-enterprise

[Bug 1720745] [NEW] connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel

Public bug reported: When selecting a WPA-ENTERPRISE Network for the first time, using gnome-shell "select network" popup, gnome-control-center is automatically started with the "Network" panel open. But in gnome 3.26's new control center this panel only lists Wired, Mobile Broadband, VPN

[Bug 1263499] Re: missing dependency: python-spice-client-gtk

*** This bug is a duplicate of bug 1268466 *** https://bugs.launchpad.net/bugs/1268466 ** Also affects: virt-viewer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1268466] Re: virt-manager does not include the python-spice-client-gtk dependency for Spice

this is ridiculous. Invalid? Whishlist? a functionality is broken (what if the virtualization host is a remote server? what should the user do, reboot all the vm in order to change them to vnc?) and you refuse to recognize it as something that should work. Well, PATCH virt-manager and add a

[Bug 1301765] Re: Need to use gstreamer1.0 dependencies

furthermore, since ffmpeg was purged from ubuntu, even gstreamer0.10-ffmpeg was removed from the repos when ubuntu decided to endorse libav instead. which is perfectly fine with me, but why the need to remove even gstreamer0.10-ffmpeg which did and still provides an INTERNAL ffmpeg

[Bug 1359564] Re: radiotray crashed with Attempt to unlock mutex that was not locked

thanks for your cooperation. i stumbled into this trying to help a forum user with radiotray problems (didn't play some radios because of dropped gstreamer0.10-ffmpeg package from ubuntu). after he manually patched and compiled it as I suggested, he started having this error. to exculpate

[Bug 1359564] Re: radiotray crashed with Attempt to unlock mutex that was not locked

I'm planning to submit this to debian, is this the correct way of doing so? ** Patch added: radiotray-debian.patch https://bugs.launchpad.net/ubuntu/+source/radiotray/+bug/1359564/+attachment/410/+files/radiotray-debian.patch -- You received this bug notification because you are a

[Bug 1359564] Re: radiotray crashed with Attempt to unlock mutex that was not locked

thanks for your feedback. so, avoiding that call appears to be a valid workaround, however the bug lies in libgtk2 (it seems to be a latent bug which emerged only with the new, stricted glib). someone should open a bug against it as it seems to affect any gtk application calling

[Bug 1359564] Re: radiotray crashed with Attempt to unlock mutex that was not locked

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359564 Title: radiotray crashed with Attempt to unlock mutex that was not locked To manage

[Bug 1359564] Re: radiotray crashed with Attempt to unlock mutex that was not locked

psensors ran in a similar problem, which appears to be a bug in GTK itself making it incompatible with glib = 2.41 (both from gnome...) https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1346299 it was solved by the packager by avoiding a call to the now deprecated gdk_threads_init which

[Bug 1359564] Re: radiotray crashed with Attempt to unlock mutex that was not locked

attaching a tentative patch. ** Patch added: tentative patch https://bugs.launchpad.net/ubuntu/+source/radiotray/+bug/1359564/+attachment/4191180/+files/SysTray.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.