Summary: | Segfault in PlasmaQuick::DialogPrivate::availableScreenGeometryForPosition | ||
---|---|---|---|
Product: | [Frameworks and Libraries] libplasma | Reporter: | Jan Kundrát <jkt> |
Component: | libplasmaquick | Assignee: | Marco Martin <notmart> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | edoubrayrie, jnelson-kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/plasma-framework/3f9109a2657a132879f29cc56471598a5f519b94 | Version Fixed In: | |
Sentry Crash Report: |
Description
Jan Kundrát
2015-03-15 10:11:57 UTC
I consider this behavior change in Qt quite unacceptable.. anyways, screens should be checked for null everywhere now I guess.. Well, Qt >= 5.0 && Qt < 5.5 would just crash a long time before an application got an opportunity to do so, so it's certainly a progress :). The upstream's rationale for returning null QScreens is at http://lists.qt-project.org/pipermail/development/2015-March/020614.html ; you should probably talk to them now if they screwed up. I have no idea what's a correct thing and what ain't. Feel free to Cc me on patches which look like they could fix these problems (or anything 5.5-related). I run Qt from 5.5 git now, so I'll be happy to report what is broken and what got fixed. *** Bug 345772 has been marked as a duplicate of this bug. *** Git commit 3f9109a2657a132879f29cc56471598a5f519b94 by Christoph Cullmann. Committed on 05/10/2015 at 14:59. Pushed by cullmann into branch 'master'. Check for nullptr screen to avoid crash REVIEW: 125528 M +4 -2 src/plasmaquick/dialog.cpp http://commits.kde.org/plasma-framework/3f9109a2657a132879f29cc56471598a5f519b94 *** Bug 354303 has been marked as a duplicate of this bug. *** |