The PackageKit Project dialog keeps popping up to prompt for the root password on my Debian Jessie desktop, apparently assuming that the logged in account has root permissions or knows the root password Is there someway to disable it in the desktop settings?

I just ran the following command without fully knowing what it would do:

sudo pacman -S packagekit-qt6 flatpack fwupd

And now my KDE Discover Store is broken. Whenever I try to update something in KDE Discover, I get the following error popups: Can someone please help me how to remove this and revert back to before? I need my KDE Discover to work again. --- I tried searching and found to run sudo pacman -R packagekit-qt6, but that didn't work. I get the following errors: error: cachyos-znver4: signature from "CachyOS " is invalid error: cachyos-core-znver4: signature from "CachyOS " is invalid error: cachyos-extra-znver4: signature from "CachyOS " is invalid error: cachyos: signature from "CachyOS " is invalid error: failed to init transaction (unable to lock database) error: could not lock database: File exists if you're sure a package manager is not already running, you can remove /var/lib/pacman/db.lck

I would like the help of someone with more experience to understand the differences and how those 5 things are connected: libzypp, YaST, Zypper, PackageKit and Gnome Software Center. Here is my take away from a day of research: - libzypp: the backend package management library that powers applications like YaST, zypper and the openSUSE implementation of PackageKit - YaST: it's a system configuration tool that happens to allow the management of dependencies through libzypp. It provides both a graphical interface (GTK) and an interface through the terminal (not sure what it's used here) - Zypp: the official command-line package manager of Open SUSE - PackageKit: that's where things get a little fuzzy for me. This seems to be a package manager abstraction - its supposed to abstract all the differences between apt, zypper, yum, etc - Gnome Software Center: it's a graphical interface (GTK) to install dependencies through package kit - so it's supposed to work with all distros, regardless of the underline package manager used If I understood this correct: - Why don't I see the apps installed through YaST in the Gnome Software Center and vice-versa? - Why would I want to keep Gnome Software Center installed if the previous point (^) doesn't happen? To me this thing just seems cluttered

I am trying to figure out why an application updated. Apparently it shouldn't update automatically, but did, and this caused problems for me. When I go into the logs at /var/log/apt I see the record of what happened, but I don't fully understand it Start-Date: 2024-02-26 19:09:09 Commandline: packagekit role='update-packages' Install: #list of stuff that was installed Upgrade: # list of stuff that was upgraded End-Date: 2024-02-26 19:10:07 My question is what does "Commandline: packagekit role='update-packages'" mean? Naively, this looks like I issued the update command but there is nothing that looks at all relevant in the command history. Is this something I did, or something that happened automatically?

sudo apt-get install sshpass Reading package lists... Done Building dependency tree... Done Reading state information... Done Package sshpass is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

My disk is full and I found that PackageKit uses more than 12GB in cache folder. So I found that I can delete the cached files. I used the following command [unix@localhost ~]$ sudo pkcon -c 8000000 refresh
Refreshing cache [=========================]
Loading cache [=========================]
Downloading repository information[=========================]
Finished [=========================]
Fatal error: Error when getting information for file “/var/cache/PackageKit/28/metadata
/phracek-PyCharm/repodata/36899dd8cb609ee8604863268813e848e6d48b2448bad93a4037e14dcad30dcd-appstream.xml”: No such
file or directory But I have this error about missing files and folders. Could some one help me to fix it?

My usual process of installing things on NixOS is changing my configuration.nix , executing nixos-rebuild switch, rebooting, and choosing the new (last) OS generation. I know it is also possible to install packages via nix-shell (but I have never used it). What are the differences between the two options? When one is more appropriate than the other?

Fresh install of Fedora 34. Home software updater is packagekit behind, though gnome-packagekit says gnome-software and all comoonents like fwupd are not installed on the machine, dnf says the same. Gnome-software installs stuff, however it does not uninstall some default apps, it says could not remove, package missing, although the packages successfully runs. It removes Flatpaks normally though. The interesting thing is that dnf and packagekit also say that such package is not installed. To remove it for real on the system, I need fo install it eith dnf or packagekit but not gnome-software, because there it exists and it actually works prior to installing it, after that I sill remove it by dnf kr packagekit (again gnome-softsare does not remove them) , only then gnome software will have launch button removed and inly an uninstall button with red left, which again does not work, bur upon reboot the package is gone succesfully from the store. I tried refreshing and uodating and cleaning caches on both dnf and packagekit, I also tried btrfs rollbacks, to no avail. Additionally, I think I had packages saying that are inztalled through dnf, but not actually as the bins were missing, this could have been fixed with dnf history rollback, which I am not sure if should be the case.

Recently I've been having the issue that some rpm commands (e.g. # rpm --rebuilddb fail due to this error: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission denied) It also seems this affects PackageKit as whenever I try to open GNOME Software's updates tab it says "Timeout was reached". To me, it seems like some rpm transaction was aborted while running and now the lock file is stuck there. I would just remove the file, but I'm not sure how to tell whether it's safe. [neboula@shock ~]$ file /var/lib/rpm/.rpm.lock /var/lib/rpm/.rpm.lock: empty [neboula@shock ~]$ pidof dnf [neboula@shock ~]$ pidof rpm This looks like it's safe, but I also have packagekitd (always) running, so I'm wondering: How can I safely remove this file given my circumstances?

When [PackageKit](https://en.wikipedia.org/wiki/PackageKit) has updates fetched for installation and you use the Gnome GUI to shut down the machine, it is possible to set a checkbox to install updates before shut down. How can this be accomplished from command line without root? Example purpose: automating the execution of custom commands before shut down.

**Update - I'm on Fedora 25 now but the issue is still unsolved.** I have Fedora 25 Workstation on my laptop. The internet access is through proxy server only. I have successfully configured proxy settings for dnf and wget. I can install and updates packages using dnf from terminal. wget and firefox also work. But Gnome Software Center and curl do not work. Everytime I try to install something from software center, I get the error > Curl error (7): Couldn't connect to server for > https://mirrors.fedoraproject.org/metalink?repo=fedora-24&arch=x86_64 > [Failed to connect to mirrors.fedoraproject.org port 443: Connection > refused] What I have tried so far: 1 : Set proxy settings using dconf-editor **(Source) ** 2 : Manually add proxy info to /etc/PackageKit/PackageKit.conf **(Source1) ** **(Source2) ** 3 : Add proxy info to ~/.bash_profile, ~/.curlrc, /etc/profile **(Source) ** None of these have worked. How do I get Gnome Software Center working?

(I have installed systemd-coredump) What would send a QUIT signal to debconf-communicate? Since the backtrace does not include raise() / kill(), I guess I can assume this fatal signal was sent to debconf-communicate by some other running program? man 7 signal says that signal QUIT was originally intended for "Quit from keyboard". The distinction from signal INT ("Interrupt from keyboard") is that QUIT deliberately dumps core. Presumably this was a debugging technique. SIGINT is sent by the key combination Ctrl+C. SIGQUIT is sent by Ctrl+\\. However I seem to be getting these core dumps without anyone pressing Ctrl+\\ on an apt command running in a terminal. It seems to be happening (sometimes?) when doing package upgrades with PackageKit. This is a Debian 9 desktop system (GNOME). I don't know what happens at the times when this crash occurs, other than to say the users have not reported any problem :-). The main user is generally good at applying updates, and understands their importance. Due to bugs in Debian which failed to deliver update notifications in the past, the system currently has installed pk-update-icon (with .desktop file patched to auto-start in GNOME) and gnome-packagekit / gpk-update-viewer, in addition to the usual gnome-software.

$ dpkg-query -l packagekit gnome-software gnome-packagekit pk-update-icon debconf dpkg apt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                 Version         Architecture    Description
+++-====================-===============-===============-==============================================
ii  apt                  1.4.9           amd64           commandline package manager
ii  debconf              1.5.61          all             Debian configuration management system
ii  dpkg                 1.18.25         amd64           Debian package management system
ii  gnome-packagekit     3.22.1-2        amd64           Graphical distribution neutral package manager
ii  gnome-software       3.22.5-1        amd64           Software Center for GNOME
ii  packagekit           1.1.5-2+deb9u1  amd64           Provides a package management service
ii  pk-update-icon       2.0.0-2         amd64           Displays an update-notification tray icon

$ sudo coredumpctl --no-pager
TIME                            PID   UID   GID SIG COREFILE EXE
Thu 2018-07-12 10:13:09 BST    5059  1005  1009   3 missing  /usr/bin/perl
Sat 2018-07-14 11:16:38 BST    2346  1005  1009   3 missing  /usr/bin/perl
...
Wed 2019-05-22 14:35:32 BST    2535  1005  1009   3 missing  /usr/bin/perl
Thu 2019-05-23 11:39:52 BST    2311  1005  1009   3 missing  /usr/bin/perl
Sat 2019-05-25 10:16:47 BST    2445  1005  1009   3 missing  /usr/bin/perl
Thu 2019-05-30 08:16:50 BST    2497  1005  1009   3 missing  /usr/bin/perl
Fri 2019-05-31 11:10:27 BST    2404  1005  1009   3 missing  /usr/bin/perl
Thu 2019-06-06 15:47:50 BST    4282  1005  1009   3 missing  /usr/bin/perl
Fri 2019-06-07 10:16:49 BST    2640  1005  1009   3 missing  /usr/bin/perl

$ sudo coredumpctl info 2640
           PID: 2640 (debconf-communi)
           UID: 1005 (YYY)
           GID: 1009 (YYY)
        Signal: 3 (QUIT)
     Timestamp: Fri 2019-06-07 10:16:49 BST (4 days ago)
  Command Line: /usr/bin/perl -w /usr/bin/debconf-communicate
    Executable: /usr/bin/perl
 Control Group: /user.slice/user-1005.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1005.slice
       Session: 2
     Owner UID: 1005 (YYY)
       Boot ID: 37f2efd8086a42b5a39144b5411b1523
    Machine ID: 35fb9280fa2847946f17a060542fd617
      Hostname: drystone
       Storage: /var/lib/systemd/coredump/core.debconf-communi.1005.37f2efd8086a42b5a39144b5411b1523.2640.1559899009000000000000.lz4 (inaccessible)
       Message: Process 2640 (debconf-communi) of user 1005 dumped core.
                
                Stack trace of thread 2640:
                #0  0x00007fa8db86a210 read (libpthread.so.0)
                #1  0x00005598354afa7d PerlIOUnix_read (perl)
                #2  0x00005598354b2fcf PerlIOBuf_fill (perl)
                #3  0x00005598354b1658 Perl_PerlIO_fill (perl)
                #4  0x00005598354b2e80 PerlIOBase_read (perl)
                #5  0x00005598354b4e08 PerlIO_getc (perl)
                #6  0x000055983544b2a5 Perl_sv_gets (perl)
                #7  0x000055983542d376 Perl_do_readline (perl)
                #8  0x0000559835428aa6 Perl_runops_standard (perl)
                #9  0x00005598353ae8a9 perl_run (perl)
                #10 0x0000559835387a5d main (perl)
                #11 0x00007fa8db4db2e1 __libc_start_main (libc.so.6)
                #12 0x0000559835387a9a _start (perl)

$ sudo journalctl --since="2019-06-07"
...
Jun 07 10:16:05 drystone PackageKit: get-updates transaction /21666_bacedcbd from uid 1005 finished with success after 657ms
Jun 07 10:16:09 drystone PackageKit: new update-packages transaction /21669_aeeccbac scheduled from uid 1005
Jun 07 10:16:10 drystone PackageKit: get-update-detail transaction /21667_cebbebab from uid 1005 finished with success after 5406ms
Jun 07 10:16:11 drystone PackageKit: get-details transaction /21668_dabdcebe from uid 1005 finished with success after 395ms
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package evolution;3.22.6-1+deb9u2;amd64;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package evolution-common;3.22.6-1+deb9u2;all;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package evolution-plugins;3.22.6-1+deb9u2;amd64;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package libevolution;3.22.6-1+deb9u2;amd64;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package qemu-kvm;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package qemu-system-common;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package qemu-system-x86;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: in /21669_aeeccbac for update-packages package qemu-utils;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was updating for uid 1005
Jun 07 10:16:11 drystone PackageKit: update-packages transaction /21669_aeeccbac from uid 1005 finished with success after 585ms
Jun 07 10:16:11 drystone PackageKit: uid 1005 is trying to obtain org.freedesktop.packagekit.system-update auth (only_trusted:1)
Jun 07 10:16:11 drystone gnome-shell: JS LOG: polkitAuthenticationAgent: Received 2 identities that can be used for authentication. Only considering one.
Jun 07 10:16:16 drystone polkitd(authority=local): Operator of unix-session:2 successfully authenticated as unix-user:YYY to gain TEMPORARY authorization for action org.freedesktop.packagekit.system-update
Jun 07 10:16:16 drystone PackageKit: new update-packages transaction /21670_adbeabac scheduled from uid 1005
Jun 07 10:16:16 drystone PackageKit: uid 1005 obtained auth for org.freedesktop.packagekit.system-update
Jun 07 10:16:38 drystone packagekitd: PARENT process running...
Jun 07 10:16:41 drystone gnome-software-service.desktop: 09:16:41:0610 As  failed to rescan: No valid root node specified
Jun 07 10:16:41 drystone gnome-software-service.desktop: 09:16:41:0617 As  failed to rescan: Failed to parse /usr/share/applications/evolution.desktop file: cannot process file of type application/x-deskto
Jun 07 10:16:41 drystone gnome-software-service.desktop: 09:16:41:0642 As  failed to rescan: No valid root node specified
Jun 07 10:16:41 drystone gnome-software-service.desktop: 09:16:41:0646 As  failed to rescan: Failed to parse /usr/share/applications/evolution.desktop.dpkg-tmp file: cannot process file of type text/plain
Jun 07 10:16:42 drystone gnome-software-service.desktop: 09:16:42:0406 As  failed to rescan: No valid root node specified
Jun 07 10:16:42 drystone gnome-software-service.desktop: 09:16:42:0410 As  failed to rescan: No valid root node specified
Jun 07 10:16:42 drystone gnome-software-service.desktop: 09:16:42:0410 As  failed to rescan: No valid root node specified
Jun 07 10:16:42 drystone gnome-software-service.desktop: 09:16:42:0414 As  failed to rescan: No valid root node specified
Jun 07 10:16:42 drystone gnome-software-service.desktop: 09:16:42:0414 As  failed to rescan: No valid root node specified
Jun 07 10:16:44 drystone gnome-software-service.desktop: 09:16:44:0075 As  failed to rescan: No valid root node specified
Jun 07 10:16:44 drystone gnome-software-service.desktop: 09:16:44:0078 As  failed to rescan: No valid root node specified
Jun 07 10:16:44 drystone gnome-software-service.desktop: 09:16:44:0082 As  failed to rescan: No valid root node specified
Jun 07 10:16:49 drystone packagekitd: Parent finished...
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-system-common;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package evolution-plugins;3.22.6-1+deb9u2;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package evolution;3.22.6-1+deb9u2;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package libevolution;3.22.6-1+deb9u2;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package evolution-common;3.22.6-1+deb9u2;all;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-kvm;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-system-x86;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-utils;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package evolution-common;3.22.6-1+deb9u2;all;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package libglib2.0-0;2.50.3-2;amd64;installed:debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-utils;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package libevolution;3.22.6-1+deb9u2;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-system-common;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-system-x86;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package evolution;3.22.6-1+deb9u2;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package evolution-plugins;3.22.6-1+deb9u2;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: in /21670_adbeabac for update-packages package qemu-kvm;1:2.8+dfsg-6+deb9u7;amd64;debian-stable-main was installing for uid 1005
Jun 07 10:16:49 drystone PackageKit: update-packages transaction /21670_adbeabac from uid 1005 finished with success after 33545ms
Jun 07 10:16:49 drystone gpk-update-view: Source ID 1825 was not found when attempting to remove it
Jun 07 10:16:49 drystone systemd: Created slice system-systemd\x2dcoredump.slice.
Jun 07 10:16:49 drystone systemd: Started Process Core Dump (PID 3620/UID 0).
Jun 07 10:16:49 drystone systemd-coredump: Process 2640 (debconf-communi) of user 1005 dumped core.
                                                 
                                                 Stack trace of thread 2640:
                                                 #0  0x00007fa8db86a210 read (libpthread.so.0)
                                                 #1  0x00005598354afa7d PerlIOUnix_read (perl)
                                                 #2  0x00005598354b2fcf PerlIOBuf_fill (perl)
                                                 #3  0x00005598354b1658 Perl_PerlIO_fill (perl)
                                                 #4  0x00005598354b2e80 PerlIOBase_read (perl)
                                                 #5  0x00005598354b4e08 PerlIO_getc (perl)
                                                 #6  0x000055983544b2a5 Perl_sv_gets (perl)
                                                 #7  0x000055983542d376 Perl_do_readline (perl)
                                                 #8  0x0000559835428aa6 Perl_runops_standard (perl)
                                                 #9  0x00005598353ae8a9 perl_run (perl)
                                                 #10 0x0000559835387a5d main (perl)
                                                 #11 0x00007fa8db4db2e1 __libc_start_main (libc.so.6)
                                                 #12 0x0000559835387a9a _start (perl)
Jun 07 10:16:50 drystone PackageKit: get-updates transaction /21671_baceadea from uid 1005 finished with success after 597ms
Jun 07 10:16:50 drystone gpk-update-view: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
Jun 07 10:16:52 drystone PackageKit: get-updates transaction /21672_cdcdcbca from uid 1005 finished with success after 884ms
Jun 07 10:16:52 drystone gpk-update-view: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
Jun 07 10:16:55 drystone gpk-update-view: g_application_release: assertion 'application->priv->use_count > 0' failed
Jun 07 10:16:57 drystone PackageKit: get-updates transaction /21673_bdabdecd from uid 1005 finished with success after 638ms
Jun 07 10:17:01 drystone CRON: pam_env(cron:session): Unable to open env file: /etc/environment: No such file or directory
Jun 07 10:17:01 drystone CRON: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 07 10:17:01 drystone CRON: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 07 10:17:01 drystone CRON: pam_unix(cron:session): session closed for user root
Jun 07 10:24:14 drystone systemd: Starting Cleanup of Temporary Directories...
Jun 07 10:24:14 drystone systemd: Started Cleanup of Temporary Directories.

I ran pkcon update force. I noticed PackageKit is logging about only_trusted:0. That is, an operation where the only_trusted option is disabled. Even though I did not pass --allow-untrusted to pkcon. PackageKit: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) So PackageKit is writing a log message about allowing untrusted packages. I did not want it to do that. I did not ask it do that. Why is it logging this message? Is there a problem in PackageKit? $ sudo systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled) Active: active (running) since Mon 2019-04-08 12:34:58 BST; 1min 29s ago Main PID: 19819 (packagekitd) Tasks: 3 (limit: 4915) Memory: 192.7M CGroup: /system.slice/packagekit.service └─19819 /usr/libexec/packagekitd Apr 08 12:34:58 alan-laptop PackageKit: daemon start Apr 08 12:34:58 alan-laptop systemd: Starting PackageKit Daemon... Apr 08 12:34:58 alan-laptop systemd: Started PackageKit Daemon. Apr 08 12:34:58 alan-laptop PackageKit: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Apr 08 12:34:58 alan-laptop PackageKit: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Apr 08 12:35:09 alan-laptop PackageKit: refresh-cache transaction /17652_eabaebee from uid 1000 finished with success after 11018ms $ rpm -q PackageKit PackageKit-1.1.12-2.fc29.x86_64

sudo apt-get install numactl E: Problem executing scripts APT::Update::Post-Invoke-Success '/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null' E: Sub-process returned an error code How to fix it?

This annoying dialog "Authentication Required" started to pop up recently, just after every login to KDE, demanding root password to refresh system repositories. After a minute or so it disappears on it's own, followed by a "update failed" tray notification, which also disappears soon. It's not a blocker, just annoying and looking unprofessionally. Please, how to get rid of this? It must be something to do with KDE/Gnome interoperability because: * it started to appear only after I had installed Gnome alongside my primary KDE * no Authentication Required pops up when login to Gnome * the dialog looks like it is from Gnome (KDE has a differently looking password UI) The pop-up dialog says (in case you cannot see the screenshot above):

Authentication is required to refresh the system repositories.
Action: Refresh system repositories
        org.freedesktop.packagekit.system-sources-refresh
Vendor: The PackageKit project.
polkit.subject-pid: xxxx
polkit.caller-pid:  xxxx

I'm using Kali Linux, latest edition and in the last two weeks it has auto-updated packages. I wasn't aware of this until I saw a notification bubble and when I checked out the GNOME PackageKit updater, it showed updates on three days when I had only booted up the computer and did not explicitly update any packages myself. I already looked for the apt-get Periodic configuration setting to see if that was the cause and could not find anything in /etc/apt-get/ that suggested apt was handling the automatic updating setting. I also looked at the settings for PackageKit and it doesn't have anything related to automatic updates. At this point I'm lost and I'm not sure how to turn off automatic updates in Kali Linux. For a security-oriented distro it's extremely frustrating that it would just use up bandwidth and make contact with the outside world automatically.

I'm wondering if Packagekit's command pkcon refresh also pulls in information about updateable packages from Debian mirrors - like: apt update does - or if it just updates Packagekit's internal cache of avaible updates. The man page just says > Refresh the cached information about avaible updates.

tl;dr: We build an RPM package that automatically detect dependencies (no Requires in .spec file). How can I remove dependencies from this RPM package. Long story:-> I'm shipping the dynamic libraries along with the binary but RPMs automatic dependencies mechanism obviously lists that shipped libraries also as dependencies. How to avoid this?

I noticed that GNOME Software on my Fedora 24 installation only shows packages that are already installed (even in the *featured* and *editor's picks* sections). I also can't search for new packages to install. Here's a screenshot of the *Graphics* category. On the left side, it shows only installed packages. On the right side (from another computer), it shows the correct list: I found out that GNOME Software is a frontend for PackageKit, so I tried to use the CLI (pkcon). However, it also doesn't find most of the programs. For example, I wanted to search for *Shotwell* using the CLI. This is the output: [user ~]$ pkcon search name shotwell Searching by name [=========================] Finished [=========================] [user ~]$ On the other computer, pkcon finds the package: [user ~]$ pkcon search name shotwell Searching by name [=========================] Starting [=========================] Finished [=========================] Available shotwell-0.23.5-1.fc24.i686 (updates) A photo organizer for the GNOME desktop Available shotwell-0.23.5-1.fc24.x86_64 (updates) A photo organizer for the GNOME desktop Available shotwell-0.23.1-1.fc24.x86_64 (fedora) A photo organizer for the GNOME desktop [user ~]$ **How can I fix PackageKit to find all packages again?** ---------- **Edit:** Output of dnf repolist: repo id repo name status Dropbox Dropbox Repository 4 *fedora Fedora 24 - x86_64 49.722 google-chrome google-chrome 3 rpmfusion-free RPM Fusion for Fedora 24 - Free 352 rpmfusion-free-updates RPM Fusion for Fedora 24 - Free - Updates 277 rpmfusion-nonfree RPM Fusion for Fedora 24 - Nonfree 89 rpmfusion-nonfree-updates RPM Fusion for Fedora 24 - Nonfree - Updates 127 *updates Fedora 24 - x86_64 - Updates 9.817

> [etckeeper] hooks into package managers like apt to automatically commit changes made to /etc during package upgrades [to a git repository] Fedora uses libhif as a backend for PackageKit tools, such as GNOME Software. libhif doesn't use the command-line package manager, dnf, which leads to some confusing situations. E.g. PackageKit and dnf don't share caches, at least for the moment. Question: If I install etckeeper on Fedora, will it make the automatic commits before/after package installs/upgrades, if these actions are performed using PackageKit as opposed to using dnf on the command line?