Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: how can i stop PackageKit -

  1. #1

    Default how can i stop PackageKit -

    how can i stop PackageKit

    i want to run sudo zypper up

    since i run in a bug
    https://forums.opensuse.org/showthre...-queue-so-what


    note. i had luck in running the abofe mentioned command - but now (today) i try to do so on a new notebook - now i have to install ++ updates... in opensuse.#
    note: the notebook was not in use for more than 1 month.

    but packagekit does not want me to do so - does not allow this....

    it allways stops the process


    PackageKit blockiert zypper. Dies passiert, wenn Sie ein Aktualisierungsmodul oder eine andere Softwareverwaltungsanwendung benutzen, die PackageKit verwendet.
    PackageKit beenden? [ja/nein] (nein): j
    PackageKit läuft noch (wahrscheinlich aktiv).
    Erneut versuchen? [ja/nein] (nein): j
    PackageKit läuft noch (wahrscheinlich aktiv).


    need your help now

    look forward to hear from you
    dilbert ;-)
    Wordpress-development - a Toolset: wpgear.org

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,769

    Default Re: how can i stop PackageKit -

    kill packagekit from command line

    ps -A
    lists all processes
    find the PID (process ID) of packagekit

    then
    kill PID
    where PID is the ID for packagekit

    I forgot if you have to be root. Probably would not hurt

    With package kit dead and as root

    zypper up

  3. #3

    Default Re: how can i stop PackageKit -

    Quote Originally Posted by gogalthorp View Post
    kill packagekit from command line

    ps -A
    lists all processes
    find the PID (process ID) of packagekit

    then
    kill PID
    where PID is the ID for packagekit
    Or "sudo killall packagekitd" would also work.

    Or use KDE's system monitor (Ctrl+ESC), it will ask you for the root password if you try to kill a root process (or any process running as another user).

    I forgot if you have to be root. Probably would not hurt
    Yes. packagekitd runs as root.

    That said, if packagekitd is always blocking, something seems to be wrong with your repos.
    It should shut itself down after 15 seconds of inactivity.

    So check too that you don't have any repos that are not reachable at the moment. E.g. try to run "sudo zypper ref" after you killed packagekitd.

  4. #4

    Default Re: how can i stop PackageKit -

    hello

    many thanks - this is very helpful

    guess that the pid is 2037

    should i run kill PID2037

    see the following

    Code:
    Die Systemverwaltung ist durch die Anwendung mit dem PID 2037 (/usr/lib/packagekitd) gesperrt.
    Schließen Sie diese Anwendung, bevor Sie es erneut probieren.
    martin@linux-o61y:~> ps -A
      PID TTY          TIME CMD
        1 ?        00:00:04 systemd
        2 ?        00:00:00 kthreadd
        3 ?        00:00:01 ksoftirqd/0
        5 ?        00:00:00 kworker/0:0H
        7 ?        00:00:01 rcuc/0
        8 ?        00:00:00 rcub/0
        9 ?        00:00:04 rcu_preempt
       10 ?        00:00:00 rcu_sched
       11 ?        00:00:00 rcu_bh
       12 ?        00:00:00 migration/0
       13 ?        00:00:00 watchdog/0
       14 ?        00:00:00 watchdog/1
       15 ?        00:00:00 migration/1
       16 ?        00:00:00 rcuc/1
       17 ?        00:00:00 ksoftirqd/1
       19 ?        00:00:00 kworker/1:0H
       20 ?        00:00:00 watchdog/2
       21 ?        00:00:00 migration/2
       22 ?        00:00:00 rcuc/2
       23 ?        00:00:00 ksoftirqd/2
       25 ?        00:00:00 kworker/2:0H                                                                                                                                                            
       26 ?        00:00:00 watchdog/3                                                                                                                                                              
       27 ?        00:00:00 migration/3                                                                                                                                                             
       28 ?        00:00:00 rcuc/3                                                                                                                                                                  
       29 ?        00:00:00 ksoftirqd/3                                                                                                                                                             
       31 ?        00:00:00 kworker/3:0H                                                                                                                                                            
       32 ?        00:00:00 khelper                                                                                                                                                                 
       33 ?        00:00:00 kdevtmpfs
       34 ?        00:00:00 netns
       35 ?        00:00:00 khungtaskd
       36 ?        00:00:00 writeback
       37 ?        00:00:00 ksmd
       38 ?        00:00:01 khugepaged
       39 ?        00:00:00 crypto
       40 ?        00:00:00 kintegrityd
       41 ?        00:00:00 bioset
       42 ?        00:00:00 kblockd
       44 ?        00:00:00 ata_sff
       45 ?        00:00:00 khubd
       48 ?        00:00:00 kswapd0
       49 ?        00:00:00 fsnotify_mark
       56 ?        00:00:00 kthrotld
       58 ?        00:00:00 scsi_eh_0
       59 ?        00:00:00 scsi_tmf_0
       60 ?        00:00:00 scsi_eh_1
       61 ?        00:00:00 scsi_tmf_1
       64 ?        00:00:00 kpsmoused
       66 ?        00:00:00 ipv6_addrconf
       67 ?        00:00:00 deferwq
       70 ?        00:00:00 kworker/2:1H
      110 ?        00:00:00 kauditd
      122 ?        00:00:00 kworker/1:2
      131 ?        00:00:00 kworker/0:2
      205 ?        00:00:00 kworker/3:2
      223 ?        00:00:00 kworker/0:1H
      227 ?        00:00:00 kworker/3:1H
      234 ?        00:00:00 kworker/1:1H
      251 ?        00:00:00 jbd2/sda6-8
      252 ?        00:00:00 ext4-rsv-conver
      337 ?        00:00:01 systemd-journal
      345 ?        00:00:00 dmeventd
      346 ?        00:00:00 lvmetad
      362 ?        00:00:00 systemd-udevd
      373 ?        00:00:02 haveged
      397 ?        00:00:00 acpi_thermal_pm
      400 ?        00:00:00 cfg80211
      401 ?        00:00:00 irq/106-mei_txe
      413 ?        00:00:00 hd-audio0
      425 ?        00:00:00 kmemstick
      455 ?        00:00:00 jbd2/sda7-8
      456 ?        00:00:00 ext4-rsv-conver
      473 ?        00:00:00 auditd
      641 ?        00:00:00 avahi-daemon
      644 ?        00:00:00 wpa_supplicant
      646 ?        00:00:00 ModemManager
      649 ?        00:00:04 dbus-daemon
      650 ?        00:00:06 nscd
      656 tty1     00:00:00 agetty
      721 ?        00:00:00 systemd-logind
      726 ?        00:00:02 NetworkManager
      728 ?        00:00:00 polkitd
      743 ?        00:00:00 kdm
      759 ?        00:00:00 cupsd
      808 tty7     00:03:46 Xorg
      984 ?        00:00:00 kdm
     1050 ?        00:00:00 master
     1051 ?        00:00:00 pickup
     1052 ?        00:00:00 qmgr
     1067 ?        00:00:00 cron
     1092 ?        00:00:00 systemd
     1093 ?        00:00:00 (sd-pam)
     1094 ?        00:00:00 startkde
     1176 ?        00:00:00 dbus-launch
     1177 ?        00:00:00 dbus-daemon
     1178 ?        00:00:00 gpg-agent
     1218 ?        00:00:00 start_kdeinit
     1219 ?        00:00:00 kdeinit4
     1220 ?        00:00:00 klauncher
     1222 ?        00:00:08 kded4
     1225 ?        00:00:01 kglobalaccel
     1234 ?        00:00:00 kactivitymanage
     1235 ?        00:00:00 upowerd
     1250 ?        00:00:01 udisksd
     1255 ?        00:00:00 kwrapper4
     1257 ?        00:00:01 ksmserver
     1267 ?        00:01:35 kwin
     1275 ?        00:03:53 plasma-desktop
     1276 ?        00:00:01 baloo_file
     1284 ?        00:00:00 bluetoothd
     1295 ?        00:00:00 kuiserver
     1306 ?        00:00:02 krunner
     1309 ?        00:00:01 kmix
     1316 ?        00:00:08 konsole
     1318 ?        00:00:42 pulseaudio
     1319 ?        00:00:00 rtkit-daemon
     1320 ?        00:00:22 kwrite
     1335 ?        00:00:00 polkit-kde-auth
     1336 ?        00:00:00 klipper
     1340 pts/0    00:00:00 bash
     1385 ?        00:00:01 filezilla
     1386 ?        00:31:18 firefox
     1390 ?        00:00:00 knotify4
     1404 ?        00:00:00 gvfsd
     1416 ?        00:00:00 gvfsd-fuse
     1500 ?        00:00:00 at-spi-bus-laun
     1505 ?        00:00:01 kmozillahelper
     1577 ?        00:00:00 dhclient
     1695 ?        00:00:02 ksysguardd
     2011 ?        00:00:00 kworker/2:0
     2037 ?        00:00:11 packagekitd
     2680 ?        00:00:00 kworker/3:1
     2684 ?        00:00:00 kworker/2:1
     2749 ?        00:00:00 kworker/0:1
     2803 ?        00:00:01 kworker/u8:0
     2839 ?        00:00:00 kworker/u8:2
     2841 ?        00:00:00 kworker/1:0
     2892 ?        00:00:00 kworker/1:1
     2897 ?        00:00:00 kworker/2:2
     2901 ?        00:00:00 kworker/u8:1
     2912 pts/0    00:00:00 ps
    martin@linux-o61y:~> kill PID 2037 
    bash: kill: PID: Die Argumente müssen Prozess- oder Jobbezeichnungen sein.
    bash: kill: (2037) - Die Operation ist nicht erlaubt
    martin@linux-o61y:~> PID 2037 
    If 'PID' is not a typo you can use command-not-found to lookup the package that contains it, like this:
        cnf PID
    martin@linux-o61y:~> kill PID 2037
    dilbert ;-)
    Wordpress-development - a Toolset: wpgear.org

  5. #5

    Default Re: how can i stop PackageKit -

    Quote Originally Posted by dilbertone View Post
    should i run kill PID2037
    Yes, as even zypper tells you already.

    But, see my previous reply.

  6. #6
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,769

    Default Re: how can i stop PackageKit -

    DO NOT use the letters PID that is not part of the command only indicates you need to put the PID number there not the letters PID.

  7. #7
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,211
    Blog Entries
    15

    Default Re: how can i stop PackageKit -

    On Tue 30 Jun 2015 08:06:02 PM CDT, dilbertone wrote:


    hello

    many thanks - this is very helpful

    guess that the pid is 2037

    should i run kill PID2037

    see the following
    Code:
    2037 ?        00:00:11 packagekitd
    Hi
    You also need to add the signal (hint kill -l <--that's a lower case
    L).... and if you know the name, then can use pidof...
    Code:
    kill -9 `pidof packagekitd`
    
    or
    
    kill -9 2037
    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel
    3.12.43-52.6-default If you find this post helpful and are logged into
    the web interface, please show your appreciation and click on the star
    below... Thanks!


  8. #8

    Default Re: how can i stop PackageKit -

    Rather than go through complicated steps to find the PID of the process you want to end, you can just use pkill, followed by the name of the process you want to end, so in this case
    Code:
    pkill packagekit
    should work.

  9. #9

    Default Re: how can i stop PackageKit -

    Quote Originally Posted by sdfghjk123 View Post
    Rather than go through complicated steps to find the PID of the process you want to end, you can just use pkill, followed by the name of the process you want to end, so in this case
    Code:
    pkill packagekit
    should work.
    The process is called "packagekitd", so it should be:
    Code:
    pkill packagekitd
    (run as root)

    Or "killall packagekitd" would work as well, as I mentioned already.

    Still, it should not be necessary at all. Packagekitd should quit itself after 15 seconds of inactivity.
    If it doesn't something else is wrong.

  10. #10
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,769

    Default Re: how can i stop PackageKit -

    I have had packagekit be reluctant to stop several times on the last several updates. It seems to hang. Only why is to kill it. Logging out and back in just restarts the program. This last time it did actually do the update on logging back in but in the recent past I had to kill it.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •