Summary: | Konsole crashes on average once a day | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Harald Hvaal <metellius> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | martin.sandsmark |
Priority: | NOR | Keywords: | drkonqi |
Version: | 16.08.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Harald Hvaal
2016-11-04 10:51:07 UTC
Long shot, but a couple of commits recently fixed some signal connection stuff in TerminalDisplay (ec172b8f6b39a056326751f26ce81af664f0837f), could you try with the latest git master and see if it still happens? (In reply to Martin Sandsmark from comment #1) > Long shot, but a couple of commits recently fixed some signal connection > stuff in TerminalDisplay (ec172b8f6b39a056326751f26ce81af664f0837f), could > you try with the latest git master and see if it still happens? As mentioned in the report, I'm on KDE neon and updating regularly. Will that fix be in the next kde patch release? FYI, now running konsole compiled from master. Will report back if I have the crash again. I just hope drkonqi/apport will pick it up and get me a bt if it crashes; I'd prefer not having to run konsole in gdb for days :) If you're running under systemd journald should catch the coredump otherwise (run `coredumpctl` to see a list of coredumps it has captured, and to run gdb etc. on them). Thanks, I'll do that next time I see a crash. As for this bug, I haven't seen it since running from master for almost two weeks, so I'll assume it's fixed in the next release. Will reopen if I see it again. |