Hey Anthony, Quoting Anthony Campbell (2012-05-12 15:47:15) > Yes, that's what I'm doing. Here is the output: > > killall $(pidof i3) > 4068: no process found Ugh, my mistake. I meant either "killall i3" or "kill $(pidof i3)".
> 4068 is the proces corresonding to i3 according to ps ax. Killall 4068 > gives the same message BUT kill 4068 locks up the machine! (Sorry, I > know this doesn't make sense.) OK. > You've probably got my last email, saying that the same thing is > reproducible in dwm and icewm, so it is not specific to i3. No, I didn’t get that mail. Can you please sent me the message ID and (if you have access to it) the corresponding log entry from your outgoing mailserver? > (Yes, I know I said icewm was OK, but that was if I bring up the menu and > use logout. If I do "kill" as above I get the same lockup in icewm.) Hm, judging from the source of icewm, the only thing it does different than i3 is that it kills all windows before doing exit(0). You could try "killall i3bar; killall i3" and see if that locks up your machine, too. > > Can you attach the contents of /var/log/Xorg.0.log after exiting in i3 and > > after exiting in icewm please? > > Sorry - I don't understand what you want here. I can: > > 1. Cause a lockup with Shift-Mod-e (or kill) in i3 and send the > Xorg.log.0 file. Yes, plesae do this. > 4. Exit icewm via the menu, in which case there is again no lockup. Yes, please do this, too (and send the logfile). Best regards, Michael PS: Please CC 672...@bugs.debian.org so that your full mails are in the bugreport. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
