| Summary: | Cauldron Xfce on laptop seizes up after screenlocker executes | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Len Lawrence <tarazed25> |
| Component: | RPM Packages | Assignee: | Jani Välimaa <jani.valimaa> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
Last 80 lines of the current journal file
Install log for Xfce Live |
||
|
Description
Len Lawrence
2020-06-05 00:01:38 CEST
Created attachment 11678 [details]
Last 80 lines of the current journal file
There was no report.bug.xz in /root/drakx but there was an installer.log which I shall copied across the network. Shall attach it here. Created attachment 11679 [details]
Install log for Xfce Live
There does not seem to be much of interest in that file with respect to this bug.
Installed Xfce from Live session on an Alienware desktop machine and rebooted, set up user data and allowed screenlocker to start. It responded immediately when password was typed. No problems at all. The next step is re-install on laptop and check again. Re-installed Xfce from live session on Aorus laptop. Noted a failure at the setting up sources stage on first login. This happened before but I had forgotten about it. All hdlists downloaded except core release, which had to be added later. The first time lockout occurred the session resumed on unlock but on subsequent occasions it failed. Had to perform cold reboot - the unlocker had intercepted CtrlAltF2 and presented askpass again. Installed Xfce again, this time via the boot menu. No longer any failure message during downloading of hdlists. Mixed results with screenlocking. It occasionally failed to unlock but most of the time was successful. Disabled screenlocking eventually. My feeling is that the cause of this bug is not going to be found. It is too erratic and so far has affected only this laptop amongst all the hardware that QA has tested. Agree to WONTFIX. Can somebody set that? Mageia 8, "Here we go"! This looks like yet another occurrence of bug 25008, bug 25066, bug 25445, bug 26692; but of course may not be the same. In this case, 64-bit for the first time (all the others are for Xfce on 32-bit). From https://bugs.mageia.org/show_bug.cgi?id=26692#c1 : > This looks like yet another duplicate of bug 25008, which is enormously long > & confused. See especially https://bugs.mageia.org/show_bug.cgi?id=25008#c33 edited below: > The main points were: > - having more than 1 screensaver running. To investigate this, do: > $ ps ax | grep saver > Disable every screensaver you can find! Please report back if you had > multiple screensavers, and whether getting rid of them solves your problem. and say whether you think this bug is the same as the others. Also, if you can stop the problem by reducing to <=1 screensaver, please reduce the severity (In reply to Len Lawrence from comment #7) > Agree to WONTFIX. Can somebody set that? A bit premature... CC:
(none) =>
lewyssmith @Lewis: comment 8. You are quite right; there were two screensavers in operation. One was for Mate, which is the user's preferred DE so there is a Mate profile in there. The Xfce screensaver kicks in but after the password it must yield to the Mate version, which explains the different appearance. Killed the Mate screensaver and awaited developments. So far the Xfce screen has unlocked successfully three times. Problem solved. What status do we give this bug now? Thanks Lewis. And a rider. To permanently fix this problem the Mate profile needs to be adjusted to permanently disable its screensaver. Shall look into that later. Second thoughts about this. Comment 10 should be ignored. There is only one screensaver listed in the Xfce Live manifest so on an Xfce only system others such as mate-screensaver must have been introduced by user action I would think. That leaves the question "why are two (or more) running?". Perhaps this has something to do with wild-cards? Assigning this to you as our 'desktop' man, and Xfce, Jani. But if you think this wrong, please re-assign it where you think best. This problem of losing the system after screensaver/locker under Xfce due to multiple screensavers running has plagued us for ages. Assignee:
bugsquad =>
jani.valimaa |