The wmii segfault I mentioned was indeed recorded in dmesg as wmii segfaulting. I didn't see anything extra in the terminal before wmii (and X) dumped me back to the command line as you did so perhaps I was experiencing a different issue caused by a similar problem. Since updating to tip fixed it though I'll leave it at that.
Thomas On Thu, Apr 23, 2009 at 04:36:57PM -0400, Robert C Corsaro wrote: > Kris Maglione wrote: >> On Thu, Apr 23, 2009 at 03:03:41PM -0400, Robert C Corsaro wrote: >> >>> I was just messing around. But generally things should segfault, right? >>> I only brought it up here because it's a seg fault and not a normal >>> error. >>> >> >> Well, no, they shouldn't segfault, but that has nothing to do with wmii. >> Presumably you're using GNU chmod, which seems to be what seg faulted. >> >> > Oh, I see what you mean. The segfault output is indicative of chmod > segfaulting, so maybe wmii didn't segfault but simply crashed. I took it > for granted since it quickly appeared and then wmii dies, killing my X > session. I certainly don't see the permission denied error as Thomas does. > I'll try tip. >
