Where is packagekit started from?

[tho.mei]

Hallo

I just moved from Fedora8 to 10. On F8 and before I wrote my own cron-jop to update the system. (see: http://forums.fedoraforum.org/showpo...3&postcount=11) It did always It's job very well in the background. Without interruption of the users.

I thorough PackageKit could now do it. But I learned, PackageKit is no backgrund-service. It asks for password and beg for OK..... A relay annoying tool. And if I or a user would need a GUI package manager, I would advice yumex. There is a handy search an package groups available.

Now I can't find where the packagekit-deamon is started. I'm not familiar with the new upstart. But I can't find packagekit in /etc/rc.* or in /etc/cron*. And tt is not listed in system-config-services, but it is loaded at boot time. Where is packagekit started from? I don't like to deinstall it at the moment.

[darth01]

System -> Preferences -> Personal -> Sessions

[tho.mei]

Hallo darth01

Thanx for your answer!
But it's not a lot of help
I use KDE. There is no such tool.

Could you tell my the command? Or can you tell my which script packagekit does start?

[tameboy]

command: gpk-application

[marcrblevins]

Look at:
http://www.packagekit.org/pk-faq.html#session-system

[tho.mei]

I've no gpk-application on my box. But kpackagekit still runs in the background.

I'm still look for a solution to stop and disable the packagekit daemon. I won't deinstall it. Some one a idea?

Until now, I believed on Fedora every thing is started by init-scripts or cron-job. Was there a change because of upstart? I thought upstart does still use the init-scripts. It's relay a worse thing to implement daemons how are not shown by system-config-services. To implement it an daemon that not startet like other is much more worse!

It reminds my on Windwoz. Now it seams easier to stop a daemon in Windowz. Registry... Or is it a debian habit?

[tho.mei]

Hallo
I'm still looking for a way to have Packagekit installed but not running as a daemon. I've no gpk-application on my box, because the ins no Gome installed. May Packagekit is "...coded as a QObject for KDE..." But how should I remove a QObject.

I thought qt until now qt is as a toolkit for GUI. Since when does a GUI start a system daemon? How far from UNIX have we come?

Anyway... today I tried to update the system with packagekit (last test of it!) It was unable to find the dependencys. And there was not hope for a linux-newbe (not me) to solve problem.
I could solve it fast:

su -
killall packagekitd
yum upgrade
I got the result:

...
---> Package kernel-headers.i386 0:2.6.27.7-134.fc10 set to be updated
---> Package device-mapper-libs.i386 0:1.02.27-7.fc10 set to be updated
---> Package PackageKit-qt.i386 0:0.3.11-4.fc10 set to be updated
---> Package cjkunifonts-uming.noarch 0:0.2.20080216.1-10.fc10 set to be updated
---> Package libarchive.i386 0:2.5.5-2.fc10 set to be updated
---> Package system-config-printer.i386 0:1.0.12-2.fc10 set to be updated
---> Package kernel-firmware.noarch 0:2.6.27.7-134.fc10 set to be updated
---> Package kernel.i686 0:2.6.27.7-134.fc10 set to be installed
---> Package cups.i386 1:1.3.9-4.fc10 set to be updated
---> Package PackageKit-glib.i386 0:0.3.11-4.fc10 set to be updated
---> Package PackageKit-yum.i386 0:0.3.11-4.fc10 set to be updated
---> Package nfs-utils.i386 1:1.1.4-4.fc10 set to be updated
--> Finished Dependency Resolution
kpackagekit-0.3.1-4.fc10.i386 from installed has depsolving problems
--> Missing Dependency: libpackagekit-qt.so.10 is needed by package kpackagekit-0.3.1-4.fc10.i386 (installed)
Error: Missing Dependency: libpackagekit-qt.so.10 is needed by package kpackagekit-0.3.1-4.fc10.i386 (installed)
[root@srat01 ~]#

Did I tell you how I dislike pachagekit?
Next step:
yum remove packagekit -y
And the I got success with:
yum upgrade

Now packagekit won't run after next boot. But I still would like to install it again. But not as a daemon! (This because I'm not the only person how uses the workstations. Some my like to search Software by Packagekit.)

Now I set up the cron-job I wrote in 2004 to upgrade Fedora Core 3 in the backgrund. (See: http://forums.fedoraforum.org/showpo...3&postcount=11) It works well. It could be that simply!

[marcrblevins]

How funny, I ran "yum provides */libpackagekit-qt.so.10" and got:

[root@kiriyamablevins marc]# yum provides */libpackagekit-qt.so.10
Loaded plugins: refresh-packagekit
fedora                                                   | 2.8 kB     00:00     
rpmfusion-free-updates                                                                                                                                     | 2.7 kB     00:00     
rpmfusion-nonfree-updates                                                                                                                                  | 2.7 kB     00:00     
rpmfusion-nonfree-updates/primary_db                                                                                                                       |  18 kB     00:00     
rpmfusion-free                                                                                                                                             | 2.7 kB     00:00     
rpmfusion-nonfree                                                                                                                                          | 2.7 kB     00:00     
updates                                                                                                                                                    | 2.3 kB     00:00     
updates/primary_db                                                                                                                                         | 931 kB     00:02     
rpmfusion-nonfree/filelists_db                                                                                                                             |  41 kB     00:00     
updates/filelists_db                                                                                                                                       | 2.4 MB     00:11     
rpmfusion-free-updates/filelists_db                                                                                                                        | 7.0 kB     00:00     
rpmfusion-free/filelists_db                                                                                                                                | 269 kB     00:01     
rpmfusion-nonfree-updates/filelists_db                                                                                                                     | 5.6 kB     00:00     
PackageKit-qt-0.3.9-4.fc10.i386 : QT libraries for accessing PackageKit
Matched from:
Filename    : /usr/lib/libpackagekit-qt.so.10

PackageKit-qt-0.3.9-4.fc10.i386 : QT libraries for accessing PackageKit
Matched from:
Filename    : /usr/lib/libpackagekit-qt.so.10
[root@kiriyamablevins marc]#

Your list is showing a newer version: PackageKit-qt.i386 0:0.3.11-4.fc10

[tho.mei]

Hallo marcrblevins

Your list is showing a newer version: PackageKit-qt.i386 0:0.3.11-4.fc10

nice, but how do I disable the packagekit daemon? Where is it stared from? Is it relay a Qobject.

[Weasel68]

Hi,

PackageKit is a pain when it starts everytime you login and checks for new packages.
Telling it to 'Never check for updates' from it's popup window doesn't seem to stop it checking the next time you login.

There are 2 ways I have found to stop it. With the first method, it stiil starts, but doesn't seem to check for updates.

1. System -> System Settings -> Add and Remove Software -> Settings
Check for update = Never
Automatically Install = None
Uncheck 'Notify me when updates are avaliable'

2. If this doesn't work, the process that checks for updates is '/usr/bin/gpk-update-icon'.
You can rename the file so it can't start...
'mv /usr/bin/gpk-update-icon /usr/bin/gpk-update-icon.bak'

To enable it again, just rename it back.

Once PackageKit is disabled, you can use yumex to manually check for updates.

[marcrblevins]

Ouch, that is alot of work.
Con:
If its a real daemon, it should have a service file that we could shut it off like we do with vsftpd, httpd, etc. That is the Fedora Way. I don't see why this package is bending the rules. Should be allow to stop it temporary per se when dbus was busted.
Pro:
PackageKit is running nicely so far.

[tho.mei]

@marcrblevins
I agree!

[jenaniston]

An older thread, but recent F20 KDE installed from live gets locked up in yum
as it goes through checking for 422 updates. Yumex is now erasing 9 packagekit packages,
but really there has to be a way to turn this daemon off.

In KDE F20, Applications > Administration > Service Configuration there may be a possibility . . .

But since the pid (process id is identified in the yum lock) I could kill the process, or find it by

ps ax|grep packagekit

and then

 kill <pid>

[PabloTwo]

Yumex is now erasing 9 packagekit packages,
but really there has to be a way to turn this daemon off.

Being rid of PackageKit gets my vote, but then I'm a "yum at the command line only" type of guy. But now days, yum itself has an automatic check for updates built in in Fedora. Yes, you can turn it off,

# systemctl disable yum-makecache.timer

And if you also have dnf installed, do the same for it,

# systemctl disable dnf-makecache.timer

[Ahmad Samir]

An older thread, but recent F20 KDE installed from live gets locked up in yum
as it goes through checking for 422 updates. Yumex is now erasing 9 packagekit packages,
but really there has to be a way to turn this daemon off.

In KDE F20, Applications > Administration > Service Configuration there may be a possibility . . .

But since the pid (process id is identified in the yum lock) I could kill the process, or find it by

ps ax|grep packagekit

and then

 kill <pid>

This should work:

systemctl mask packagekit.service

of course uninstalling PackageKit takes care of the issue altogether.