Hm it only helped yesterday, now I get a different backtrace haning again. It looks like there is a glibc doublefree that raises SIGABRT, which tries to fork but hangs to do so. I'm a bit uncertain what could make a fork to actually hang? Besides that it is weird that there is a double free. This backtrace occured after a plain restart so nothing should be garbled.
** Attachment added: "gdb backtrace haning in signal handler" http://launchpadlibrarian.net/52348712/backtrace-20100723 -- gdm-session-worker crashes on logout when pam_mount is enabled https://bugs.launchpad.net/bugs/574329 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
