Bug 357631 - SystemSettings crashes when opening Desktop Effects for second time.
Summary: SystemSettings crashes when opening Desktop Effects for second time.
Status: RESOLVED DUPLICATE of bug 351839
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.5.4
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-06 21:14 UTC by Tomáš Jędrzejek
Modified: 2017-01-04 14:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
valgrind log (14.62 KB, text/plain)
2016-02-06 13:02 UTC, Elvis Angelaccio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomáš Jędrzejek 2016-01-06 21:14:37 UTC
When I open Desktop behavior configuration (translated to english) and then Desktop effects, everything is OK and I can see list of the effects. Then when I close the window with Desktop behavior configuration and open again it and going to Desktop effects whole SystemSettings crashes.
It is fully reproducible.

Reproducible: Always

Steps to Reproduce:
1. Select Desktop behavior configuratinon/Desktop Effects menu.
2. Close the window.
3. Open Desktop behavior configuratinon window again and select Desktop Effects

Actual Results:  
Crash

Expected Results:  
Do not crash

I can see this bug for long time with KDE 5.
Comment 1 Elvis Angelaccio 2016-02-06 13:01:28 UTC
I can reproduce it every time on Archlinux, both with Intel and proprietary Nvidia drivers.

However, I cannot reproduce it on a Tumbleweed virtual machine with Plasma 5.5.2 and KF 5.17.

On Arch I don't have debug symbols for the backtrace, so I'm only going to attach the valgrind log for now.
Comment 2 Elvis Angelaccio 2016-02-06 13:02:06 UTC
Created attachment 97048 [details]
valgrind log
Comment 3 Elvis Angelaccio 2016-02-06 14:20:55 UTC
Weird, the crash does not occur on a fully upgraded Fedora 23 (Intel graphics + plasma 5.5.4 + frameworks 5.18).
Sounds like an Archlinux-specific issue?
Comment 4 Christoph Feck 2017-01-04 14:50:21 UTC

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