| Summary: | update manager crashed as I was searching for nm-app | ||
|---|---|---|---|
| Product: | [Unmaintained] kpackagekit | Reporter: | Bruno Vernay <brunovern.a> |
| Component: | general | Assignee: | Steven M. Parrish <smparrish> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | andresbajotierra, dantti12 |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Is the crash reproduceable at will ? Thanks I didn't reproduce it, but I think that it may due to a lack of memory. By the way, I didn't have the will to search and fill a bug, but this one is reproductible: 1/ install a "broken" package with dpkg (ex: dpkg -i HandBrake-0.9.3-Ubuntu_GUI_amd64.deb ) 2/ the install should give an error (otherwise you are too lucky) 3/ launch the Package Manager : it takes 100% CPU and is unusable. 4/ launch synaptic: it proposes to solve the problem. Bruno On Wed, Jul 29, 2009 at 3:00 AM, Dario Andres<andresbajotierra@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=201814 > > > Dario Andres <andresbajotierra@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |andresbajotierra@gmail.com > > > > > --- Comment #1 from Dario Andres <andresbajotierra gmail com> 2009-07-29 03:00:28 --- > Is the crash reproduceable at will ? Thanks > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > Hmm the first problem is a bit hard to understand what happened, did you do anything with the kpackagekit so this back trace come out? About the second problem, kpackagekit has none to do with it it's all your backend distro fault. For the first problem, I didn't do anything special with kpackagekit, apart operating with an overloaded system ... About the second one, even if the package state is broken, kpackagekit shouldn't take 100% CPU and being unusable. Specially when compared to Synaptic which propose to resolve the underlying problem. Bruno On Wed, Jul 29, 2009 at 3:32 PM, Daniel Nicoletti<dantti85-kde@yahoo.com.br> wrote: > https://bugs.kde.org/show_bug.cgi?id=201814 > > > Daniel Nicoletti <dantti85-kde@yahoo.com.br> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |NEEDSINFO > Resolution| |REMIND > > > > > --- Comment #3 from Daniel Nicoletti <dantti85-kde yahoo com br> 2009-07-29 15:32:05 --- > Hmm the first problem is a bit hard to understand what > happened, did you do anything with the kpackagekit so this > back trace come out? > About the second problem, kpackagekit has none to do with it > it's all your backend distro fault. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > Ok, let's put names in things KPackageKit a simple GUI front end to PackageKit PackageKit a layer between KPackageKit and a backend that in you case is apt Backend the piece of code that does the job. So which process takes 100% CPU (ie, packagekitd, kpackagekit or aptBackend.py)? "Layers. Onions have layers. Ogres have layers. Onions have layers. You get it?" Right, so definitively it is not kpackagekit nor packagekitd, but the backend in python Exactly: /usr/lib/packagekit/aptDBUSBackend.py and its PID is always changing, as if it were called again and again. Anyway, thanks for the explaination. Bruno On Wed, Jul 29, 2009 at 5:41 PM, Daniel Nicoletti<dantti85-kde@yahoo.com.br> wrote: > https://bugs.kde.org/show_bug.cgi?id=201814 > > --- Comment #5 from Daniel Nicoletti <dantti85-kde yahoo com br> 2009-07-29 17:41:57 --- > Ok, let's put names in things > KPackageKit a simple GUI front end to PackageKit > PackageKit a layer between KPackageKit and a backend > that in you case is apt > Backend the piece of code that does the job. > So which process takes 100% CPU (ie, packagekitd, kpackagekit or > aptBackend.py)? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > Ok, so better report it at launchpad, the first one i still have no clue.. Thanks. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Application that crashed: systemsettings Version of the application: 1.0 KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-13-generic x86_64 Distribution: Ubuntu 9.04 -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #5 QAction::activate (this=0x0, event=QAction::Trigger) at kernel/qaction.h:67 #6 0x00007f6b2498ec40 in ?? () from /usr/lib/kde4/kcm_kpk_addrm.so #7 0x00007f6b2fa1d78d in QApplicationPrivate::notify_helper (this=0x1b09180, receiver=0x1ffb8c0, e=0x7fff39d9a1d0) at kernel/qapplication.cpp:4084 #8 0x00007f6b2fa268bf in QApplication::notify (this=<value optimized out>, receiver=0x1ffb8c0, e=0x7fff39d9a1d0) at kernel/qapplication.cpp:3690 #9 0x00007f6b308e971b in KApplication::notify (this=0x7fff39d9b380, receiver=0x1ffb6c0, event=0x7fff39d9a1d0) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302 #10 0x00007f6b2ee6375c in QCoreApplication::notifyInternal (this=0x7fff39d9b380, receiver=0x1ffb6c0, event=0x7fff39d9a1d0) at kernel/qcoreapplication.cpp:602 #11 0x00007f6b2fab26b4 in QKeyMapper::sendKeyEvent (keyWidget=0x1ffb6c0, grab=<value optimized out>, type=QEvent::KeyPress, code=16777220, modifiers={i = 970564608}, text=@0x7fff39d9a3f0, autorepeat=false, count=1, nativeScanCode=36, nativeVirtualKey=65293, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1675 #12 0x00007f6b2fab4a12 in QKeyMapperPrivate::translateKeyEvent (this=0x1b423a0, keyWidget=0x1ffb6c0, event=0x7fff39d9afc0, grab=false) at kernel/qkeymapper_x11.cpp:1645 #13 0x00007f6b2fa8d5bd in QApplication::x11ProcessEvent (this=0x7fff39d9b380, event=0x7fff39d9afc0) at kernel/qapplication_x11.cpp:3436 #14 0x00007f6b2fab6464 in x11EventSourceDispatch (s=0x1b0cf60, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #15 0x00007f6b2ad2020a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0x00007f6b2ad238e0 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0x00007f6b2ad23a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #18 0x00007f6b2ee8ce6f in QEventDispatcherGlib::processEvents (this=0x1ae1b50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323 #19 0x00007f6b2fab5bef in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #20 0x00007f6b2ee62002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 970568368}) at kernel/qeventloop.cpp:149 #21 0x00007f6b2ee623cd in QEventLoop::exec (this=0x7fff39d9b2f0, flags={i = 970568448}) at kernel/qeventloop.cpp:200 #22 0x00007f6b2ee64694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880 #23 0x000000000040cb6a in _start () Reported using DrKonqi