| Summary: | Mageia-6-rc-LiveDVD-Plasma-x86_64-DVD boots into a black screen | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Peter Hartmann <phartmann> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | kde, mageia, marja11, sysadmin-bugs |
| Version: | Cauldron | Keywords: | FOR_ERRATA6 |
| Target Milestone: | Mageia 6 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | Created Journal.log file with journalctl | ||
|
Description
Peter Hartmann
2017-06-10 09:53:37 CEST
Peter Hartmann
2017-06-10 09:54:51 CEST
Priority:
Normal =>
release_blocker If you wait for 5-10 minutes without touching anything, does the lock screen appear? Does clicking on the unlock button take you back to the black screen? If you press Ctrl-Alt-Backspace twice in quick succession, do you get the SDDM login screen? If so, log in as the Live user - do you get a working desktop? CC:
(none) =>
mageia P.S. Ctrl-Alt-L might take you directly to the lock screen without having to wait.
Marja Van Waes
2017-06-11 09:06:24 CEST
CC:
(none) =>
kde, marja11 Waiting does not help Pressing Ctrl-Alt-BS let the mouse cursor disappear. The screen remains black Ctrl-Alt-L works. But doing the suggested command does not help When the welcome-window appear, I am able to start apps In the meantime I had the possibility to test the DVD on a friend's laptop (HP DV6000). There I got a working screen. After getting to the lock screen with Ctrl-Alt-L, could you try the option to create a new session. First try to create a new Plasma session; if that doesn't work, try to create a new IceWM session. If one of those gets you to a working desktop, open a Konsole, type 'su' to become the root user, then 'journalctl -ab > journal.log', and attach the resulting journal.log file to this bug report. When using Ctrl-Alt-L there is no option to create a new session.
Only the following text appeared: As the text is in German I try to translate it.
The Screenlock is distrurbed and the session can not be freed. For freeing chage to a console (i.e. Ctrl-Alt-F2) login and enter the following command:
loginctl unlock-sessions
Change again to your running session (Ctrl-Alt-F1)
I am not able to start a Plasma nor IceWM session. But I can create a journal.log file which is attached.
Created attachment 9405 [details]
Created Journal.log file with journalctl
Thanks Peter. From the information you've provided, it seems this is a different bug to the intermittent one I'm seeing. To the KDE team, error messages in the journal suggest this is a graphics driver/hardware issue. Note this is a 16-year old Radeon device with limited support for 2D/3D acceleration - can we expect Plasma to run on it? Keywords:
NEEDINFO =>
(none) (In reply to Martin Whitaker from comment #7) > > To the KDE team, error messages in the journal suggest this is a graphics > driver/hardware issue. Note this is a 16-year old Radeon device with limited > support for 2D/3D acceleration - can we expect Plasma to run on it? Assigning to KDE team to increase the chance they'll see this question :-) Assignee:
bugsquad =>
kde During council meeting it was suggested to add "Don't use plasma on really old hardware" to the errata, and no one disagreed. So decreasing priority. Of course KDE team is free to increase it again ;) Priority:
release_blocker =>
Normal In the meantime I had the possibility to test the Live-DVD with ATI Radeon 9600 and 128 MB Memory. I am lucky to tell you that it works with this Adapter. But I don't know if this is due to the better GPU or the higher memory (my old adapter has only 64 MB memory). FYI: A test with Geforce 5600FX also fails. By the way I believe that it would be a good idea if the Mageia and/or KDE Teams would set the system requirements more precisely. We are sorry, but we no longer maintains Mageia 6. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to RESOLVED:OLD Status:
NEW =>
RESOLVED |