[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 list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 settings. The Indicator-Applet-Session completely bypasses the gnome-power-manager according to bug 501252 so it's logical the gconf setting has no effect. I suspect the same applies for Gnome- Do. Workarounds that have worked for me are: - disable screen lock altogether in gconf-editor desktop gnome lockdown - addressing to devicekit-power directly with the command: dbus-send --print-reply --system --dest=org.freedesktop.DeviceKit.Power /org/freedesktop/DeviceKit/Power org.freedesktop.DeviceKit.Power.Suspend I've put this last line in a bash script that I can execute quickly with Gnome-Do, so I'm satisfied for the moment. -- Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included) https://bugs.launchpad.net/bugs/255228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 the suspend that locks the screen but something to with the 'default keyring' or something? I'm only an Ubuntu newbie actually so I'll leave it as is now, I just hope someone can have a look in to this or explain some more what's going on.. -- Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included) https://bugs.launchpad.net/bugs/255228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 here:) When I used the suggested command (sudo gconf-editor) I found the 2 boxes were still checked. Apparently the gconf settings are different for different users. Unchecking these 2 boxes again resulted in no screen lock after suspend! Strangely now only the gconf user setting affects locking, the root setting can be set to 'lock-yes'.. If I kill the gnome-power-manager and restart it as root, the gconf root setting does affects the presence of the screen lock after suspend. So for you it might have something to do with the per user setting, but I don't know if this is the case for everybody:) -- Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included) https://bugs.launchpad.net/bugs/255228 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
