$ sudo kpackagekit --updates Error: "/var/tmp/kdecache-jd" is owned by uid 1008 instead of uid 0. Error: "/tmp/kde-jd" is owned by uid 1008 instead of uid 0. Error: "/tmp/kde-jd" is owned by uid 1008 instead of uid 0. Error: "/tmp/ksocket-jd" is owned by uid 1008 instead of uid 0. kdeinit4: Shutting down running client. klauncher: Exiting on signal 15 kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Error: "/tmp/ksocket-jd" is owned by uid 1008 instead of uid 0. Error: "/tmp/kde-jd" is owned by uid 1008 instead of uid 0. kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so Error: "/var/tmp/kdecache-jd" is owned by uid 1008 instead of uid 0. Error: "/tmp/kde-jd" is owned by uid 1008 instead of uid 0. Failed to connect to socket /tmp/fam-skroot- kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so kbuildsycoca4 running... Error: "/var/tmp/kdecache-jd" is owned by uid 1008 instead of uid 0. Error: "/var/tmp/kdecache-jd" is owned by uid 1008 instead of uid 0. kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit4: preparing to launch /usr/bin/knotify4 Error: "/var/tmp/kdecache-jd" is owned by uid 1008 instead of uid 0. Error: "/tmp/kde-jd" is owned by uid 1008 instead of uid 0. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) knotify(18043) KNotify::event: 1 ref= 0 Then an error banner popped up, and clicked on Details: Error Type: Error Value: invalid literal for int() with base 10: 'ALL' File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3398, in main() File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3395, in main backend.dispatcher(sys.argv[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 723, in dispatcher self.dispatch_command(args[0], args[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 610, in dispatch_command self.get_updates(filters) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2547, in get_updates self._check_init() File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2971, in _check_init root = self.yumbase._media_find_root(repo.mediaid) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3301, in _media_find_root disc_number_tmp = int(lines[3].strip()) So , I thought if I su - root and run kpackagekit --updates, it will not complain about the kdecache-jd ownership. So: $ su - root Password: # kpackagekit --updates <unknown program name>(18090)/: KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." <unknown program name>(18089)/: KUniqueApplication: Pipe closed unexpectedly. disc_number_tmp = int(lines[3].strip()) So I looked for dbus daemon: # ps -ef | grep -i debus | grep -v grep dbus 1036 1 0 Jul08 ? 00:00:02 dbus-daemon --system gdm 1597 1 0 Jul08 ? 00:00:00 /usr/bin/dbus-launch --exit-with jd 1710 1 0 Jul08 ? 00:00:00 dbus-launch --sh-syntax --exit-w jd 1711 1 0 Jul08 ? 00:00:00 /bin/dbus-daemon --fork --print- root 18007 1 0 20:27 pts/2 00:00:00 dbus-launch --autolaunch 16591fa root 18008 1 0 20:27 ? 00:00:00 /bin/dbus-daemon --fork --print- Guess I will not be using kpackagekit for a while. It's version number 0.6 tell me it is still in a nascent stage. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
