Bug#618313: similar problem, but only sometimes [ addendum ]
Hi, On Wed, 06.04.2011 at 10:00:05 +0200, Toni Mueller supp...@oeko.net wrote: after killing the screensaver using an SSH session, I see an alert box on my screen, saying this: Unable to start new display The name org.gnome.DisplayManager was not provided by any .service files. I found that maybe something else was going wrong. The keyboard produced the wrong output, which I could only fix by quitting Gnome and then starting it again (no reboot required, though). Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618313: similar problem, but only sometimes [ addendum ]
Hi, On Wed, 06.04.2011 at 09:56:17 +0200, Toni Mueller supp...@oeko.net wrote: Sometimes, the unlock fails despite my using the correct password, esp. after waking up from suspend-to-ram. Unfortunately, in this state, I can't even send after killing the screensaver using an SSH session, I see an alert box on my screen, saying this: Unable to start new display The name org.gnome.DisplayManager was not provided by any .service files. HTH Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
