session logout after suspend

[Kaustubh]

In Kubuntu 9.04 Jaunty, my laptop lid down is set to suspend via guidance-power-manager. After I lid up, I am at the login screen, instead of the unlock screen dialog.

WORKAROUND: Disable the "Lock screen on resume" option in the power management settings.

[Daniele Depetrini (daniele-depetrini)]

I've exactly the same problem. Both suspend on disk and suspend on RAM will cause a (brutal) logout, so when the system resume I'll be brought to main login page.

[omni-vi (catcher)]

Hi

Me too !

I've got the same problem. Is there any information I can provide to help the people concernd fix this bug? It is verry annoying since the standard behaviour under KUbuntu is to go into stynby after 15 min of not using the pc

[Kaustubh (kaustubh-gadkari)]

I solved this problem by disabling the "Lock screen on resume" option in the power management settings.

[Daniele Depetrini (daniele-depetrini)]

The workaround to disable "Lock screen on resume" flag solved the issue for me too. Anyway this feature is very important for me, so I would consider this a workaround, not a real solution.

Any plan for a fix?

Thanks,

Daniele.

[aliencam (cameronk)]

I have the same problem in gnome.

[Dang Kang (kangdang)]

Does this problem still occurs after the latest update of Kubuntu 9.04?

[ojap (ojap-deactivatedaccount)]

WORKAROUND

Disable "Lock screen on resume."

[iainm (iain-mccracken)]

This bug affects Oneric (11.10) as well.

There is no option in the GUI to not lock on resume (that I've found, anyway), so there is no workaround for 11.10 unless there's something that can be edited or run from the command line.

I have confirmed that this forcibly kills user processes, as I have had LibreOffice gvim documents open with unsaved changes when I closed the lid and they all lost the data.

[iainm (iain-mccracken)]

Another observation:

If Thunderbird is running when I suspend the machine, or if I walk away long enough for the screen to lock, I get this problem.

Here's the version from dpkg-query.
Version: 7.0.1+build1+nobinonly-0ubuntu1

Issues (these happen sometimes but not always, and only when Thunderbird is running, it seems):
The Synaptics touchpad device vanishes on unlocking the screen.
The Intel HD Audio device vanishes on unlocking the screen.
All user programs killed and session logged out on resume from suspend.

The vanished devices require I log out and back in again. (Maybe a simple X server restart would do it, but I haven't looked around to find out how to do that -- ctrl-alt-backspace doesn't do it under Unity).

[Ryan Reich (ryan-reich)]

I get this bug in Oneiric. It is not triggered by *any* running application; in fact, I can reproduce it with excellent probability by:

1. Logging in.
2. Once login is complete, closing my laptop lid (which suspends).
3. Immediately waking up the laptop.
4. If that didn't cause the bug, suspend and try again.

The result is that when the screen lights up, I will see my desktop background (not the application switcher or title bar/system tray) for a moment, then the desktop will crash and I will end up back at the login screen in a second or two. It is not a *logout* so much as a *desktop crash*; all programs are terminated instantly.

[Ryan Reich (ryan-reich)]

I am attaching a portion of my kernel log from a recent desktop crash during resume. I want to point out particularly the events at the following times: [33221.164300] [33221.269629] [33222.874647], reflecting segfaults in bamfdaemon, compiz, and gnome-settings, all of them leading back to a location in libgdk-3.so.0.200.0. These are the only errors that show up in the course of the resume (in the kernel log, which is the only place I know where to look), so I assume they are relevant. They do *not* show up in a normal resume (next attachment).

[Ryan Reich (ryan-reich)]

I am also attaching a comparison "okay" log. There is nothing remarkable about it except that it does not mention bamfdaemon, compiz, or gnome-settings (in particular, they don't segfault).

[Ryan Reich (ryan-reich)]

This bug is almost certainly in libgdk-3.so.0.200.0. I have installed the repository http://ppa.launchpad.net/ricotz/testing/ubuntu (Gnome Shell) and upgraded to libgtk-3-0 version 3.3.5+git20111207.807a449f-0ubuntu1~11.10~ricotz0, and the bug seems to be fixed there.

[penalvch (penalvch)]

Kaustubh, thank you for reporting this and helping make Ubuntu better. Jaunty reached EOL on October 23, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[indigocat (indigocat)]

This problem persists on Ubuntu 16.04.

[penalvch (penalvch)]

indigocat, it will help immensely if you use the computer the problem is reproducible with, file a new report with Ubuntu by first ensuring the package xdiagnose is installed, click the Yes button for attaching additional debugging information after running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

[Simon (simsamsom)]

Hey Christopher, I've created a new version of this bug for 16.04

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1753884