Translate

Image of Advanced Programming in the UNIX Environment, Second Edition (Addison-Wesley Professional Computing Series)
Image of XSLT 2.0 and XPath 2.0 Programmer's Reference (Programmer to Programmer)
Image of Beginning Google Maps API 3
Image of Operating System Concepts

Exploring PackageKit's GNOME Software

Fedora 20 (codename Heisenbug) Beta was released on November 12th 2013. One of the accepted system wide change proposals for this release was to replace the existing gnome-packagekit frontends (gpk-update-viewer and gpk-application) with a new unified and more user-centric application. A quick high-level overview of PackageKit first. It is essentially a framework which consists of frontends such as yum which communicate with backends such as PackageKit-yum via an abstraction layer based on D-Bus. Essentially, it is a set of APIs exported through a D-Bus interface. Glib, qt and python and other language bindings are available. This abstraction layer enables applications

PackageKit D-Bus Abstraction Layer

PackageKit uses an abstraction layer to allow a session user to manage software packages in a secure way. This abstraction layer is based on D-Bus. Essentially, it is a set of APIs exported through a D-Bus interface. Glib, qt and python and other language bindings are available. This abstraction layer enables applications to perform high-level package operations such as add or remove a package without having to know much about package management. PolicyKit (AKA PolKit) is incorporated to provide a fine grained policy mechanism for users. D-Bus has two connections types (buses): System and Session. System interfaces normally run as

Using The PackageKit Console Frontend

PackageKit is essentially a framework which consists of frontends such as yum which communicate with backends such as PackageKit-yum via an abstraction layer based on D-Bus. Essentially, it is a set of APIs exported through a D-Bus interface. Glib, qt and python and other language bindings are available. This abstraction layer enables applications to perform high-level package operations such as add or remove a package without having to know much about package management. PolicyKit (AKA PolKit) is incorporated to provide a fine grained policy mechanism for users. PackageKit is not Fedora-specific. A number of Linux distributions use it. PackageKit was

Fedora 18/19, PackageKit, KSplice and Failed Backend Message

A couple of months ago, the PackageKit utility on my Fedora 18 system stopped working. YUM continued to work so I had an easy workaround and did not really try to trace down the problem and fix it. I assumed that a future version of a PackageKit RPM would fix the problem. Recently I did a FedUp upgrade to Fedora 19 and the problem persisted so I decided the time had come to investigate the root cause of the problem and fix it. Here is how the problem manifested itself: A quick check of Fedora Bugzilla convinced me that the

Disable PackageKit Update Check after Yum

Ever get an error message like the following when you use yum to install an RPM package or a group of RPM packages, and then, within a minute or two, attempt to use yum to install another RPM package? # yum groupinstall “Development Tools” Loaded plugins: langpacks, presto, refresh-packagekit Existing lock /var/run/yum.pid: another copy is running as pid 1651. Another app is currently holding the yum lock; waiting for it to exit… The other application is: PackageKit Memory : 114 M RSS (506 MB VSZ) Started: Wed Oct 26 15:11:42 2011 – 00:10 ago State : Running, pid: 1651 Another