[Bug 455421] Re: rhythmbox crashed with SIGSEGV in g_object_set()

same problem here, reproducible by changing the volume, also on Karmic -- rhythmbox crashed with SIGSEGV in g_object_set() https://bugs.launchpad.net/bugs/455421 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing

[Bug 455421] Re: rhythmbox crashed with SIGSEGV in g_object_set()

same problem here, reproducible by changing the volume, also on Karmic -- rhythmbox crashed with SIGSEGV in g_object_set() https://bugs.launchpad.net/bugs/455421 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing

[Bug 455421] Re: rhythmbox crashed with SIGSEGV in g_object_set()

same problem here, reproducible by changing the volume, also on Karmic -- rhythmbox crashed with SIGSEGV in g_object_set() https://bugs.launchpad.net/bugs/455421 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing

[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)

It appears that these problems are indeed not caused by a bug in gnome- power-manager. In my case, the lock only persists when using the Indicator-Applet-Session or Gnome-Do to initiate the suspend. Suspending with the Shut Down-applet or the dedicated sleep key on my notebook follows the gconf

[Bug 454325] Re: (Karmic regression) Despite my wishes screen is locked on resume

please also have a look at bug 501252 and bug 255228 -- (Karmic regression) Despite my wishes screen is locked on resume https://bugs.launchpad.net/bugs/454325 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in

[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)

A little update about what I said earlier, the problem stilt isn't gone actually. After a restart there's most of the time still a lock after suspend. It seems to depend on if the wireless is active or not and if the sudo password was used in a terminal before going into suspend. So its not really

[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)

This problem affected me initially in 9.10, but not anymore. In my case I did: - open gconf-editor (no sudo / root) - navigate to /apps/gnome-power-manager/locks - disable lock_on_hibernate - disable lock_on_suspend After this the screen would still get locked after a suspend, so I googled to