Summary: | console crashed in background | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Marcin Gryszkalis <mg> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 16.08.1 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Marcin Gryszkalis
2016-11-12 21:00:12 UTC
Git commit 40b1f0e851c115e1a2df79e7ec4bc4fe726d9e43 by Martin T. H. Sandsmark. Committed on 20/11/2016 at 13:40. Pushed by sandsmark into branch 'master'. Only use foreground process info if valid getProcessInfo() returned _foregroundProcessInfo without checking the return value of updateForegroundProcessInfo() indicating whether _foregroundProcessInfo was non-existent or invalid. I think this might be the solution to a bunch of recent crash bugs, but not closing them as I can't test. Also skipping RB because it is a simple patch and RB is down from here. Related: bug 372620, bug 372619, bug 372593 M +1 -2 src/Session.cpp http://commits.kde.org/konsole/40b1f0e851c115e1a2df79e7ec4bc4fe726d9e43 Git commit d28afb6664459cf28d73d7617b74c49711ce7a86 by Kurt Hindenburg, on behalf of Martin T. H. Sandsmark. Committed on 24/11/2016 at 14:42. Pushed by hindenburg into branch 'Applications/16.12'. Only use foreground process info if valid getProcessInfo() returned _foregroundProcessInfo without checking the return value of updateForegroundProcessInfo() indicating whether _foregroundProcessInfo was non-existent or invalid. I think this might be the solution to a bunch of recent crash bugs, but not closing them as I can't test. Also skipping RB because it is a simple patch and RB is down from here. Related: bug 372620, bug 372619, bug 372593 (cherry picked from commit 40b1f0e851c115e1a2df79e7ec4bc4fe726d9e43) M +1 -2 src/Session.cpp https://commits.kde.org/konsole/d28afb6664459cf28d73d7617b74c49711ce7a86 Reopen if you can duplicate the issue in 19.08 - a lot has changed since 16.08 |