[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
i have also this issue in 10.04. additionally if i disable screensaver and disable shutting down monitor if idle for some time i still get a black screen after some minutes of idleing. it seems some more powersaving options are totally ignored. anyhow, i will try later some of this mentioned tests and workarrounds to see if how they influence the behaviour. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
Just updated machine to 10.04 release. Indicator applet session still contains this bug. By selecting suspend option you lock your machine regardless of gnome-power-manager settings. MoarningSun workaround still works fine. ** Also affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-session (Ubuntu) Status: New = Confirmed ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed = Invalid -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
Hmmm, this bug seems to be fixed in 10.04. I just wish that there was an option in one of the system menu's. You shouldn't have to turn off this option via terminal. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
Thank you MoarningSun, for pointing out that there are different config files for different users when using gconf-editor. The lock problem was driving me crazy, since I always used 'gksudo gconf-editor'. Thus i think this is a good advice (most of the time): ** Don't use 'gksudo' in combination with 'gconf-editor' ** While it's quite logical to have different config files for different users, it's not that obvious. I guess a lot of unexpected behavior occurred, because the settings of the wrong user were changed. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
I too have the same problem on my Toshiba M500 running 9.10 with the latest updates ... but in reverse I am trying to make the system prompt for a password upon resume. i have tried the gconf-editor method to no avail. Both in sudo and without it makes absolutely what is checked in the editor ... the system still does NOT prompt upon resume. It used to to so, but since the latest updates it no longer does. Also another weird thing is that the suspend button combo (func+F3) does still suspend the machine BUT when I press the power button to resume (like it used to work) the computer resumes with a frozen cursor, and promptly goes back to sleep only a complete power down with the battery out solves this cycle. I am an ubuntu n00b so it is quite difficult for me to diagnose all this, but I have tried all suggested methods and so far have had no luck. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
Just did double check of MoarningSun observation results... it's absolutely correct: gnome-power-manager settings work just fine. Once disabled lock not appear when using either timeout suspend or keyboard hotkey. My workaround appears even simpler, I replaced standard applet with old Power Down... applet (look like red power button). It rises window with choice of suspend, log off and shut down options. Almost the same but works correctly (at least on my machine). -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
Thanks for the workaround, MoarningSun. It worked for me. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
I'm suffering from this issue as well. (running 32-bit Ubuntu 9.10) This far I've disabled the screen locking through gconf as both my own user and as root, and I also tried disabling it in /etc/default/acpi-support with no effect. This problem seems to only occur when suspending using the Indicator- Applet-Session applet, suspending with the Shut Down-applet or by closing the laptop lid works correctly. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
I'm having the same problem in 9.1 -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
This affects me to (in karmic). -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
** Summary changed: - Disabling the suspend and hibernate locks via gconf-editor in Intrepid Ibex doesn't do anything + Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included) -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
The bug is definitely present in Karmic. ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete = Confirmed -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255228] Re: Disabling the suspend and hibernate locks via gconf-editor doesn't do anything (from Intrepid to Karmic included)
Also none of the other methods that can be found on the forums work. See a collection of methods here: http://superuser.com/questions/71465/how-to-disable-screen-locking-after-sleep-on-ubuntu-9-10 (The first one is BS...) -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
