Summary: | Plasma crashed after connecting to an OpenVPN | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | pedron.alexandre |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | CLOSED DUPLICATE | ||
Severity: | crash | CC: | gb0101010101, gnu4ever, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.5.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | DrKonqi report (Aug. 4th 2018) |
Description
pedron.alexandre
2017-10-09 10:23:34 UTC
*** This bug has been marked as a duplicate of bug 346118 *** *** Bug 386092 has been marked as a duplicate of this bug. *** Created attachment 114297 [details] DrKonqi report (Aug. 4th 2018) Reopening this bug to let everyone know it's NOT solved. Despite of its previous status ("RESOLVED DUPLICATE of bug 346118" - I highly doubt it's a duplicate). Your backtrace clearly starts with: Application: plasmashell (5.5.5) and then I spent time reading further to see the line it refers to 566 is definitely changed and it isn't calling QAIM::dataChanged. Maybe this isn't fixed, but that backtrace only shows that old versions before the supposed fix unsurprisngly don't have the supposed fix. Thanks for your prompt reply David. It's too technical for me (I didn't get that part: "the line it refers to 566 is definitely changed and it isn't calling QAIM::dataChanged.") but never mind, at least I prefer a CLOSED status than a RESOLVED one, since I'm facing that bug every day :) So assuming Plasma 5.5.5 stopped being maintained a long time ago (funny for a Kubuntu LTS release btw), no chance there will ever be a fix, right? From a KDE POV, we don't control what Kubuntu put in their LTS. Our first LTS was Plasma 5.8. There is the option of asking Kubuntu to backport the supposed fix. I know KDE and Kubuntu teams are separate ones. Now, if Plasma 5.8 was the very first LTS, I understand there was no better solution at the time for the Kubuntu team than Plasma 5.5 (thanks for the explanation). Getting in touch with the Kubuntu team could be an option, but considering the support of Kubuntu 16.04 will end in April 2019 (9 months from now), I guess the wisest option will be to upgrade to Kubuntu 18.04 when possible :) Better concentrate on 18.04 bugs than backport an uncertain fix for a very short duration... |