Description of problem: After installing the latest updates (urpmi --auto-update) most applications won't start anymore on my gnome desktop. For example starting Thunderbird or Firefox from the gnome desktop does not work (the applications do not open) - the same outcome when I start them via command line. LibreOffice starts but it takes approximately two minutes until the application is open. Anyways, some applications start without problems, e. g. Geany and Nautilus. When I choose "Gnome 3 on Xorg" at the login screen, then everything is fine (firefox, thunderbird and libreoffice are starting normally). So it's probably related to Wayland (because Gnome 3 uses Wayland as default). Version-Release number of selected component (if applicable): Gnome 3.24.3-1 How reproducible: Just update your system with "urpmi --auto-update" and reboot and login to the default Gnome 3 Shell (on Wayland).
Severity: critical => normal
Assignee: bugsquad => gnomeCC: (none) => marja11
Anything shown when running from the terminal? I thought the Wayland upgrade was tested for GNOME.
CC: (none) => olav
(In reply to Olav Vitters from comment #1) > Anything shown when running from the terminal? I thought the Wayland upgrade > was tested for GNOME. Yeah, I'm running the new wayland since February 7th without issues so we need more info...
Keywords: (none) => NEEDINFOCC: (none) => tmb
Thanks for your feedback. Unfortunately, there is no output on the terminal when launching one of the mentioned applications. The applications seem to hang forever. top does not show any suspicious processes - the CPU is idle all the time. But there is something even more strange: When I close the terminal where I started libreoffice then libreoffice opens (and I can work with it).
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 => RESOLVEDResolution: (none) => OLDCC: (none) => ouaurelien