Bug 24024

Summary:	skrooge fails after launch in Plasma for mageia7-beta1 and fails to respond to user
Product:	Mageia	Reporter:	Len Lawrence <tarazed25>
Component:	Release (media or process)	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	davidwhodgins, geiger.david68210, marja11, sysadmin-bugs
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	journal output after problem encountered journal from second session

Description Len Lawrence 2018-12-17 09:50:52 CET

Description of problem:
On x86_64 UEFI hardware with nvidia proprietary driver, after Plasma upgrade from mageia7-beta1 iso on USB penddrive, skrooge fails to launch properly.
The welcome message is black on MidnightBlue so is virtually impossible to read.
None of the items in borders and menus respond to the mouse exxcept the window decorations.  The kill window button comes back with something like "application not responding" - ""force quit?".  Select "yes" and nothing happens.  Repeat and the same thing happens.  The only way to kill skrooge is to raise a konsole and kill -9 <pid>.

Version-Release number of selected component (if applicable):
Mageia 7 beta1 (iso) x86_64

How reproducible:
Same behaviour on two reboot/logins.  Can be reproduced also in one session.
So, always.

Steps to Reproduce:
1. Run an upgrade installation of a Mageia 6.1 system from a USB pendrive (the base system in this case contained multiple desktops (Mate, Plasma, Xfce). 
2. Reboot and login to Plasma.
3. Select skrooge from the menus or run it as a detached process from a terminal.
4. Try to obtain a response from any of the buttons in the gui.
5. After no response try to kill the application using the window manager and observe that that fails.  (The only recourse at this point is to kill it from a terminal.)

Comment 1 Len Lawrence 2018-12-17 09:57:33 CET

Created attachment 10573 [details]
journal output after problem encountered

Comment 2 Len Lawrence 2018-12-17 09:59:17 CET

Created attachment 10574 [details]
journal from second session

This one shows  attempts to kill the  application.

Marja Van Waes 2018-12-19 08:40:15 CET

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

Comment 3 David GEIGER 2018-12-22 08:26:21 CET

Is skrooge 2.17.0 in Core/Updates_testing repo working with the big kde stack update?

CC: (none) => geiger.david68210

Comment 4 Len Lawrence 2019-02-19 13:09:20 CET

Can't answer that question.  Tried installing skrooge on my Mate production system just now - 2.10.5.  That fails to launch from the menus.  The logo appears and then the process hangs, possibly athe point where 23 plugins have been loaded (23/25).  Two instances of skrooge running, states S and Sl.  zapped them from a terminal.

Using the cli 
$ skrooge
##WARNING: Icon [view-categories] not found
[...]
##WARNING: QFSFileEngine::open: No file name specified
^C

So it will not open without a file.  It is not something I have ever used.

Comment 5 Aurelien Oudelet 2020-08-29 21:17:18 CEST

Hi Len,

What about this bug today?
Is it still valid?

Comment 6 Dave Hodgins 2020-08-29 22:31:21 CEST

I'm not testing an upgrade from M6, just a newly created skrooge account,
where it is working. Closing as fixed using skrooge-2.19.1-2.mga7 from core
updates, under plasma.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
CC: (none) => davidwhodgins