crash when searching ampache

Bug #367737 reported by AZ
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)

Bug Description

After setting up an ampache server (debian lenny), amarok crashes when try to search from the internet => ampache view. Happening in jaunty i686.


[Switching to Thread 0xb3f16710 (LWP 10653)]
QString::operator= (this=0x44, other=@0xbfccd9a8) at tools/qstring.cpp:1130
1130 tools/qstring.cpp: No such file or directory.
 in tools/qstring.cpp
Current language: auto; currently c++
(gdb) bt
#0 QString::operator= (this=0x44, other=@0xbfccd9a8) at tools/qstring.cpp:1130
#1 0xb7956b67 in CollectionTreeItemModelBase::setCurrentFilter () from /usr/lib/
#2 0xb795fcb4 in ?? () from /usr/lib/
#3 0xb79660fb in ?? () from /usr/lib/
#4 0xb6a45ca8 in QMetaObject::activate (sender=0xbc21b88, from_signal_index=27, to_signal_index=27, argv=0xbfccdabc) at kernel/qobject.cpp:3069
#5 0xb6a46932 in QMetaObject::activate (sender=0xbc21b88, m=0xb7793648, local_signal_index=0, argv=0xbfccdabc) at kernel/qobject.cpp:3143
#6 0xb733f8b3 in QLineEdit::textChanged (this=0xbc21b88, _t1=@0xbfccdb04) at .moc/release-shared/moc_qlineedit.cpp:228
#7 0xb7344f0a in QLineEditPrivate::finishChange (this=0xbc21bb0, validateFromState=0, update=false, edited=true) at widgets/qlineedit.cpp:2975
#8 0xb734595b in QLineEdit::insert (this=0xbc21b88, newText=@0xbfccdb60) at widgets/qlineedit.cpp:1408
#9 0xb7347547 in QLineEdit::keyPressEvent (this=0xbc21b88, event=0xbfcce1dc) at widgets/qlineedit.cpp:2176
#10 0xb7eda795 in KLineEdit::keyPressEvent (this=0xbc21b88, e=0xbfcce1dc) at /build/buildd/kde4libs-4.2.2/kdeui/widgets/klineedit.cpp:892
#11 0xb6f57a93 in QWidget::event (this=0xbc21b88, event=0xbfcce1dc) at kernel/qwidget.cpp:7551
#12 0xb7345345 in QLineEdit::event (this=0xbc21b88, e=0xbfcce1dc) at widgets/qlineedit.cpp:1681
#13 0xb7edbcea in KLineEdit::event (this=0xbc21b88, ev=0xbfcce1dc) at /build/buildd/kde4libs-4.2.2/kdeui/widgets/klineedit.cpp:1309
#14 0xb6f00f2c in QApplicationPrivate::notify_helper (this=0x9a82d20, receiver=0xbc21b88, e=0xbfcce1dc) at kernel/qapplication.cpp:4084
#15 0xb6f0a2eb in QApplication::notify (this=0xbfccec84, receiver=0xbc21b88, e=0xbfcce1dc) at kernel/qapplication.cpp:3690
#16 0xb7dfe94d in KApplication::notify (this=0xbfccec84, receiver=0xbc21b88, event=0xbfcce1dc)
    at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#17 0xb6a2fa3b in QCoreApplication::notifyInternal (this=0xbfccec84, receiver=0xbc21b88, event=0xbfcce1dc) at kernel/qcoreapplication.cpp:602
#18 0xb6f01e0e in qt_sendSpontaneousEvent (receiver=0xbc21b88, event=0xbfccd901) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#19 0xb6f9f0a0 in QKeyMapper::sendKeyEvent (keyWidget=0xbc21b88, grab=false, type=QEvent::KeyPress, code=84, modifiers={i = -1077091544}, text=@0xbfcce354,
    autorepeat=<value optimized out>, count=<value optimized out>, nativeScanCode=28, nativeVirtualKey=116, nativeModifiers=0)
    at kernel/qkeymapper_x11.cpp:1675
#20 0xb6fa126e in QKeyMapperPrivate::translateKeyEvent (this=0x9aa9988, keyWidget=0xbc21b88, event=0xbfcce9bc, grab=184) at kernel/qkeymapper_x11.cpp:1645
#21 0xb6f76dfe in QApplication::x11ProcessEvent (this=0xbfccec84, event=0xbfcce9bc) at kernel/qapplication_x11.cpp:3436
#22 0xb6fa2cfa in x11EventSourceDispatch (s=0x9a80168, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#23 0xb4454b88 in IA__g_main_context_dispatch (context=0x9a7ef10) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#24 0xb44580eb in g_main_context_iterate (context=0x9a7ef10, block=1, dispatch=1, self=0x9a82c80) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#25 0xb4458268 in IA__g_main_context_iteration (context=0x9a7ef10, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#26 0xb6a5b438 in QEventDispatcherGlib::processEvents (this=0x9a633f8, flags={i = -1077089416}) at kernel/qeventdispatcher_glib.cpp:323
#27 0xb6fa23f5 in QGuiEventDispatcherGlib::processEvents (this=0x9a633f8, flags={i = -1077089368}) at kernel/qguieventdispatcher_glib.cpp:202
#28 0xb6a2e06a in QEventLoop::processEvents (this=0xbfccec20, flags={i = -1077089304}) at kernel/qeventloop.cpp:149
#29 0xb6a2e4aa in QEventLoop::exec (this=0xbfccec20, flags={i = -1077089240}) at kernel/qeventloop.cpp:200
#30 0xb6a30959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#31 0xb6f00da7 in QApplication::exec () at kernel/qapplication.cpp:3553
#32 0x0814c4b2 in _start ()

Revision history for this message
Charlie_Smotherman (cjsmo) wrote :

AZ ,

The Ampache guys really suggest that you upgrade to ampache-3.5 or at least use ampache-3.4.4 which is in "squeeze" and to use at least version 2.1 of Amarok.


Amarok nightly builds


Revision history for this message
Charlie_Smotherman (cjsmo) wrote :

Ohh yea, please ensure that your ACL's for Ampache are setup correctly have a look at


Revision history for this message
AZ (m-dev) wrote :

Thanks for that quick reply, I already considered the wiki source when setting up the ampache.
I have no problem with amarok not working with not up-to-date version of ampache, nevertheless
I should not crash at all. Sadly, amarok 2.1 is not in jaunty and ampache 3.4.4 is not in lenny
so upgrading would result in a lot more administrative overhead for checking for security updates.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

If you haven't already, could you please install amarok-dbg and get a new backtrace? I see a few lines missing from libamaroklib. Thanks in advance. :)

Changed in amarok (Ubuntu):
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Upstream bug, which is closed at the moment:

Revision history for this message
AZ (m-dev) wrote :

Well I see those lines missing too but I already had amarok-dbg installed when creating the backtrace.

summary: - creash when searching ampache
+ crash when searching ampache
Revision history for this message
Charlie_Smotherman (cjsmo) wrote :

Have you enabled logging for ampache? and is it telling you anything?


Revision history for this message
AZ (m-dev) wrote :

Depends on #368470 .

Changed in amarok:
status: Unknown → Invalid
Revision history for this message
AZ (m-dev) wrote :

Why is this bug invalid? Amarok is crashing although it should not.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Needs a backtrace.

Changed in amarok (Ubuntu):
status: Incomplete → Invalid
Changed in amarok:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.