Bug 349387

Summary:	Selecting the Open File button for "Play Sounds" option more than once causes application to freeze
Product:	[Applications] systemsettings	Reporter:	Marcus Harrison <marcus>
Component:	kcm_notify	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	budimanjojo, kde, saxonbeta
Priority:	NOR
Version First Reported In:	5.3.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Marcus Harrison 2015-06-19 16:09:03 UTC

When changing notifications, changing one notification with the "Play a sound" option enabled by clicking the "Open file dialogue" button opens the file dialogue and allows you to navigate as expected. On my system, the dialogue was configured to show the sidebar and automatically play audio files by default.

After selecting the file I wanted and clicking "OK" or clicking on the desired file correctly sets the file to be the notification sound.

Then, when selecting a different notification with the "Play a sound" option enabled, and when clicking the "Open file dialogue" button to change the sound, a loading wheel appears for a brief period before ending without opening the file dialogue. The dialogue never opens no matter how long I wait.

Resizing the KCM window causes it to repaint correctly, but otherwise, clicking on UI widgets such as buttons or text areas does nothing, nor does using the standard window manager method of closing the window. I was forced to kill the application in order to make it close.

Reproducible: Always

Comment 1 Saxonbeta 2015-07-27 20:17:05 UTC

This bug is still present in systemsettings 5.3.2

Comment 2 David Edmundson 2015-09-26 10:55:04 UTC

Confirmed.

Comment 3 David Edmundson 2015-09-26 16:46:39 UTC

Thanks.

There's a review in the works, should be fixed soon.

*** This bug has been marked as a duplicate of bug 350758 ***