Bug 155610

Summary:	plasma crashes when trying to add a custom wallpaper
Product:	[Unmaintained] plasma4	Reporter:	Craig Duquette <cduquette>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED FIXED
Severity:	crash	CC:	s.illes79
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Backtrace of the crash

Description Craig Duquette 2008-01-13 07:51:56 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

I'm using trunk built around 1am EST January 13th. When I select the open button after choosing a wallpaper in configure desktop plasma crashes.

The expected behavior would to have the background change to the custom image and be added to the dropdown list. I can select wallpapers from the existing list of default wallpapers without issues.

I took debugging symbols out so I can't generate a usable backtrace, but I'll recompile kdebase if it can't be reproduced.

Comment 1 Craig Duquette 2008-01-13 08:54:10 UTC

Created attachment 22982 [details]
Backtrace of the crash

Comment 2 Craig Duquette 2008-01-13 09:02:30 UTC

Alright going through the backtrace it seems to be a qt bug. If I select a wallpaper from the file dialog list and hit "Open" the wallpaper is added and things work; however I've been double clicking a files and that causes plasma to crash instead of actually selecting the wallpaper.

Comment 3 Riccardo Iaconelli 2008-01-13 10:08:42 UTC

SVN commit 760666 by ruphy:

Don't crash when double clicking on a file in the file dialog, and be safer anyways.
BUG: 155610


 M  +2 -1      backgrounddialog.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=760666

Comment 4 Riccardo Iaconelli 2008-02-02 23:20:30 UTC

*** Bug 156336 has been marked as a duplicate of this bug. ***

Comment 5 Chris Desjardins 2008-02-07 16:58:38 UTC

This is still occurring on KDE 4.0.1.

Comment 6 Sebastian Sauer 2008-03-08 21:15:14 UTC

bug #158784 deals with that issue in 4.0.2