on Thursday 23 June 2005 02:05, Alban browaeys wrote:
Hum i meant to stop dbus before starting kde (and before sleeping) . I
disabled dbus monthes ago though kded still starts.
I guess that after killing dbus, starting a new kde application should
restart kded without dbus (thohg i could not
This is a followup for your report:
http://bugs.debian.org/315433
Do you use a kernel patched with swspend2 or the vanilla
swsuspend (1) from standard kernel ?
Hardware accelerated drivers in X ? (proprietary or vanilla X
drivers)
If you use swsuspend 2 does it helps if you use its option to
on Thursday 23 June 2005 00:43, [EMAIL PROTECTED] wrote:
This is a followup for your report:
http://bugs.debian.org/315433
Do you use a kernel patched with swspend2 or the vanilla
swsuspend (1) from standard kernel ?
vanilla kernel with i2e-keywest patch
Le jeudi 23 juin 2005 à 01:52 +0200, Jorge Salamero a écrit :
Thank you for the informations. This at least close a few tracks.
i stop dbus wich also kills kded, i start kded manually and sleep the
computer, when i wake up the same proble, no message no, x display, frozen
Hum i meant to stop
4 matches
Mail list logo
