[SOLVED] After update I lost Disk mount KDE widget

[cruzki123]

Hello

This one is probably easy but I do not found the problem. Since last update to plasma 6.4 I lost the widget in the system tray that allows you to mount and umount external devices. I have triple check and it is not in the list to activate or desactivate, so most probably it is not installed at all. This seems a USE flag problem or that I have a package missing. Does anyone knows in which package has the this widget?

Thanks in advance

[rab0171610]

The last updated to 6.4 is in testing so that means you are testing software. Be willing to report bugs if that is the case
and work with Gentoo devs to answer any questions they may ask.

What exact plasmoid are you referring to? Since you did not provide specifics I am going to assume you are referring to 'Disks and Devices' aka device notifier.

That is part of the kde-plasma/plasma-workspace package, which is a dependency of plasma-meta. It is still part of upstream's KDE Gear so I assume it should still be installed and available.

The plasmoid is installed at /usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier.
Please check that directory and report what you find there. If the folder does not exist, you can ensure your use flags do not deviate from the ebuild defaults for KDE packages. I don't think that is the issue.

You can try to reinstall kde-plasma/plasma-workspace (using --oneshot). Check to see if the plasmoid reappeared. You will have to log out and log back in again first.

You can check to see if the /usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier directory exists. Also check the contents of that directory. It should have a folder called contents and a file named metadata.json.
If that directory exists, for testing purposes you can also copy it to ~/.local/share/plasma/plasmoids/ . You can log out and log in again to see if it appears in the list of widgets when adding widgets under 'Panel Configuration'.

Also for testing purposes, if the directory, /usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier is missing you can also try to copy it to your system from another recent and up-to-date KDE installation such as a KDE Neon live disk. Log out and log in again to see if it is available in your widgets list.

If all of that fails, then there is something else going on with your system or a bug but that would seem likely to affect other users also on testing. You can check upstream KDE bug reports for something similar. You can also file a bug report of your own here at Gentoo or upstream.

[cruzki123]

Thansk rab0171610 for the quick answer:

Yes, I am partly in ~amd64 and yes I am willing to report a bug when I have something a little more clearer that this is actualy a bug and not that I have scub up something (as usually).

Yes. I am refering to the 'Disks and Devices' aka device notifier. I have check and /usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier DOES NOT EXISTS on my system (WTF!) and should not have existeed since 6.4.0 (so three re-emerges have been carried out). I have made an equery f and seems like the package install some pieces but not all (!!!)

Code: Select all

equery f kde-plasma/plasma-workspace | grep deviceno
/usr/lib64/qt6/plugins/kf6/kded/devicenotifications.so
/usr/share/locale/es/LC_MESSAGES/kded_devicenotifications.mo
/usr/share/locale/es/LC_MESSAGES/plasma_applet_org.kde.plasma.devicenotifier.mo

My useflags are:

kde-plasma/plasma-workspace-6.4.3 USE="X calendar networkmanager (policykit) screencast telemetry -appstream -debug -fontconfig -handbook -ksysguard -semantic-desktop -systemd -test -wallpaper-metadata"

According to my packages.use, I am doing:

kde-plasma/plasma-workspace -wallpaper-metadata -fontconfig -ksysguard

I have checked the ebuild and seems like the only one that might be related is ksysguard. I am just rebuilding with this use flag to see if the plasmoid got installed. If this is the case, I think that a note after emerging that package without this useflag could be handy

I will came back in one hour (yes, emerge take some time in this machine

EDIT:

OK, adding ksysguard solve the problem. Do you think it would be usefull to fill a bug about this?

Thanks a lot.

[rab0171610]

So my suggestion to "ensure your use flags do not deviate from the ebuild defaults for KDE packages" is the solution. This does not look like a bug to me. There is a new +ksysguard use flag in the ebuild for plasma-workspace. It appears to be enabled by default in the 6.4 version according to the ebuild. My question to you is did you previously disable or negate this use flag? You should not have had to rebuild plasma-workspace with +ksysguard unless you had previously disabled it with intent.
Previously kde-plasma/libksysguard was a dependency of plasma-workspace but it now appears that it is a dependency only if the ksysguard use flag is enabled.
https://github.com/KDE/libksysguard
"Library to retrieve information on the current status of computer hardware"
Without digging into the code there, It is very possible that this library would be necessary for org.kde.plasma.devicenotifier to function correctly. If that is the case it would make sense that any plasmoids that rely on this library to function correctly would not be installed if library is not satisfied as a dependency. It would make no sense to install plasmoids that will not function correctly. Again, this is just assumption on my part.

https://packages.gentoo.org/useflags/ksysguard

Code: Select all

   Packages describing “ksysguard” as local USE flag
Package	“ksysguard” Flag Description
kde-plasma/plasma5support	Enable device notifications dataengine using kde-plasma/libksysguard
kde-plasma/plasma-workspace	Enable device notifier and system monitor applets as well as terminate applications runner   

That seems to indicate that the +ksysguard use flag does indeed enable device notifier.
Anyway, my suggestion is to allow your profile (or the ebuilds if you are on a minimal profile) to dictate what use flags are enabled or disabled and ONLY override this is if you know exactly what you are doing and why. I would keep any deviations from the defaults to a minimum.

[cruzki123]

Hi rab0171610

Yes, I have manually override the default configuration and seems like I have missing the description of the use flag. As usual, this was my mistake. So everything is now solved

Thanks again.