Bug 149968 - Integrate PackageKit with KDE, provide a GUI
Summary: Integrate PackageKit with KDE, provide a GUI
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kpackage
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Toivo Pedaste
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-18 11:56 UTC by Roland Wolters
Modified: 2009-12-20 14:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Wolters 2007-09-18 11:56:05 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Fedora RPMs

Currently software/package management in KDE is limited to kpackage which is replaced in almost all distributions by the distribution specific tools. The same is true for other DEs like Gnome and XFCE, btw.

The Project PackageKit [1] tries to solve this problem by abstracting away the used backends and providing a single API for a given frontend. Despite other advantages like asynchronous operations and non-locking of the backend with PackageKit it becomes possible to provide a single GUI integrated with a DE to manage all simple tasks around software management (updates, installation, query, etc.).

Therefore I would like to see PackageKit integrated into KDE to provide a "Phonon of the software managers". A GNOME interface already exists, several backends (conary, yum, apt, box, alpm) are already supported (with others like emerge or libzypp in work) and PackageKit itself is designed around D-Bus and therefore fits to the general idea of today's sdesktop software design.
If PackageKit would be integrated KDE would have a very useful replacement for kpackage.

[1]
http://www.packagekit.org/wiki/index.php/Main_Page
Comment 1 Piotr Pełzowski 2007-09-18 16:07:36 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 Piotr Pełzowski 2008-11-10 14:22:38 UTC
There already exists PackageKit's integration for KDE4. KpackageKit[1] , according to what kpackagekit developers said[2] it will likely by submitted to KDE-svn.

All people interested in Bug 149968 should test Kpackagekit and give feedback to developers :) In site linked under [2] you can see a lot of screenshots, this application is really in a good state now. 

regards

[1] http://www.kde-apps.org/content/show.php/KPackageKit?content=84745
[2] http://polishlinux.org/kde/kpackagekit-interview/
Comment 3 wendigo 2009-01-09 11:18:35 UTC
What i have to do to resolve this? (p.s i'm italian)
------------------------------------------------------------------------------
The application KPackageKit (kpackagekit) crashed and caused the signal 6 (SIGABRT).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were
-------------------------------------------------------------------------------
Applicazione: KPackageKit (kpackagekit), segnale SIGABRT
(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1243162928 (LWP 11483)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb6b31d90 in raise () from /lib/i686/libc.so.6
#8  0xb6b337f8 in abort () from /lib/i686/libc.so.6
#9  0xb625f795 in dbus_malloc () from /lib/libdbus-1.so.3
#10 0xb625af31 in dbus_watch_handle () from /lib/libdbus-1.so.3
#11 0xb6244224 in dbus_set_error () from /lib/libdbus-1.so.3
#12 0xb62790dc in polkit_dbus_error_generate ()
   from /usr/lib/libpolkit-dbus.so.2
#13 0xb6279354 in polkit_auth_obtain () from /usr/lib/libpolkit-dbus.so.2
#14 0xb6d71ed7 in PackageKit::PolkitClient::getAuth ()
   from /usr/lib/libpackagekit-qt.so.2
#15 0xb6d58bec in PackageKit::Client::updatePackages ()
   from /usr/lib/libpackagekit-qt.so.2
#16 0x08050ec4 in _start ()
#17 0x080511f2 in _start ()
#18 0xb784ec8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb784fa95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0xb6d62dfd in PackageKit::Transaction::finished ()
   from /usr/lib/libpackagekit-qt.so.2
#21 0xb6d68ea3 in PackageKit::TransactionPrivate::finished ()
   from /usr/lib/libpackagekit-qt.so.2
#22 0xb6d6acec in PackageKit::TransactionPrivate::qt_metacall ()
   from /usr/lib/libpackagekit-qt.so.2
#23 0xb784ec8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb784fa95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb6d6b4dd in PackageKit::TransactionProxy::Finished ()
   from /usr/lib/libpackagekit-qt.so.2
#26 0xb6d6c82b in PackageKit::TransactionProxy::qt_metacall ()
   from /usr/lib/libpackagekit-qt.so.2
#27 0xb691dce5 in qDBusAddSpyHook () from /usr/lib/libQtDBus.so.4
#28 0xb6925616 in QString::arg () from /usr/lib/libQtDBus.so.4
#29 0xb7849782 in QObject::event () from /usr/lib/libQtCore.so.4
#30 0xb6eecfac in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#31 0xb6ef5205 in QApplication::notify () from /usr/lib/libQtGui.so.4
#32 0xb7d00b91 in KApplication::notify () from /usr/lib/libkdeui.so.5
#33 0xb7839853 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#34 0xb783a535 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#35 0xb783a71c in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#36 0xb786572d in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#37 0xb666a7ca in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#38 0xb666dee8 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#39 0xb666e0a8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#40 0xb786534a in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#41 0xb6f8995a in QX11Info::copyX11Data () from /usr/lib/libQtGui.so.4
#42 0xb7837ec3 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#43 0xb7838081 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#44 0xb783a7f2 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#45 0xb6eece14 in QApplication::exec () from /usr/lib/libQtGui.so.4
#46 0x0804dd09 in _start ()
#47 0xb6b1e5c5 in __libc_start_main () from /lib/i686/libc.so.6
#48 0x0804d581 in _start ()
Comment 4 Piotr Pełzowski 2009-03-24 13:26:58 UTC
@wendigo, if this crash still exist on fresk kde packages (4.2.1) then please submit _another_ bug to kde bugzilla if there is section for kpackagekit.
Comment 5 Dario Andres 2009-12-20 14:00:32 UTC
KPackage was recently removed from KDE SC (since 4.4 beta2) as it was completely broken and unmaintained.

Most of the common GNU/Linux distributions offer their own tools to deal with packages, and KDE is working on an universal package manager replacement named "Shaman" (to superseed KPackageKit)

Closing the KPackage's bug reports as UNMAINTAINED.

Regards