Bug 407633 - kwin closed unexpectedly on login
Summary: kwin closed unexpectedly on login
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.15.5
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-17 08:05 UTC by Alan Prescott
Modified: 2019-05-20 07:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Backtrace (7.45 KB, text/plain)
2019-05-17 08:05 UTC, Alan Prescott
Details
qdbus output (3.43 KB, text/plain)
2019-05-17 11:09 UTC, Alan Prescott
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Prescott 2019-05-17 08:05:21 UTC
Created attachment 120125 [details]
Backtrace

SUMMARY
On login I get a message saying that kwin closed unexpectedly. If I manage to open any window it is missing window decorations.

STEPS TO REPRODUCE
1. Login
2. 
3. 

OBSERVED RESULT
Message 'kwin closed unexpectedly'

EXPECTED RESULT
Normal boot to desktop

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.12.8
KDE Frameworks Version: 5.45.0
Qt Version: 

ADDITIONAL INFORMATION
Happens on all users including new user created just to make sure that any existing user settings not causing a problem

Hardware: Lenovo Yoga with Thinkpad
Comment 1 Vlad Zahorodnii 2019-05-17 08:24:50 UTC
#6  KWin::Workspace::performWindowOperation (this=0x56026e96ce20, c=0x287, op=<optimized out>) at /usr/src/debug/kwin5-5.15.5-lp150.293.3.x86_64/useractions.cpp:1247

c=0x287 looks very suspicious.

Can you post output of `qdbus org.kde.KWin /KWin supportInformation`?
Comment 2 Vlad Zahorodnii 2019-05-17 08:34:00 UTC
Also, I don't get how we get from DecoratedClient::color to Workspace::performWindowOperation.

#6  KWin::Workspace::performWindowOperation (this=0x56026e96ce20, c=0x287, op=<optimized out>) at /usr/src/debug/kwin5-5.15.5-lp150.293.3.x86_64/useractions.cpp:1247
#7  0x00007f05801aa105 in KDecoration2::DecoratedClient::color (this=this@entry=0x56026ea2b7b0, group=group@entry=KDecoration2::ColorGroup::Active, role=role@entry=KDecoration2::ColorRole::TitleBar) at /usr/src/debug/libkdecoration2-5.12.5-lp150.1.2.x86_64/src/decoratedclient.cpp:100
Comment 3 Alan Prescott 2019-05-17 10:42:32 UTC
(In reply to Vlad Zagorodniy from comment #1)
> #6  KWin::Workspace::performWindowOperation (this=0x56026e96ce20, c=0x287,
> op=<optimized out>) at
> /usr/src/debug/kwin5-5.15.5-lp150.293.3.x86_64/useractions.cpp:1247
> 
> c=0x287 looks very suspicious.
> 
> Can you post output of `qdbus org.kde.KWin /KWin supportInformation`?

"Service 'org.kde.KWin does not exist"
Comment 4 Alan Prescott 2019-05-17 11:09:01 UTC
Created attachment 120129 [details]
qdbus output

output of `qdbus org.kde.KWin /KWin supportInformation`
Comment 5 Alan Prescott 2019-05-17 11:13:49 UTC
Comment on attachment 120129 [details]
qdbus output

Sorry these responses are a bit of a mess but I'm getting confused about how this bug reporting site works.

I managed to get into system settings for this user and set up to start with a new session to get this output.
Comment 6 Vlad Zahorodnii 2019-05-17 12:07:51 UTC
Do you use stock KWin? without custom patches, etc
Comment 7 Alan Prescott 2019-05-17 16:29:08 UTC
(In reply to Vlad Zagorodniy from comment #6)
> Do you use stock KWin? without custom patches, etc

Straight from the openSUSE Leap 15.0 packages.

Looking at my main WS with openSUSE 15.0 and same repositories I see:-
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.3

tried zypper dup --allow-vendor-change
and now get:-
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.3
on the yoga laptop.

Kwin now appears to be Ok - window decorations and everything :-). So it looks like I somehow ended up with a set of mis-matched versions of plama/kwin/frameworks etc. during the install, despite zypper up, zypper dup.
Comment 8 Alan Prescott 2019-05-17 16:59:48 UTC
Thanks for your time - shame it took me so long to find out what I'd gone wrong, though how I did it I've no idea.
Comment 9 Vlad Zahorodnii 2019-05-20 07:38:32 UTC
No problem.