Summary: | Amarok crashes at first start [@ MySqlStorage::initThreadInitializer] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | tom |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | deszynski, michal, morvau, ralf-engels, valir |
Priority: | NOR | Keywords: | regression |
Version: | 2.3.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
tom
2010-08-15 11:19:55 UTC
So this is a one-time crash that you can't reproduce? Looks like a badly initialized Database. I can confirm it too. Amarok crashes once everytime I restart kubuntu. After that it is ok to the next system restart. Piotr, do you have a backtrace? It might be a different issue... Created attachment 50673 [details]
New crash information added by DrKonqi
amarok (2.3.1) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3
- What I was doing when the application crashed:
I switched the display from external LCD (1920x1200) to internal laptop display (1440x900), Amarok crashed immediatelly after I started it.
The distro is Chakra GNU/Linux (Arch Linux & KDE4 based)
-- Backtrace (Reduced):
#7 0x00007f8cf0e21714 in KConfigGroup::KConfigGroup(KSharedPtr<KSharedConfig> const&, char const*) () from /usr/lib/libkdecore.so.5
#8 0x00007f8cf0e351ca in KSharedConfig::groupImpl(QByteArray const&) () from /usr/lib/libkdecore.so.5
#9 0x00007f8cf0e2078c in KConfigBase::group(char const*) () from /usr/lib/libkdecore.so.5
#10 0x00007f8ccee82c3c in MySqlStorage::initThreadInitializer() () from /usr/lib/kde4/amarok_collection-mysqlservercollection.so
#11 0x00007f8ccee881a5 in MySqlServerStorage::query(QString const&) () from /usr/lib/kde4/amarok_collection-mysqlservercollection.so
Thank you for the feedback. Setting status correctly, sorry for the noise. Hi, sorry I didn't provide backtrace, but after purgeing and reinstalling Amarok problem disappeared. If I'll be able to reproduce bug again, I'll post the trace right away. *** Bug 250867 has been marked as a duplicate of this bug. *** Hi all, we need a new backtrace to be able to reproduce it. For 2.4 a lot has changed for the SqlCollection. Also the comment from Piotr indicates that a newer version fixes this problem so I will remove the release_blocker keyword for this error. Changing status to waitingforinfo. Closing for lack of feedback. This is most likely solved now Created attachment 77482 [details]
New crash information added by DrKonqi
amarok (2.7.0) on KDE Platform 4.10.00 using Qt 4.8.2
- What I was doing when the application crashed:
I just start the computer with amarok autolaunch. Amarok crashed without any action of me on the computer.
-- Backtrace (Reduced):
#8 0x005fe9cb in qstrcmp (str1=..., str2=...) at tools/qbytearray.cpp:346
#9 0x002b250f in operator< (k2=..., k1=...) at ../../kdecore/config/kconfigdata.h:122
#10 qMapLessThanKey<KEntryKey> (key2=..., key1=...) at /usr/include/qt4/QtCore/qmap.h:107
#11 findNode (akey=..., this=0x8624390) at /usr/include/qt4/QtCore/qmap.h:487
#12 find (akey=..., this=0x8624390) at /usr/include/qt4/QtCore/qmap.h:608
(In reply to comment #12) > Created attachment 77482 [details] > New crash information added by DrKonqi > > amarok (2.7.0) on KDE Platform 4.10.00 using Qt 4.8.2 > > - What I was doing when the application crashed: > > I just start the computer with amarok autolaunch. Amarok crashed without any > action of me on the computer. > > -- Backtrace (Reduced): > #8 0x005fe9cb in qstrcmp (str1=..., str2=...) at tools/qbytearray.cpp:346 > #9 0x002b250f in operator< (k2=..., k1=...) at > ../../kdecore/config/kconfigdata.h:122 > #10 qMapLessThanKey<KEntryKey> (key2=..., key1=...) at > /usr/include/qt4/QtCore/qmap.h:107 > #11 findNode (akey=..., this=0x8624390) at /usr/include/qt4/QtCore/qmap.h:487 > #12 find (akey=..., this=0x8624390) at /usr/include/qt4/QtCore/qmap.h:608 Your backtrace has nothing in common with this bug, please file a new one if this is reproducible. |