Bug 32489

Summary: Dolphin don´t open file | follow up notice
Product: Mageia Reporter: Holger Mainz <Ed_Werder>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: minor    
Priority: Normal CC: fri, lewyssmith
Version: 9   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: ^

Description Holger Mainz 2023-11-03 17:28:02 CET
The problem was solved by 

dnf install task-plasma5-minimal

but this has slowed my Computer down at close to zero. I then had to remove it.
Comment 1 Holger Mainz 2023-11-03 17:30:01 CET
Created attachment 14125 [details]
^

Addition
Comment 2 Holger Mainz 2023-11-03 17:30:44 CET
down to close to zero
Comment 3 katnatek 2023-11-03 18:23:24 CET
Must be one o the dependencies, but I not sure what
Try to disable some things in Systemsettings -> Startup and Shutdown -> Background Services

I disable Search Folder Updater and Bluetooth (I don't have bluetooth)
Comment 4 Holger Mainz 2023-11-04 04:15:40 CET
Yeah, there are a lot of them, i would say some 40 packages.

Search Folder Updater does not show up in my start/stop settings.
Comment 5 Lewis Smith 2023-11-07 22:31:01 CET
"Dolphin don´t open file | follow up notice"
Follow-up to what? Sorry, comment 0 makes no sense on its own. This bug on its own is a mystery

Trying to deduce the series of events:
1. A problem - not described in this bug
2. solved by dnf install task-plasma5-minimal
3. slowed my Computer down at close to zero:
 in what sense?
4. had to remove it
 I am surprised you could without taking out Plasma and a lot of other stuff.
 Also, did that not re-introduce the original problem, point 2?
5. down to close to zero
 Comment 1 (top O/P). What was down?

CC: (none) => lewyssmith

Comment 6 Morgan Leijström 2023-11-07 23:48:16 CET
I believe this was the user having problems that right clicking in Dolphin did not work to open file, and it was solved by installing task-plasma5-minimal, which apparently pulled in needed stuff.

Removing a task-* package do not remove anything directly, but it makes it possible to remove other parts.  This package is empty but pulls in all stuff needed for a functional Plasma desktop.

So it is impossible that that the removal of task-plasma5-minimal helped the issue described as nothing got changed by that alone.

I do not understand what the attachement is supposed to describe, no CPU hog in sight.  So what is the problem?

CC: (none) => fri

Comment 7 katnatek 2023-11-08 00:04:49 CET
See if the logs in ~/.local/share/sddm/ have useful information
Comment 8 Lewis Smith 2023-11-09 21:21:20 CET
(In reply to Morgan Leijström from comment #6)
> Removing a task-* package do not remove anything directly, but it makes it
> possible to remove other parts.  This package is empty but pulls in all
> stuff needed for a functional Plasma desktop.
 $ sudo urpme --test task-plasma5-minimal
You are right: testing removing it allowed its removal (in principle) without threatening to remove other packages. Strange.

> I do not understand what the attachement is supposed to describe,
> no CPU hog in sight.
I think that is what it it is meant to show: that whatever was slowing the computer (? task-plasma5-minimal) is not doing so any more.

@Holger
Seeing that you used DNF comment 0, can we be assured that you always use this, and do not mix it with Add/Remove software (= rpmdrake)?

I think we can close this 'works' after getting a reply. Equally if no reply.
Comment 9 Morgan Leijström 2023-11-09 21:30:12 CET
Thinking...

Maybe installing task-plasma5-minimal with dependencies made the indexing service operable and got to work for a while, and it was *that* workload the user noticed.  And then indexing finished about the same time he uninstalled task-plasma5-minimal, by coincidence only.

:) ?
Comment 10 Holger Mainz 2023-11-23 18:16:50 CET
(In reply to katnatek from comment #7)
> See if the logs in ~/.local/share/sddm/ have useful information

Can it be, that /usr/share/sddm is the folder ?
Comment 11 Holger Mainz 2023-11-23 18:19:03 CET
> @Holger
> Seeing that you used DNF comment 0, can we be assured that you always use
> this, and do not mix it with Add/Remove software (= rpmdrake)?
> 
> I think we can close this 'works' after getting a reply. Equally if no reply.

Indeed, i am using mainly dnf, but also urpmi here and there and the mcc, since searching packages is way easier there
Comment 12 katnatek 2023-11-23 18:46:09 CET
(In reply to Holger  Mainz from comment #10)
> (In reply to katnatek from comment #7)
> > See if the logs in ~/.local/share/sddm/ have useful information
> 
> Can it be, that /usr/share/sddm is the folder ?

sddm write some logs in ~/.local/share/sddm
Comment 13 Lewis Smith 2023-11-23 22:41:23 CET
Since Holger's problem comment 0 is gone, we can close this.

(In reply to Holger  Mainz from comment #11)
> > Seeing that you used DNF comment 0, can we be assured that you always use
> > this, and do not mix it with Add/Remove software (= rpmdrake)?
> Indeed, i am using mainly dnf, but also urpmi here and there and the mcc,
> since searching packages is way easier there

It is never a good idea to mix the two. Apparently Orphans get messed up.

Status: NEW => RESOLVED
Resolution: (none) => INVALID