Bug 985768 - i586: screenlocker fails to work
i586: screenlocker fails to work
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma)
Other Other
: P5 - None : Major (vote)
: ---
Assigned To: E-Mail List
E-mail List
Depends on:
Blocks: 984984
  Show dependency treegraph
Reported: 2016-06-20 21:40 UTC by Dominique Leuenberger
Modified: 2016-08-08 15:41 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Dominique Leuenberger 2016-06-20 21:40:31 UTC
Detected by openQA: https://openqa.opensuse.org/tests/213533#step/first_boot/4

Sfreenlocker is broken.

The same issue was already seen in staging on x86_64, but that had been fixed by a patch. Apparently it did not solve i586 (which is not built/tested in stagings though)
Comment 1 Luca Beltrame 2016-06-20 22:00:40 UTC
There needs to be a backtrace in order to understand what's going on in the screensaver. Unfortunately, I don't have i586 hardware to test this with.

If someone can test the snapshot, even in a VM, the easiest way would be

/usr/lib/libexec/kscreenlocker_greet --testing

and see if it crashes. If it does, it needs to be run through gdb to get the bt.
Comment 2 Fabian Vogt 2016-06-21 08:48:02 UTC
The crash can be easily reproduced by running the screenlocker with QV4_MM_AGGRESSIVE_GC=1 set. It produces the following backtrace: 


This also breaks plasmashell with a similiar backtrace (valgrind):

Comment 3 Bernhard Wiedemann 2016-06-21 12:00:42 UTC
This is an autogenerated message for OBS integration:
This bug (985768) was mentioned in
https://build.opensuse.org/request/show/403818 Factory / libqt5-qtdeclarative
Comment 4 Bernhard Wiedemann 2016-06-21 14:00:33 UTC
This is an autogenerated message for OBS integration:
This bug (985768) was mentioned in
https://build.opensuse.org/request/show/403815 Factory / libqt5-qtdeclarative
Comment 5 Dominique Leuenberger 2016-08-08 15:41:52 UTC
this had been fixed in TW in time - RESOLVED