*** This bug is a duplicate of bug 454437 ***
https://bugs.launchpad.net/bugs/454437
Marking as dupplicate of bug 454437 since this gnome-session package has
not been updated in Karmic.
** This bug has been marked a duplicate of bug 454437
Karmic gdm loops back to login after login
--
** Tags added: regression-update
--
gnome-session doesn't always start
https://bugs.launchpad.net/bugs/477867
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in ubuntu.
--
desktop-bugs mailing list
Removing the regression-update tag - Karmic has had no gnome-session
updates since release. If this is a regression due to a stable update,
then it's got nothing to do with gnome-session
** Tags removed: regression-update
--
gnome-session doesn't always start
Maybe this is a regression-update in gdm (I started to get this bug
around 2009-11-07).
--
gnome-session doesn't always start
https://bugs.launchpad.net/bugs/477867
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in ubuntu.
I was wrong. After disabling encrypted swap and home folder, I can still
reproduce this bug.
** This bug is no longer a duplicate of bug 475936
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
** Description changed:
Binary
*** This bug is a duplicate of bug 475936 ***
https://bugs.launchpad.net/bugs/475936
This bug is actually caused by bug 475935 and that bug fixes this bug.
--
gnome-session doesn't always start if using encrypted swap
https://bugs.launchpad.net/bugs/477867
You received this bug notification
*** This bug is a duplicate of bug 475936 ***
https://bugs.launchpad.net/bugs/475936
Sorry I meant bug 475936.
** This bug has been marked a duplicate of bug 475936
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
--
I found this from /etc/gdm/:0-greeter.log
Ikkunointiohjelman varoitus: Buggy client sent a _NET_ACTIVE_WINDOW message
with a timestamp of 0 for 0x1600027
Ikkunointiohjelman varoitus: meta_window_activate called by a pager with a 0
timestamp; the pager needs to be fixed.
[...]
Ikkunointiohjelman
After testing, this bug actually happens to users having an encrypted
/home folder and for those having an unencrypted /home folder.
** Summary changed:
- gnome-session isn't started automatically for users using encrypted /home
folder
+ gnome-session doesn't always start if using encrypted