Okay, this is specific to my using the lowlatency kernel /and/ having lowlatency-requiring apps running at the time of the user switch. If either of these conditions is not met, the switch goes through fine.
I'll have to change this bug out, and I understand that this makes the scope of this bug /much/ less expansive, but that's fine. It'd be wrong to leave a misleading bug around. ** Description changed: + Note: I am running a) a low-latency kernel and b) apps that are using + the low-latency facilities. This bug is specific to both of those + conditions. Doing the same thing in gnome2 does not produce this kind of + error, which means it's still a bug. + What I expected: ---- User A and user B both have accounts. User A logs on and leaves some programs running, then uses the fast-user-switch button to let user B do something. User B logs on and checks his email (or whatever), then logs back off. User A logs back on and continues working. What actually happened: ---- User A and user B both have accounts. User A logs on and leaves some programs running, then uses the fast-user-switch button to let user B do something. As soon as User B begins logging on (by clicking name on the logon manager), a GNOME "Program not responding" dialog (I believe it cites gdm-screen as the offending non-closing application) pops up: a) Clicking "Log out anyway" (or whatever its analog was on that screen; I'm writing from memory for obvious reasons) allows user B to log on and do work and suchlike, but user A loses all his work. b) Clicking "Lock screen" or "Cancel" leaves the login manager unresponsive, forcing User A to lose his work anyway because the only way to regain control is to power off and power back on. ---- Because I am using a netbook and, well, people often ask if they want to check their email, this is a fairly large problem. I'm not about to give them access to my own account, yet I don't want to lose my place in whatever I am doing either. I would go back to GNOME, because that fast user switch applet works fine, if it weren't for the fact that /that/ interface is just barely at the limit of what this teensy netbook can do. KDE's window manager is unusable on Intel integrated graphics. Note: I do have some custom repositories turned on, but the ones I use are written by and for KDE users so I seriously doubt that any of those settings/programs would interfere with the XFCE login/logout process. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xfswitch-plugin 0.0.1-1 ProcVersionSignature: Ubuntu 2.6.38-8.42+all1~lucid1-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency i686 Architecture: i386 Date: Mon Jun 27 14:24:22 2011 EcryptfsInUse: Yes InstallationMedia: Xubuntu 10.04.2 "Lucid Lynx" - Release i386 (20110214.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xfswitch-plugin ** Summary changed: - Attempting to fastswitch user does not work + fast-user-switch fails weirdly with lowlatency apps running -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802750 Title: fast-user-switch fails weirdly with lowlatency apps running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfswitch-plugin/+bug/802750/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
