Jonathan Thomas wrote: > Could you show the backtrace from the KDE crash handler please? > > ** Package changed: kdelibs (Ubuntu) => kde4libs (Ubuntu) > > ** Changed in: kde4libs (Ubuntu) > Status: New => Incomplete >
(I don't have a _reproducable_ crash, so for testing I've been triggering one with "kill -SIGSEGV"). Hmm, it works fine now. Confusing. Maybe KDE only picked up the dbg packages when I logged out or rebooted. Since it works for me now, I'm happy to close the bug. Do you think it's worth pursuing? I could have another go with the LiveCD, and experiment with installing the dbg packages from my apt cache. That would show whether it was necessary to log out or not. Obviously I couldn't test rebooting :-). My expectation is that installing the dbg packages should have an immediate effect. It should be possible since the debug symbols are only loaded when the crash happens. I think it makes sense from the user POV. Also it should make it easier to report crashes without having to worry about losing the state that causes the bug. Ta Alan -- KDE crash dialog does not produce useful backtraces even when dbg packages are installed https://bugs.launchpad.net/bugs/373142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/universe-bugs
