Bug 18957 - KWin (kwin_x11), signal: Segmentation fault
Summary: KWin (kwin_x11), signal: Segmentation fault
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-16 11:08 CEST by Bjarne Thomsen
Modified: 2017-03-15 17:16 CET (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Report from application (7.04 KB, text/plain)
2016-07-16 11:08 CEST, Bjarne Thomsen 		Details
kwin_x11 crash (7.35 KB, text/plain)
2016-07-24 14:35 CEST, Ãlo Parri 		Details
kwin_x11 crash with line numbers (9.43 KB, text/plain)
2016-07-25 18:42 CEST, Ãlo Parri 		Details
Trace-back with debuginfo, also for glibc (7.96 KB, text/plain)
2016-07-26 22:48 CEST, Bjarne Thomsen 		Details
KCrash with debuginfo for Qt5 (8.44 KB, text/plain)
2016-07-28 10:17 CEST, Bjarne Thomsen 		Details
gdb backtrace after running gwenview from the command line (23.51 KB, text/plain)
2016-08-30 23:05 CEST, Shlomi Fish 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bjarne Thomsen 2016-07-16 11:08:58 CEST 
Created attachment 8185 [details]
Report from application

It happened when I entered MCC. The same thing happened on another
system running an updated mga6.
Marja Van Waes 2016-07-16 17:46:25 CEST

CC: (none) => marja11
Assignee: bugsquad => mageia

Comment 1 Ãlo Parri 2016-07-24 14:35:30 CEST 
Created attachment 8248 [details]
kwin_x11 crash

CC: (none) => yltsparri

Comment 2 Ãlo Parri 2016-07-24 14:38:07 CEST 
Could be same bug.
New window opening sometimes crashes kwin_x11
Comment 3 Bjarne Thomsen 2016-07-25 10:02:34 CEST 
It happened again this morning when I updated using the MCC
Comment 4 Nicolas Lécureuil 2016-07-25 10:15:07 CEST 
please install debuginfo packages and paste a new backtrace
Comment 5 Bjarne Thomsen 2016-07-25 16:38:12 CEST 
I tried all debuginfo packages but I am running out of space.
Which packages should be installed?
Comment 6 Ãlo Parri 2016-07-25 18:42:25 CEST 
Created attachment 8261 [details]
kwin_x11 crash with line numbers

Installed -debuginfo packages with qt, kwin, plasma in thire names.
Is more needed?

For me crash happens almost always after desktop loads and i start konsole and chromium browser.
Comment 7 Bjarne Thomsen 2016-07-26 22:48:17 CEST 
Created attachment 8262 [details]
Trace-back with debuginfo, also for glibc

I installed debuginfo for kwin and all packages with plasma in their names.
Plus glibc-debuginfo.
Comment 8 Nicolas Lécureuil 2016-07-26 22:52:15 CEST 
you miss debug packages related to /lib64/libQt5Qml.so.5
Comment 9 Bjarne Thomsen 2016-07-27 00:02:05 CEST 
There are no debug packages related to the lib64qt5* packages.
Actually, I have not found a single debug package related to lib* packages.
I have only found debuginfo for big collections of libraries like glibc.
I have no idea where to find debuginfo for /lib64/libQt5Qml.so.5.
Comment 10 Rémi Verschelde 2016-07-27 08:18:32 CEST 
I think KCrash has a tab where it gives you the command to install the missing debuginfo. Finding them all manually is difficult, but typically the debugger can list them.

For Qt5Qml, the package is "qtdeclarative5-debuginfo" (I know, you couldn't have guessed that :D).
Comment 11 Bjarne Thomsen 2016-07-28 10:17:42 CEST 
Created attachment 8270 [details]
KCrash with debuginfo for Qt5

Here we go again. I hope all deguginfos are included this time.
Samuel Verschelde 2016-08-25 16:24:34 CEST

Assignee: mageia => kde

Comment 12 Shlomi Fish 2016-08-30 23:05:13 CEST 
Created attachment 8383 [details]
gdb backtrace after running gwenview from the command line

CC: (none) => shlomif

Comment 13 Nicolas Lécureuil 2017-03-15 16:04:10 CET 
is it still valid on current cauldron ?

CC: (none) => mageia

Comment 14 Bjarne Thomsen 2017-03-15 17:12:51 CET 
No. It has worked for a long time without a crash.
Comment 15 Rémi Verschelde 2017-03-15 17:16:47 CET 
Feel free to close it then as FIXED. (doing it now)

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.