SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I run openSUSE 24/7, plus I have many installations on various extra PCs mainly used for QA and support work, including Debian, Fedora, Mageia & others. On none of them do I have PackageKit installed. openSUSE has Zypper and YaST for package management. It doesn't need PackageKit.
That might be so, but I doubt that OP installed it of their own volition.
Can you say for sure their system won't break if they remove something that is at the very least indirectly involved in its management?
My guess is that the KDE package manager uses it as a backend?
As I said, manual updates/grades would probably be better on this hardware.
PackageKit is just a front-end - I would not expect it to be risky in the same way as removing apt/yum/etc might be, since one could just reinstall it with whatever tool they uninstalled it with?
As per Who uses PackageKit?, KDE's Apper doer use it, so if that is relied upon then removing it presumably isn't an option, but since pinguin20 says they've switched from Plasma to Cinnamon, they probably aren't using Apper any more?
In any case, a dry-run/simulation removal should highlight dependencies and allow a more informed choice on the matter.
But, if the issue is random freezes potentially caused by PackageKit doing automated updates, it would make most sense to first work out what is triggering PK to start in the first place, and maybe testing what happens if the packagekitd service is disabled, without actually uninstalling.
PackageKit is an add-on, not necessary to run any openSUSE system, but automatically started by default if installed. Plasma has enough to do. It doesn't need to be involved in package management. My brother was running Plasma on 15.3 and bothered by various things, including daily updates. I told him to uninstall it. Now he's happy. On openSUSE forums and mailing lists removing it and Apper is a common recommendation.
You disconnect the PC power cable, open the PC cover, and remove the power and signal cables from the rear of the OM drive. The signal cable may or may not have a tab latch to hold it fast. The power cable simply pulls away.
Not sure what you mean by "add-on"?
In any case, PackageKit is a "high level front-end for different package management systems". By default it's just a daemon which in turn relies on various fron-ends (GUI or TUI), two of which are Apper and Discover.
Whether it's optional or not is debatable - arguably, most software preinstalled on any distro is optional.
Quote:
Originally Posted by mrmazda
My brother was running Plasma on 15.3 and bothered by various things, including daily updates. I told him to uninstall it. Now he's happy. On openSUSE forums and mailing lists removing it and Apper is a common recommendation.
I'll take your word for it.
For the sake of clarification, you told him to uninstall what? Packagekit/Apper or Plasma?
However, the crucial bit of info (that I overlooked previously) is this IMO:
Quote:
Originally Posted by boughtonp
pinguin20 says they've switched from Plasma to Cinnamon, they probably aren't using Apper any more?
And, I'll repeat, IMHO OP's machine is suffering from overload, there's nothing wrong with it per se.
Not sure what you mean by "add-on"?
In any case, PackageKit is a "high level front-end for different package management systems". By default it's just a daemon which in turn relies on various fron-ends (GUI or TUI), two of which are Apper and Discover.
Whether it's optional or not is debatable - arguably, most software preinstalled on any distro is optional.
I'll take your word for it.
For the sake of clarification, you told him to uninstall what? Packagekit/Apper or Plasma?
However, the crucial bit of info (that I overlooked previously) is this IMO:
And, I'll repeat, IMHO OP's machine is suffering from overload, there's nothing wrong with it per se.
I think he told him to uninstall PackageKit, and in my case I decided to just disable it and mask it to make sure that this service is not loading again
What is IMO or IMHO? If the real problem is overload then how can I solve it?
I have installed several distros and all of them has same issue. If my current distro freezes again I will search for what you suggested. Sadly, for now, I don't have enough money to upgrade my computer, so there isn't much to do
If the real problem is overload then how can I solve it?
If there are things running in the background you don't use, uninstall or disable them. sudo ps -A should give you many clues to what's been loaded. Top/htop show resource consumption. systemctl list-unit-files | grep service | egrep -v 'static|generated|disabled|masked' shows systemd's loaded/running tasks. Indexers can be a serious problem on a system short on resources.
If the system thinks it's supposed to be able to be accessing an OM drive that's bad, it can tie up resources. That can happen with a program that accessed files from an OM disc, and keeps a history of accesses, when there is no disc in the drive.
4GB isn't a whole lot of RAM. Close programs when not using them, web browsers especially. Don't keep a lot of web browser tabs open at once. Avoid web sites whose pages don't have a fixed size or end, e.g. Facebook. I wouldn't call 4GB a shortage per se, but it is an amount that needs to be respected with common sense. When something of significant consequence must be swapped out, it's usually pretty noticeable as a pause or apparent freeze that lasts more than a second or two.
Did you disconnect the OM drive?
Don't forget post #5. Hardware issues are a common cause of freezing, which here seems all the more likely because different distros misbehave similarly.
If there are things running in the background you don't use, uninstall or disable them. sudo ps -A should give you many clues to what's been loaded. Top/htop show resource consumption. systemctl list-unit-files | grep service | egrep -v 'static|generated|disabled|masked' shows systemd's loaded/running tasks. Indexers can be a serious problem on a system short on resources.
If the system thinks it's supposed to be able to be accessing an OM drive that's bad, it can tie up resources. That can happen with a program that accessed files from an OM disc, and keeps a history of accesses, when there is no disc in the drive.
4GB isn't a whole lot of RAM. Close programs when not using them, web browsers especially. Don't keep a lot of web browser tabs open at once. Avoid web sites whose pages don't have a fixed size or end, e.g. Facebook. I wouldn't call 4GB a shortage per se, but it is an amount that needs to be respected with common sense. When something of significant consequence must be swapped out, it's usually pretty noticeable as a pause or apparent freeze that lasts more than a second or two.
In my case when freeze issue happens the entire system gets frozen even keyboard and mouse. I tried the shortcut to kill X server and it didn't work, only REISUB
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.