Summary: | Plasma Desktop Shell (kdeinit4), Segmentation fault at startup | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | b.o.kenworm |
Component: | plasmoid | Assignee: | marble-bugs |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | nienhueser, plddev, shentey |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
b.o.kenworm
2011-01-08 13:13:29 UTC
[Comment from a bug triager] - Are your "marble" (world map) related packages updated ? Regards On Saturday 08 January 2011 17:28:24 Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=262515
>
>
> Dario Andres <andresbajotierra@gmail.com> changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
> - CC| |saschpe@gmx.de
> Component|general |wallpaper-marble
> AssignedTo|plasma-bugs@kde.org |gladhorn@kde.org
>
> --- Comment #1 from Dario Andres <andresbajotierra gmail com> 2011-01-08
> 17:28:22 --- [Comment from a bug triager]
> - Are your "marble" (world map) related packages updated ?
> Regards
Yes shure. I wouldn't think of bothering you guys otherwise.
Herman
Looks suspiciously like this bug: https://bugzilla.novell.com/show_bug.cgi?id=662861 and the workaround has helped me too: After removing the existing ~/.kde4/share/config/plasma* files, plasma-desktop works again. *** Bug 263327 has been marked as a duplicate of this bug. *** The reason for the crash is the worldclock plasmoid which somehow tries to access an invalid image pixel (y=-1). There doesn't seem to be any range checking happening before accessing the lookup table, therefore a segmentation fault occurs. Removing plasma config files is a possible workaround because in the standard configuration there is no worldclock plasmoid. Once you'd add it again, plasma will (likely) crash again. Given the number of bugs reported against the plasmoid and it being without a maintainer for quite some time now I wonder if we should disable it for the 4.6 release. *** This bug has been marked as a duplicate of bug 205893 *** |