Bug 201774 - crash on kpackagekit
Summary: crash on kpackagekit
Status: RESOLVED DUPLICATE of bug 218200
Alias: None
Product: kpackagekit
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-28 15:09 UTC by karim
Modified: 2010-08-18 23:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description karim 2009-07-28 15:09:04 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Fedora RPMs

Cette pile des appels apparaît être inutilisable.
C'est probablement dû au fait que votre paquetage a été construit d'une manière qui empêche de créer des piles d'appels corrects, ou que le cadre de pile a été sérieusement corrompu dans l'incident.

[Thread debugging using libthread_db enabled]
0x0000003d4eaa3e30 in __nanosleep_nocancel () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f3da2ec7820 (LWP 2223))]

Thread 1 (Thread 0x7f3da2ec7820 (LWP 2223)):
#0  0x0000003d4eaa3e30 in __nanosleep_nocancel () from /lib64/libc.so.6
#1  0x0000003d4eaa3cb0 in sleep () from /lib64/libc.so.6
#2  0x0000003f5d26604c in ?? () from /usr/lib64/libkdeui.so.5
#3  0x0000003f5d266a75 in KCrash::defaultCrashHandler(int) () from /usr/lib64/libkdeui.so.5
#4  <signal handler called>
#5  0x0000003d4ea332f5 in raise () from /lib64/libc.so.6
#6  0x0000003d4ea34b20 in abort () from /lib64/libc.so.6
#7  0x0000003f57c2a435 in ?? () from /lib64/libdbus-1.so.3
#8  0x0000003f57c2629d in ?? () from /lib64/libdbus-1.so.3
#9  0x0000003f57c11989 in dbus_set_error () from /lib64/libdbus-1.so.3
#10 0x0000003f5ec05a72 in ?? () from /usr/lib64/libpolkit-dbus.so.2
#11 0x0000003f5ec05cef in polkit_auth_obtain () from /usr/lib64/libpolkit-dbus.so.2
#12 0x0000003f58c2d445 in PackageKit::PolkitClient::getAuth(QString const&) () from /usr/lib64/libpackagekit-qt.so.11
#13 0x0000003f58c10b74 in PackageKit::Client::updatePackages(QList<PackageKit::Package*> const&) () from /usr/lib64/libpackagekit-qt.so.11
#14 0x000000000040e1f0 in _start (
Comment 1 Dario Andres 2009-07-28 17:05:58 UTC
This could be related to bug 198706. 
- What were you doing when the application crashed?
- What is your version of the "packagekit", "packagekit-qt" and "kpackagekit" packages ?
Thanks
Comment 2 karim 2009-07-28 17:42:54 UTC
Hello Dario Andres ,
before it crashed, I uploaded the compiz  rpms  using this command line :

# yum install compiz compiz-fusion ccsm fusion-icon compiz-fusion-extras

then, few minutes later  my system updated automatically.

I have to say that I was doing nothing. only  conqueror navigator  was 
opened for the internet.
The version of :
packagekit-qt is : 0.4.8        revision : 2fc11 for x 86_64
Kpackagekit is : 0.4.1.1.    revision : 1.fc11
packagekit : 0.4.8              revision  : 2fc11

thank's

best regards




Dario Andres a écrit :
> https://bugs.kde.org/show_bug.cgi?id=201774
>
>
> Dario Andres <andresbajotierra@gmail.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |andresbajotierra@gmail.com
>
>
>
>
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2009-07-28 17:05:58 ---
> This could be related to bug 198706. 
> - What were you doing when the application crashed?
> - What is your version of the "packagekit", "packagekit-qt" and "kpackagekit"
> packages ?
> Thanks
>
>
Comment 3 Daniel Nicoletti 2009-07-30 14:43:23 UTC
Maybe some dependent package was updated, maybe packagekit it self..
sometimes when this package is updated it makes the running app crash
dunno why yet..
might be this...
Comment 4 Dario Andres 2009-12-11 12:49:01 UTC
This could be related to bug 218200. Thanks
Comment 5 Daniel Nicoletti 2010-08-18 23:43:09 UTC

*** This bug has been marked as a duplicate of bug 218200 ***