Bug 22761 - Upgrade to mageia-6/plasma-5 : black screen on desktop
Summary: Upgrade to mageia-6/plasma-5 : black screen on desktop
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks: 21340
  Show dependency treegraph
 
Reported: 2018-03-13 21:53 CET by Christian C
Modified: 2020-08-16 17:41 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
/etc/X11/xorg.conf (2.49 KB, text/plain)
2018-04-11 08:06 CEST, Christian C
Details

Description Christian C 2018-03-13 21:53:30 CET
Description of problem:

I upgraded to mageia-6 from mageia-5 with the following commands :
urpmi.removemedia -a
urpmi.addmedia --distrib --mirrorlist http://mirrors.mageia.org/api/mageia.6.x86_64.list
urpmi --replacefiles --auto-update --auto
I had no problem.

But when I ran my user session, I got a few error windows about gpg configuration and clicking the desktop switched off the screen.
To summarize, when I clic :
- the desktop background : the screen switch off
- the cauldron to launch a program : the screen switch off
- a window opened on the desktop : the screen switch on
- an icon in the task bar : the screen switch on and the program starts

I tried replacing the graphical driver from nouveau to nvidia but that doesn't change anything.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. run a plasma session from the session manager
2.
3.
Comment 1 Marja Van Waes 2018-03-14 07:40:27 CET
The message about gpg configuration might be related to https://wiki.mageia.org/en/Mageia_6_Release_Notes#gnupg_removal_of_the_secret_keyring

You shouldn't get a black screen, though!

Assigning to the KDE maintainers.

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

Comment 2 Christian C 2018-03-14 08:13:26 CET
The message about gpg configuration is not a problem. They say how to fix it.

But this strange behaviour of the plasma desktop !
I tried xfce that works fine but kmail. It can't stay alive more than a few minutes. Even resizing the window makes it crash.
Some people say that it's an installation problem but I had no problem during the installation.

So I have no other choice than getting back to mageia-5 for the moment.
My question is : is it still maintained ? And for how long ?
Comment 3 Marja Van Waes 2018-03-14 09:31:12 CET
(In reply to Christian CHEVALIER from comment #2)

> 
> So I have no other choice than getting back to mageia-5 for the moment.
> My question is : is it still maintained ? And for how long ?

It still receives important security updates, but it's better to use Mageia 6, if possible.

The problem you've hit may be a duplicate of one of the issues in  https://bugs.mageia.org/show_bug.cgi?id=21340 ([TRACKER] Upgrade issues from Mageia 5 to Mageia 6)

Before downgrading to Mga5, or before reinstalling Mageia 5, could you please try to boot into Plasma again, reproduce the issue, switch to tty2 with Ctrl+Alt+F2, log in, become root and run:

   journalctl -ab > log.txt

Please attach log.txt to this bug report.
(compress with xz if it's too large)

Thanks!

Blocks: (none) => 21340

Marja Van Waes 2018-03-14 09:31:23 CET

Keywords: (none) => NEEDINFO

Comment 4 Christian C 2018-03-14 12:27:32 CET
> ... but it's better to use Mageia 6, if possible.
Even under xfce, kmail crashes every minute so it is not usable as it is.

> Before downgrading to Mga5
Sorry ! Too late. It's done !
I need this computer too much.

But anyway, I didn't tell that Ctrl+Alt+F2 does not work anymore. The only way to exit the session (as the cauldron button is not usable) is to kill the X server with Ctrl+Alt+backspace.
Comment 5 katnatek 2018-03-15 00:01:55 CET
(In reply to Christian CHEVALIER from comment #4)
> > ... but it's better to use Mageia 6, if possible.
> Even under xfce, kmail crashes every minute so it is not usable as it is.
> 
If you switch back to mga 6 remember the packages of some kapps don't install all the required packages if your installation don't include plasma as alternative
If you provide the messages of running kmail in mageia 6 from terminal perhaps can provide a set of packages that solve the issue.
Comment 6 Christian C 2018-04-03 22:43:28 CEST
I remembered that I upgraded from mga-5 to mga-6 on another computer a few weeks ago and tested this issue. 
I created a new user and got the same behaviour : black screen on desktop.
Comment 7 Christian C 2018-04-10 14:58:40 CEST
I finally re-installed mga-6 from scratch and get the same result as above.

When I left-click the desktop background or the taskbar, the screen becomes black. If I click again on the taskbar or a window opened on the background, the screen reappears.

But this happens when "Enable Translucency (Composite extension)" is on in the graphical server configuration of the MCC.
If I enable Translucency, the behaviour seems correct.

My graphics board is an Asus 210 silent (Geforce PhysX by Nvidia).

See the attachment for my Xorg configuration.
Comment 8 Christian C 2018-04-11 08:06:04 CEST
Created attachment 10079 [details]
/etc/X11/xorg.conf

My xorg configuration for my Asus 210 graphics board
Comment 9 Marja Van Waes 2018-04-14 09:46:31 CEST
(In reply to Christian CHEVALIER from comment #7)

> When I left-click the desktop background or the taskbar, the screen becomes
> black. If I click again on the taskbar or a window opened on the background,
> the screen reappears.
> 
> But this happens when "Enable Translucency (Composite extension)" is on in
> the graphical server configuration of the MCC.
> If I enable Translucency, the behaviour seems correct.
> 

Do you mean: "If I _disable_ Translucency, the behaviour seems correct"?
Comment 10 Christian C 2018-04-16 10:06:15 CEST
> Do you mean: "If I _disable_ Translucency, the behaviour seems correct"?
Yes, sorry :
If I disable Translucency, the behaviour is correct.
I've been using plasma-5 for a few days without major problems.

And for kmail, the problem is almost resolved.
It came from starting kmail2 after having upgraded. There have been a mixing between my old kmail configuration and what I tried to reconfigure in kmail2.
So kmail2 crashed, akonadi crashed and I couldn't do anything to clear its configuration but :
- remove all the kmail references in .config, .kde4 and .local and there are a lot of them and well hidden
- the same action for akonadi after killing all akonadi processes

The last problem was to restore my mga5 on another disk and to be able to switch from mga5 to mga6 and it's not so easy because grub does not understand very well the naming of the disks in the BIOS to translate it in hdx,y. So using the mageia rescue mode to install the boot loader installs a wrong hdx,y that leads to grub error 17 at boot time.
And finally, I had to manage keeping my kde/plasma configuration when I switch between mga6<->mga5.
These problems are resolved.

There is some saving of my kalarm and kmail configuration and messages left. And restoring under maga6.
I hope the internal tools will do the job.

But my impression is that the developpers didn't take into account upgrading from plasma4 to plasma5.
- 1st at a hardware level (graphics board compatibility)
- 2nd for kde internal tools (like kmail)
Comment 11 Christian C 2018-04-16 10:14:16 CEST
> Do you mean: "If I _disable_ Translucency, the behaviour seems correct"?
No, sorry one more time. I am not completely awaken this morning.

I have to ENABLE Translucency to get the correct behaviour.
What I don't do inmga5 because I don't like it when I move a window.
So after having enabling Translucency, my screen stay alive.

I could disable Translucency in systemsettings and the translucency disappeared when I move a window and it has no disastrous effect on the screen as I said above.
Comment 12 Dave Hodgins 2018-07-11 23:43:57 CEST
Any chance you can retest this? There have been a lot of updates since then
to fix upgrade problems.

CC: (none) => davidwhodgins

Comment 13 Aurelien Oudelet 2020-08-16 17:41:50 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien


Note You need to log in before you can comment on or make changes to this bug.