Version: (using KDE 3.0.4) Installed from: compiled sources Compiler: gcc version 2.95.4 20020320 [FreeBSD] OS: FreeBSD (i386) release 4.7-STABLE 1. X crashed in my absence. 2. restart X OK 3. 4 desktops, each with one konsole window OK 4. But unable to start a new konsole window from panel or command line. 5. In both cases a window 'Konsole-The KDE Crash Handler' pops up. 6. Backtrace shows: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x28dfe9bc in _thread_sys_poll () from /usr/lib/libc_r.so.4 #0 0x28dfe9bc in _thread_sys_poll () from /usr/lib/libc_r.so.4 #1 0x28dfddb8 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.4 #2 0x28dfd6cf in _thread_kern_scheduler () from /usr/lib/libc_r.so.4 #3 0x0 in ?? () 7. Output in case of command line: algol {wei} ~ > which konsole /usr/local/bin/konsole algol {wei} ~ > /usr/local/bin/konsole& [1] 432 algol {wei} ~ > Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". QSettings::sync: filename is null/empty konsole: chownpty failed for device /dev/ptypc::/dev/ttypc. : This means the session can be eavesdroped. : Make sure konsole_grantpty is installed in : /usr/local/bin/ and setuid root. KCrash: crashing.... crashRecursionCounter = 2 KCrash: Application Name = konsole path = <unknown> pid = 432 Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". QSettings::sync: filename is null/empty [1] Killed /usr/local/bin/konsole algol {wei} ~ > 8. konsole_grantpty installed in /usr/local/bin and setuid root: OK Thanks for help Harald
Is that reproducible (after reboot)?
Yes, it is reproducible after reboot. It is a very solid bug. In fact, I've abandoned KDE since then and switched over to GNOME. I (obviously) did not *want* to re-install KDE without knowing the cause of the bug. I will certainly try KDE again in the future, because I really liked it.
Reinstallation will likely not help - this is not MS Windows. Try to move ~/.kde away or if it works for a new created user.
I just tried both ways. Same konsole crash each time with same backtrace as shown above in item 6.
This is konsole's way of complaining that no ptys can be written by you as a user. Because of a (long standing and very hard to track down) bug in the konsole_grantpty code, konsole_grantpty doesn't actually run or reassign permissions to the pty. A basic fix, on a _single_user_ system where you trust the security, is to (as root) * Add your normal user account to a group, say ttys * chgrp ttys /dev/pty* * chmod 660 /dev/pty* Alternatively, you could just chown 666 /dev/pty*, but this is a hack. If you search the archives of kde-freebsd at https://lists.csociety.org/pipermail/kde-freebsd/ you may find other threads (by me) about hunting that bug.
This does not work for me. The group of /dev/pty* has always been wheel, the mode has always been 666, I have always been in group wheel.
OK, so the crash isn't directly related to the konsole_grantpty message. Without a decent backtrace (ie. a compiled version with debugging symbols, which means recompiling the ports with different flags which I don't remember but which #kde-freebsd could tell you on IRC) this is impossible to track down. I _do_ remember that there was a code path in konsole where a function returned NULL on BSD that _couldn't_ do so on Linux, leading to a NULL pointer dereference - but normally that path wasn't reached anyway because of other konsole bugs.
It's been a long time; I don't know if we can bring Harald back into the fold. In any case, HEAD (3.2, upcoming) is most likely fixed because of the improved konsole_grantpty there.
Thank you, Adriaan. Sure,I shall soon retry KDE on a new and faster box than my actual one where compiling is often awfully slow.