tremby,
as i posted earlier with my experiences in kde, any workaround added in
/etc/gdm/PostSession/Default for Gnome is the same as adding an executable
script into the ~/.kde/shutdown folder in KDE. So you can use a killall on
logout workaround for the time being in KDE similarly as one can
One other interesting thing to note: At least on my machine here,
everytime I open the keytouch config gui and press OK, a new instance of
keytouchd spawns.
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You received this bug notification because you are a member of
don't have time to play around with this tonight, but i was poking in
/etc/X11/Xsession.d and saw that there were 2 different keytouchd_launch
files. my question is are there supposed to be 2 files launching
keytouchd at X startup? or is this causing multiple keytouchd processes
to spawn at X
I also upgraded Kubuntu 7.10 to 8.04.
I also tried removing ~/.keytouch2 and logging back in. When I went to logout
it worked properly. The next time I tried to log out it did not. I then
killed keytouchd, put my old ~/.keytouch2 back in place, and started keytouchd
back up and it logged
Same problem in Kubuntu Hardy. I do not have any seahorse-agent process
running, but I found that killing the keytouchd process itself allowed
logout/shutdown to continue. So at least for right now, I told KDE to
killall keytouchd when it logs out, and that seems to be working ok as a
temporary
Might be able to do it by adding the command to:
/etc/gdm/PostSession/Default
I really don't deal with gnome that much, but I read some people had other
gnome logout commands working by putting the commands in there.
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You
