Trying To Figure Out Why Discovery is Included in OM

Coffee break
1

Me and a couple of friends are experimenting a bit with some modifications to OM to better fit our uses. I want to streamline and par down a few things in preparation for trying XFCE with OM.

I was told never to update via Discovery store.

That leaves me with a question: Why is Discovery included in OM if it is not to be used? Why not remove it?

Not being a smart ass here, I genuinely want to know if there is a specific reason it is still here.

I don’t want to just rip it out until I know if it will break something or not. I guess I could just try it and see lol. I don’t like leaving broken things on the system unless it is a work in progress sort of situation.

Any thoughts or opinions or actual information on this?

2

I removed it from my Rock 6.0 and ROME 06.25 installs and have never faced a Problem regarding it.

2 Likes
3

Good to hear, I’m gonna try it.

4

When I look at removing discover using DNFDrake, it also wants to remove plasma6-discover-backend-flatpak. Would this remove flatpack support from FlatDrake?

Would it be better (and safer) to remove it using the CLI?

dnf remove --noautoremove plasma6-discover
1 Like
5

I will try it later. I have set up 3 OM VMs to practice on because I know I’m gonna fuck shit up a lot.

2 Likes
6

Welcome to the club :handshake: If I didn’t back up my root partition before I do anything I’d be totally hosed.

4 hours last night…4 HOURS…over a mistake in my crypttab //me bangs head on wall

1 Like
7

As a first step to development learning, I spent my evening reading time last night going over the package management documentation from the wiki. It does not seem any harder than the PowerShell scripts I wrote for my business automation tasks.

It is also not any more boring than my day job. I am spending today disassembling small kitchen appliances for parts to sell on eBay. I’ve got blenders, coffee machines, crock pots and food processors. Anyone need a crock pot lid?

8

I mean, I could not really care any less about any gui package installer, dnf is sufficient, when something is not there there is almost always a tarball or an appimage for it, currently I have almost no flatpaks (just me being lazy/not taking the time to completely remove it from my rock machine, the rome has abseloutely no flatpaks)

9

I just don’t want broken shit on my system and I don’t need multiple pieces of software that do the same thing.

I do use some flatpacks so I will be careful about that.

10

Not at the moment…thanks for asking

1 Like
11

This has been fixed and Discover should use the correct command (dnf dsync) to upgrade Cooker and ROME systems. I test this but I do not really recommend it. Discover IMO has been a :poop: since it’s inception.

  1. One culprit is that Discover uses packagekit it is packagekit that is the problem.
  2. Another culprit is that the way OMLx developes and maintains software is unique and does not work well at all with packagekit
  3. I have heard rumors that some future version of Discover will not use packagekit and will work with native package managers such as dnf or apt.
  1. Because it is a part of KDE Plasma desktop which is the primary focus of OMLx development.
  2. Because it is a good way for users to “Discover” software, it is a good gui tool to search for software.

What was the fix for Discover? @bero created a script that uses dnf dsync plus options to upgrade users systems instead of packagekit doing this.

Edit: My suggestion is if you don’t like it don’t use it and don’t worry about it. I don’t use it except for the occasional test.

2 Likes
12

This should work:

rpm -e --nodeps plasma6-discover

2 Likes
13

Thanks for the good info there. I figured there was a reason. Not using it is what I’ve been doing on the machines that are in actual use. I just had the idea to experiment with removing anything that does not work 100%. Broken things nag at my OCD brain a bit. It feels like having broken glass on the floor or something. Makes me want to sweep it up into the dustpan.

It is more of a learning exercise than anything else.

I also want to eventually use XFCE as that is the best desktop IMO so I want to see how much KDE I can remove without breaking anything. KDE is rather on the heavy side for my taste and it has that weird little off-putting animation that pulses when opening a program. WTF is up with that little thing?

14

No, it doesn’t affect Flatdrake. I usually remove Discover with the “nodeps” function in Dnfdrake “extras” or from the command line.

3 Likes
15

Go to System Settings → Colors and Themes → Cursors → Configure Launch Feedback (in the top bar) and set it to None. Gone.

That’s part of what makes KDE awesome, actually. If you don’t like how it behaves, you can almost always configure it to do what you want.

4 Likes
16

Cool, thanks for that.

I also like how a PC zips like greased lightning with XFCE. Even on potato hardware. How would I make KDE work at the same speed?

My favorite machines are potatoes that I have had for many years. One has a Core Duo Quad processor with 8GB RAM and the other has an old Celeron that was never high end to begin with and 8GB RAM. I currently have Devuan on them because of XFCE performance. I have modern machines for work, but they lack the personality of these old friends.

17

Well, you might want to turn off search indexing. I don’t think XFCE has that:

System Settings → Search → uncheck Enabled.

Adjust General Behavior → Animation Speed to Instant; uncheck Smooth Scrolling; change the double-click interval

Then you could adjust the effects under Window Management → Desktop Effects

There used to be a way to disable the compositor altogether, but maybe that was only on X11 (I’m on Wayland).

2 Likes
18

Awesome man, thanks.

I’ll play with the settings and see if I can make it work. I would like to have everything on the same distro if possible.

I’m not sure if I’m the only moron to have sentimental attachment to computers, but I’m not willing to let these go.

19

You could always move /tmp to ram. That makes a speed difference


# Move /tmp to ram
#==========================================================================================================
tmpfs                                       /tmp                 tmpfs   noatime,nodiratime,mode=1777             0 0 
#==========================================================================================================
1 Like
20

Well that sounds interesting.