Bug#618313: similar problem, but only sometimes [ addendum ]

2011-04-10 Thread Toni Mueller
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

Bug#618313: similar problem, but only sometimes

2011-04-06 Thread Toni Mueller
Hi, I have this on my laptop: $ dpkg -l gnome-screensaver Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion

Bug#618313: similar problem, but only sometimes [ addendum ]

2011-04-06 Thread Toni Mueller
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