Hi, Am Dienstag, 24. November 2020, 10:35:20 CET schrieb Dario Faggioli:
Hi everyone,
On Tue, 2020-11-24 at 09:42 +0100, Fabian Vogt wrote:
Am Dienstag, 24. November 2020, 09:34:39 CET schrieb Syds Bearda:
I reinstalled MicroOS desktop KDE this morning as the new partitioning was enabled. However as I changed my DE to KDE I could not mount my USB drive anymore. I enabled the automount removable drives in the system settings. And it still did nothing. Reboots also didn't work.
As such I'm now running Gnome again and there it works as intended.
Do you guys know which package is missing on the KDE desktop?
If the popup doesn't appear, it's probably udisks2. Otherwise, logs (mostly the journal) would be useful here.
So, I think I run into the same/similar issue on GNOME, and in fact I added `udisks2` and other packages to the GNOME Desktop pattern, see:
https://build.opensuse.org/request/show/840921
This (i.e., the fact that it's an issue on KDE as well) kinds of confirms something that I was wondering about already, which is the fact that some of the packages that we have under `%package desktop- gnome` would probably be useful under `%package desktop-kde`, and vice versa.
Now, we can put them there, of course, but that would mean quite a bit of duplication. How can we handle that?
Normally I'd copy whatever the non-MicroOS patterns do, for consistency. However, udisks2 is pulled in through Recommends by gvfs resp. libKF5Solid5, which don't have any effect on MicroOS due to "onlyRequires". (This is the reason why I tell users that setting onlyRequires themselves is a bad idea)
Should we have some kind of `%package desktop` with common stuff, that then both the GNOME and KDE patterns depends on? Or are there better ways of doing that?
While I don't think the overlap is that much, a pattern for deduplication would probably still make sense. Cheers, Fabian
Regards