I'm no longer able to reproduce this with the current nested-login
system.
** Changed in: gdm (Ubuntu)
Status: Incomplete = Fix Released
--
login in nested window dies changing workspace
https://bugs.launchpad.net/bugs/73931
You received this bug notification because you are a member of
As I said, the wish is already granted in the current default AFAICT.
Is there anything left to do before closing this bug?
** Changed in: gdm (Ubuntu)
Status: New = Incomplete
--
login in nested window dies changing workspace
https://bugs.launchpad.net/bugs/73931
You received this bug
Reassigning to gdm as a wishlist item to switch from xnest to xephyr.
I believe that is already the default. xephyr starts for me, not xnest.
I have both installed. They are alternatively RECOMMENDS.
--
login in nested window dies changing workspace
https://bugs.launchpad.net/bugs/73931
You
Yes, xephyr is to be preferred over xnest these days, since xnest
doesn't support as many of the newer extensions. I think xnest may not
be as well supported upstream anymore.
Reassigning to gdm as a wishlist item to switch from xnest to xephyr.
** Changed in: gdm (Ubuntu)
Sourcepackagename:
I'm just doing Xnest :1. It happens with gdmflexiserver but I'm 90%
sure it also happened when I directly runned Xnest. Of course, it
doesn't always happen :-)
--
login in nested window dies changing workspace
https://launchpad.net/bugs/73931
--
desktop-bugs mailing list
I'm also affected by this bug. It's not a gdm bug, though it's probably
a xnest bug: it also happens if you run xnest from the command line...
--
login in nested window dies changing workspace
https://launchpad.net/bugs/73931
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Vincent, how do you start xnest (what parameters do you use)? I've
noticed that problem with gdmflexiserver several time but I didn't
manage to crash xnest when I tried some time ago (by starting
gdmflexiserver xnest and xnest on a workspace the bug happened only to
the gdmflexiserver window)
--
Thanks for your bug report. I can't reproduce this as all. Which version
of Ubuntu and gdm do you use? Do you get anything interesting in one of
the users' ~/.xsession-errors?
** Changed in: gdm (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs
This is Edgy with all updates.
The xsession-errors shows some regular looking startup messages, then a
few alsa errors about not being able to find a device, then it just
seems like the server died.
ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
The application 'gnome-session'
