muon-installer crash

[Thijs]

Currently bugs.kde.org is minorly flooded with muon-installer crashes. All from Ubuntu 11.10, all from the past few 2 days. See https://bugs.kde.org/show_bug.cgi?id=291262 and the backtrace pasted below.

-- Backtrace:
Application: Centre de logiciels Muon (muon-installer), signal: Segmentation
fault
[Current thread is 1 (Thread 0xb7771930 (LWP 4314))]

Thread 2 (Thread 0xb568bb70 (LWP 4315)):
#0 0x00e41d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1 0x003037d5 in do_gettime (frac=0xb568b020, sec=0xb568b018) at
tools/qelapsedtimer_unix.cpp:123
#2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3 0x003d64b6 in QTimerInfoList::updateCurrentTime (this=0x911cb44) at
kernel/qeventdispatcher_unix.cpp:339
#4 0x003d680a in QTimerInfoList::timerWait (this=0x911cb44, tm=...) at
kernel/qeventdispatcher_unix.cpp:442
#5 0x003d5053 in timerSourcePrepareHelper (src=<optimized out>,
timeout=0xb568b12c) at kernel/qeventdispatcher_glib.cpp:136
#6 0x003d50ed in timerSourcePrepare (source=0x911cb10, timeout=<optimized
out>) at kernel/qeventdispatcher_glib.cpp:169
#7 0x050ef88c in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#8 0x050f0637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9 0x050f0c2a in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x003d5b37 in QEventDispatcherGlib::processEvents (this=0x91315d8,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0x003a61dd in QEventLoop::processEvents (this=0xb568b2b0, flags=...) at
kernel/qeventloop.cpp:149
#12 0x003a6421 in QEventLoop::exec (this=0xb568b2b0, flags=...) at
kernel/qeventloop.cpp:201
#13 0x002a990b in QThread::exec (this=0x8fe6028) at thread/qthread.cpp:498
#14 0x00386e2d in QInotifyFileSystemWatcherEngine::run (this=0x8fe6028) at
io/qfilesystemwatcher_inotify.cpp:248
#15 0x002ac7b3 in QThreadPrivate::start (arg=0x8fe6028) at
thread/qthread_unix.cpp:331
#16 0x00e29d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0x062ef0ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb7771930 (LWP 4314)):
[KCrash Handler]
#7 0x00300e11 in QtPrivate::QStringList_contains (that=0xbfcb3f74, str=...,
cs=Qt::CaseSensitive) at tools/qstringlist.cpp:318
#8 0x08066812 in contains (cs=Qt::CaseSensitive, str=..., this=0xbfcb3f74) at
/usr/include/qt4/QtCore/qstringlist.h:171
#9 ApplicationWindow::populateViews (this=0x90d8d48) at
/build/buildd/muon-1.2.1/installer/ApplicationWindow.cpp:229
#10 0x0806a194 in ApplicationWindow::qt_metacall (this=0x90d8d48,
_c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfcb4194) at
/build/buildd/muon-1.2.1/obj-i686-linux-gnu/installer/ApplicationWindow.moc:113
#11 0x003adb7d in metacall (argv=0xbfcb4194, idx=86,
cl=QMetaObject::InvokeMetaMethod, object=0x90d8d48) at
kernel/qmetaobject.cpp:237
#12 QMetaObject::metacall (object=0x90d8d48, cl=QMetaObject::InvokeMetaMethod,
idx=86, argv=0xbfcb4194) at kernel/qmetaobject.cpp:232
#13 0x003bca6a in QMetaObject::activate (sender=0x9166a60, m=0x8085040,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3278
#14 0x0805de57 in ApplicationBackend::appBackendReady (this=0x9166a60) at
/build/buildd/muon-1.2.1/obj-i686-linux-gnu/installer/moc_ApplicationBackend.cpp:127
#15 0x0805e1d5 in ApplicationBackend::qt_metacall (this=0x9166a60,
_c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfcb42d8) at
/build/buildd/muon-1.2.1/obj-i686-linux-gnu/installer/moc_ApplicationBackend.cpp:109
#16 0x003adb7d in metacall (argv=0xbfcb42d8, idx=12,
cl=QMetaObject::InvokeMetaMethod, object=0x9166a60) at
kernel/qmetaobject.cpp:237
#17 QMetaObject::metacall (object=0x9166a60, cl=QMetaObject::InvokeMetaMethod,
idx=12, argv=0xbfcb42d8) at kernel/qmetaobject.cpp:232
#18 0x003bca6a in QMetaObject::activate (sender=0x90d8d48, m=0x80950c0,
local_signal_index=0, argv=0xbfcb42d8) at kernel/qobject.cpp:3278
#19 0x00e687c5 in MuonMainWindow::backendReady (this=0x90d8d48, _t1=0x903eac8)
at /build/buildd/muon-1.2.1/obj-i686-linux-gnu/libmuon/MuonMainWindow.moc:168
#20 0x00e68933 in MuonMainWindow::initObject (this=0x90d8d48) at
/build/buildd/muon-1.2.1/libmuon/MuonMainWindow.cpp:79
#21 0x080654fc in ApplicationWindow::initObject (this=0x90d8d48) at
/build/buildd/muon-1.2.1/installer/ApplicationWindow.cpp:116
#22 0x0806a09f in ApplicationWindow::qt_metacall (this=0x90d8d48,
_c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfcb4404) at
/build/buildd/muon-1.2.1/obj-i686-linux-gnu/installer/ApplicationWindow.moc:104
#23 0x003adb7d in metacall (argv=0xbfcb4404, idx=77,
cl=QMetaObject::InvokeMetaMethod, object=0x90d8d48) at
kernel/qmetaobject.cpp:237
#24 QMetaObject::metacall (object=0x90d8d48, cl=QMetaObject::InvokeMetaMethod,
idx=77, argv=0xbfcb4404) at kernel/qmetaobject.cpp:232
#25 0x003bca6a in QMetaObject::activate (sender=0x9133dd8, m=0x4dd238,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3278
#26 0x003c4375 in QSingleShotTimer::timeout (this=0x9133dd8) at
.moc/release-shared/qtimer.moc:82
#27 0x003c442c in QSingleShotTimer::timerEvent (this=0x9133dd8) at
kernel/qtimer.cpp:308
#28 0x003bf994 in QObject::event (this=0x9133dd8, e=0xbfcb47fc) at
kernel/qobject.cpp:1181
#29 0x01513d54 in notify_helper (e=0xbfcb47fc, receiver=0x9133dd8,
this=0x8fd6ec0) at kernel/qapplication.cpp:4486
#30 QApplicationPrivate::notify_helper (this=0x8fd6ec0, receiver=0x9133dd8,
e=0xbfcb47fc) at kernel/qapplication.cpp:4458
#31 0x01519103 in QApplication::notify (this=0xbfcb47fc, receiver=0x9133dd8,
e=0xbfcb47fc) at kernel/qapplication.cpp:3886
#32 0x00b9f681 in KApplication::notify (this=0xbfcb4b10, receiver=0x9133dd8,
event=0xbfcb47fc) at ../../kdeui/kernel/kapplication.cpp:311
#33 0x003a719e in QCoreApplication::notifyInternal (this=0xbfcb4b10,
receiver=0x9133dd8, event=0xbfcb47fc) at kernel/qcoreapplication.cpp:787
#34 0x003d7c10 in sendEvent (event=0xbfcb47fc, receiver=<optimized out>) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#35 QTimerInfoList::activateTimers (this=0x8fd2e44) at
kernel/qeventdispatcher_unix.cpp:603
#36 0x003d5122 in timerSourceDispatch (source=0x8fd2e10) at
kernel/qeventdispatcher_glib.cpp:184
#37 0x050f025f in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#38 0x050f0990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#39 0x050f0c2a in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#40 0x003d5ada in QEventDispatcherGlib::processEvents (this=0x8fb4238,
flags=...) at kernel/qeventdispatcher_glib.cpp:422
#41 0x015cbe3a in QGuiEventDispatcherGlib::processEvents (this=0x8fb4238,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#42 0x003a61dd in QEventLoop::processEvents (this=0xbfcb4a74, flags=...) at
kernel/qeventloop.cpp:149
#43 0x003a6421 in QEventLoop::exec (this=0xbfcb4a74, flags=...) at
kernel/qeventloop.cpp:201
#44 0x003ab19d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#45 0x015118f4 in QApplication::exec () at kernel/qapplication.cpp:3760
#46 0x0805db86 in main (argc=) at
/build/buildd/muon-1.2.1/installer/main.cpp:61

[Jonathan Thomas (echidnaman)]

Muon's not changed at all in oneiric since oneiric was released. It's probably something else, but I don't know what at the moment so I'll keep the bug here for the time being.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Tommy Quist (linforcer)]

Besides not being changed, it also happened to me on a clean install, with having "install updates" turned off during install.
My best bet is this is related to package lists or servers, but then you'd expect more software to act up, not to mention purging and reinstalling muon-installer would help, which it doesn't.

[Chris L. (horkinmidget)]

Duplicated on two fresh installs.

When trying to apply updates after the first reboot. Muon package manager locked up at 55%, had to kill the process.

Workaround:

 sudo vi /etc/apt/sources.list "or use the text editor of your preference to edit the file"
   uncomment these two lines
   # deb http://archive.canonical.com/ubuntu oneiric partner
   # deb-src http://archive.canonical.com/ubuntu oneiric partner

  sudo dpkg --configure -a
  sudo apt-get update
  sudo update-apt-xapian-index

[Robert Simmons (rsimmons0)]

I have run into this in a clean install on bare metal in addition to a clean install in virtualbox. It hangs at a different percentage each time, but I think that's just because the two installs were days apart and the package selection was different the second time.

I have a slightly different workaround from the one in the previous post, but it is very similar. I just entered the following from terminal:

sudo apt-get update
sudo apt-get upgrade

This is only a workaround that works if you have NOT hit the bug. This works instead of even trying to use the GUI tools in muon.

[Jonathan Thomas (echidnaman)]

Not the same bug.

[Bill Hayes (wm-j-hayes)]

I have this bug too.

Further, exactly the same bug affects KPackageKit on fresh installs of (K)Ubuntu 11.04, related?

[Elamine Jouan (jouan51)]

A fix as been proposed in a french ubuntu forum : http://forum.ubuntu-fr.org/viewtopic.php?id=790301
it worked for me.
launch muon
in configuration, source configuration
check everything exept cd-rom in the 'other software' tab
in the 'update' tab, check 'suggested update' (the only one uncheck by default)

I work in a french version of ubuntu so i hope the translation is good enough

[Mauricio (darthsteel)]

This happens in the 64bit version of Kubuntu, whenever it runs muon.

[Andrew Grant (andrewgrant31)]

This what I did to get Muon Software Center to work. It's not perfect, but it does work - no crashes so far...:
Open Muon Package Manager --> Settings --> Configure Software Sources --> Password
Then, on the Kubuntu Software tab ( first page), "unclick" <Proprietary drivers for devices (restricted)>, followed by unclicking both <Software restricted by copyright or legal issues (multiverse)> and <Source Code>. Next tab, "Other Software", make sure nothing in this section is selected. Next tab, "Statistics", make sure <Submit statistical information> is not selected. Close and allow Muon Package Manager to refresh it's sources.
Now, right click the K-Menu button and select "Edit Applications". Find Muon Software Center in the System sub-menu. Change the command (on the right side of the screen) to "muon-installer" (without the quotes). Click Save and reboot. the Muon Software Center should be working.
It's an awful lot of work to get something that did work "out of the box" to work in a sort of satisfactory way.

[Daniel Letzeisen (dtl131)]

Fix Committed.
http://bugs.kde.org/show_bug.cgi?id=291262

[R (Chandra) Chandrasekhar (chandra)]

I am on fresh install of Kubuntu 12.04 on AMD64. Muon stoppedworking after an upgrade and when I do

`apt-get install --reinstall muon`

I get this error

******
Reading en translations from /var/lib/apt/lists/ubuntuarchive.hnsdc.com_ubuntu_dists_precise_restricted_i18n_Translation-en: done.
Traceback (most recent call last):
  File "/usr/sbin/update-apt-xapian-index", line 106, in <module>
    indexer.incrementalUpdate()
  File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 683, in incrementalUpdate
    self.updateIndex(dbpath)
  File "/usr/lib/python2.7/dist-packages/axi/indexer.py", line 633, in updateIndex
    db = xapian.WritableDatabase(pathname, xapian.DB_CREATE_OR_OPEN)
  File "/usr/lib/python2.7/dist-packages/xapian/__init__.py", line 4298, in __init__
    _xapian.WritableDatabase_swiginit(self,_xapian.new_WritableDatabase(*args))
xapian.DatabaseCorruptError: Cannot open tables at consistent revisions
*****
Can someone tell me how to get the functionality of muon back again please?

Thanks.

[R (Chandra) Chandrasekhar (chandra)]

Following up on my report

https://bugs.launchpad.net/ubuntu/+source/muon/+bug/915235/comments/12

I re-installed Kubuntu 12.04 from the alternate CD and can now report that the problem is no more.

Perhaps the first installation was corrupted in some way that is not reproducible.

Sorry for the false alarm.