FS#7623 - amarok won't start, no error written (backtrace posted)
Attached to Project:
Arch Linux
Opened by Martin Pelikan (sztorkie) - Monday, 16 July 2007, 08:12 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 25 April 2008, 15:57 GMT
Opened by Martin Pelikan (sztorkie) - Monday, 16 July 2007, 08:12 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 25 April 2008, 15:57 GMT
|
Details
Description:
This situation happened to me on my last Gentoo on desktop, then everything worked fine on Fedora 7 and now I installed Arch Linux, where it happened back: I install amarok, run it and nothing happens (just splash screen shows and after clicking on it disappears): -- bash-3.2$ amarok Amarok: [Loader] Starting amarokapp.. Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp. Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has gone wrong? -- so, I make backtrace using gdb -- (gdb) thread apply all bt Thread 3 (Thread -1253926000 (LWP 20377)): #0 0xb7f41410 in __kernel_vsyscall () #1 0xb6174423 in fcntl () from /lib/libpthread.so.0 #2 0xb7e85823 in threadLockingTest () from /opt/kde/lib/libamarok.so.0 #3 0xb616d4a2 in start_thread () from /lib/libpthread.so.0 #4 0xb5c82b1e in clone () from /lib/libc.so.6 Thread 2 (Thread -1262318704 (LWP 20378)): #0 0xb7f41410 in __kernel_vsyscall () #1 0xb6174423 in fcntl () from /lib/libpthread.so.0 #2 0xb7e85823 in threadLockingTest () from /opt/kde/lib/libamarok.so.0 #3 0xb616d4a2 in start_thread () from /lib/libpthread.so.0 #4 0xb5c82b1e in clone () from /lib/libc.so.6 Thread 1 (Thread -1248504112 (LWP 20345)): #0 0xb7f41410 in __kernel_vsyscall () #1 0xb616e855 in pthread_join () from /lib/libpthread.so.0 #2 0xb7e8c521 in findLockInfo () from /opt/kde/lib/libamarok.so.0 #3 0xb7e8c6c1 in allocateUnixFile () from /opt/kde/lib/libamarok.so.0 #4 0xb7ea6455 in sqlite3PagerOpen () from /opt/kde/lib/libamarok.so.0 #5 0xb7ea6659 in sqlite3BtreeOpen () from /opt/kde/lib/libamarok.so.0 #6 0xb7ea68a0 in sqlite3BtreeFactory () from /opt/kde/lib/libamarok.so.0 #7 0xb7ea6b20 in openDatabase () from /opt/kde/lib/libamarok.so.0 #8 0xb7b3a8dd in SqliteConnection::SqliteConnection () from /opt/kde/lib/libamarok.so.0 #9 0xb7b3d620 in CollectionDB::getMyConnection () from /opt/kde/lib/libamarok.so.0 #10 0xb7b5721d in CollectionDB::initialize () from /opt/kde/lib/libamarok.so.0 #11 0xb7b592f2 in CollectionDB::CollectionDB () from /opt/kde/lib/libamarok.so.0 #12 0xb7b599ea in CollectionDB::instance () from /opt/kde/lib/libamarok.so.0 #13 0xb7c8e575 in MoodServer::MoodServer () from /opt/kde/lib/libamarok.so.0 #14 0xb7c8e67a in MoodServer::instance () from /opt/kde/lib/libamarok.so.0 #15 0xb7b07705 in App::continueInit () from /opt/kde/lib/libamarok.so.0 #16 0xb7b08288 in App::qt_invoke () from /opt/kde/lib/libamarok.so.0 #17 0xb662e61d in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3 #18 0xb69519ee in QSignal::signal () from /opt/qt/lib/libqt-mt.so.3 #19 0xb6649db7 in QSignal::activate () from /opt/qt/lib/libqt-mt.so.3 #20 0xb6650e53 in QSingleShotTimer::event () from /opt/qt/lib/libqt-mt.so.3 #21 0xb65d0cba in QApplication::internalNotify () from /opt/qt/lib/libqt-mt.so.3 #22 0xb65d1896 in QApplication::notify () from /opt/qt/lib/libqt-mt.so.3 #23 0xb6cc0112 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4 #24 0xb65c605e in QEventLoop::activateTimers () from /opt/qt/lib/libqt-mt.so.3 #25 0xb6580b74 in QEventLoop::processEvents () from /opt/qt/lib/libqt-mt.so.3 #26 0xb65e7150 in QEventLoop::enterLoop () from /opt/qt/lib/libqt-mt.so.3 #27 0xb65e6fe6 in QEventLoop::exec () from /opt/qt/lib/libqt-mt.so.3 #28 0xb65d071f in QApplication::exec () from /opt/qt/lib/libqt-mt.so.3 #29 0x0804c017 in ?? () #30 0xbfea5d10 in ?? () #31 0xbfea5ea4 in ?? () #32 0x080695a6 in ?? () #33 0x08069595 in ?? () #34 0x00000000 in ?? () #0 0xb7f41410 in __kernel_vsyscall () (gdb) -- Am I doing something wrong? People from KDE bugs wrote me: -- Yes, the problem is because your environment is not setup properly. Likely, conflicting libraries of compiled against and installed. Please seek assistance from archlinux. You probably need to issue a 'pacman -Syu'. -- Additional info: * package version(s) bash-3.2$ amarok -v Qt: 3.3.8 KDE: 3.5.7 Amarok: 1.4.6 kernel: 2.6.21-ARCH #1 SMP * config and/or log files etc. Steps to reproduce: just install it on intel pentium4 (prescott, socket478), i875 chipset, ati radeon 9600, soundcard onboard i8x0 |
This task depends upon
Closed by Aaron Griffin (phrakture)
Friday, 25 April 2008, 15:57 GMT
Reason for closing: None
Additional comments about closing: See comments. NFS locking issue.
Friday, 25 April 2008, 15:57 GMT
Reason for closing: None
Additional comments about closing: See comments. NFS locking issue.
my user is member of groups audio, users
have you checked if another user (without an amarok config under ~/) has the same problem? maybe you should ask also on the archlinux mailinglist or forum... i do not see this to be a packaging bug.
In Fedora everything (even sqlite via nfs) worked fine...
But anyway, I made a symlink .kde/apps/amarok -> /tmp/amarok, and I will convert it to postgresql.
I think it's just worth warning other people against running their Amarok on NFS. And according to what I've read, similar problems are caused more applications than I thought, but in NFS documentation there's just a little note about it (file locking problems).
Thank you for your help.