Bug 262084 - Muon crashes when it refreshes the package lists
Summary: Muon crashes when it refreshes the package lists
Status: RESOLVED NOT A BUG
Alias: None
Product: muon
Classification: Applications
Component: muon (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-04 16:13 UTC by Mustafa Muhammad
Modified: 2011-01-05 18:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
sources.list (2.41 KB, application/octet-stream)
2011-01-05 16:09 UTC, Mustafa Muhammad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mustafa Muhammad 2011-01-04 16:13:48 UTC
Application: muon (1.0.90)
KDE Platform Version: 4.5.90 (4.6 RC1)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-11-generic x86_64
Distribution: Ubuntu natty (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

I chose "Check for Updates" and it begun downloading package lists then it crashed

The crash can be reproduced some of the time.

-- Backtrace:
Application: Muon Package Manager (muon), signal: Aborted
[Current thread is 1 (Thread 0x7fd507237780 (LWP 1762))]

Thread 2 (Thread 0x7fd4f1d23700 (LWP 1763)):
#0  0x00007fd503fe04b3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fd4ffd0d1a0 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fd4ffd0d6c9 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fd50471aa26 in QEventDispatcherGlib::processEvents (this=0x2223ba0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007fd5046eeed2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fd5046ef10c in QEventLoop::exec (this=0x7fd4f1d22dd0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fd504606214 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fd5046d13df in QInotifyFileSystemWatcherEngine::run (this=0x213c1b0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fd5046089ce in QThreadPrivate::start (arg=0x213c1b0) at thread/qthread_unix.cpp:285
#9  0x00007fd5001d4d8c in start_thread (arg=0x7fd4f1d23700) at pthread_create.c:304
#10 0x00007fd503fed61d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd507237780 (LWP 1762)):
[KCrash Handler]
#6  0x00007fd503f40ba5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fd503f444f6 in abort () at abort.c:92
#8  0x00007fd50434b7ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#9  0x00007fd504349a36 in ?? () from /usr/lib/libstdc++.so.6
#10 0x00007fd504349a63 in std::terminate() () from /usr/lib/libstdc++.so.6
#11 0x00007fd504349bb6 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#12 0x00007fd5046ef202 in QEventLoop::exec (this=0x7fff726bb020, flags=...) at kernel/qeventloop.cpp:214
#13 0x00007fd5046f351b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#14 0x0000000000418df9 in main (argc=5, argv=<value optimized out>) at /build/buildd/muon-1.0.90/muon/main.cpp:56

This bug may be a duplicate of or related to bug 259007.

Possible duplicates by query: bug 262041, bug 262002, bug 261960, bug 261900, bug 261892.

Reported using DrKonqi
Comment 1 Jonathan Thomas 2011-01-04 19:42:47 UTC
Hi,

Thanks for the report. Unfortunately the backtrace the KDE crash handler produced lacks some information about where the crash occurred. If you could, the following will most likely help me find what's causing this crash:

- Please install muon-dbg and obtain a new backtrace from the KDE crash handler, and paste it here in the bug report.
- Please run muon from the console and also attach the console output to the bug report.
- Please also attach a copy of your /etc/apt/sources.list, since perhaps it could be a bug exposed by a particular repository.

Thanks in advance,
Jonathan
Comment 2 Mustafa Muhammad 2011-01-05 16:09:55 UTC
Created attachment 55611 [details]
sources.list
Comment 3 Mustafa Muhammad 2011-01-05 16:23:42 UTC
Hi,
Its a pleasure to talk to you, you made a GREAT package manager that replaced Synaptic on Qt and KDE, so a big THANK YOU from my heart.

I'd like to point that I am using 1.0.90 and now I noticed that there is a 1.0.95 version on Maverick (already installed it today) but nothing for Natty.
and today Muon refreshed the updates but during update it said "Package: libc-bin
Error: subprocess installed post-installation script returned error exit status 1"

- The package "muon-dbg" is installed, so I can't give more backtrace
- I don't know what is the problem but I couldn't run it from the console:

mustafaa@mas-ubuntu:~$ sudo muon
[sudo] password for mustafaa: 
unnamed app(2044): KUniqueApplication: Cannot find the D-Bus session server:  "/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
" 

unnamed app(2043): KUniqueApplication: Pipe closed unexpectedly. 

mustafaa@mas-ubuntu:~$ sudo -i
root@mas-ubuntu:~# muon
unnamed app(2105): KUniqueApplication: Cannot find the D-Bus session server:  "/bin/dbus-launch terminated abnormally with the following error: No protocol specified
Autolaunch error: X11 initialization failed.
" 

unnamed app(2104): KUniqueApplication: Pipe closed unexpectedly. 

Thanks again for all your efforts
Mustafaa
Comment 4 Jonathan Thomas 2011-01-05 16:29:32 UTC
The errors on updates are a bug in either APT or dpkg themselves, and is being tracked at https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/680328

Thanks for the sources.list. Everything looks standard there so I don't think that could be causing any trouble.

I do want to confirm that that is the command line output from a muon instance that you have run through this crash. (glibc should give more info about the exception in the command line output)
Comment 5 Mustafa Muhammad 2011-01-05 17:38:40 UTC
Thanks for the correction, this output isn't from that Muon instance, I posted it because it didn't run from the console, now I figured out what was the problem: I tried to run it using "sudo".
Comment 6 Jonathan Thomas 2011-01-05 17:40:20 UTC
Oh, yeah. You don't want to run GUI apps as sudo, but with kdesudo or gksu. As long as that was the problem I guess we can close this.
Comment 7 Mustafa Muhammad 2011-01-05 18:00:40 UTC
Yes, you are right, thanks again and sorry for this wrong bug report
Regards