PDA

Visualizza la versione completa : Problemi con amarok


cron
14-12-2006, 20:53
Ciao raga,ho un problemino appunto con amarok 1.3 su mandriva 2006. All'improvviso senza aver disinstallato o modificato niente quando lo avvio si attiva l'icona sulla barra accanto l'orologio ma al momento di richiamarlo va in crash, senza neanche avviarsi per un secondo. L'errore che mi restituisce questo (preso dall'allegato della mail che prepara in automatico kde quando un prog. va in crash):


==== file `which amarokapp` =======
/usr/bin/amarokapp: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped

==== (gdb) bt =====================
Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1238825280 (LWP 5684)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb65b532b in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#2 0x081f8acc in amaroK::Crash::crashHandler ()
#3 <signal handler called>
#4 0xffffe410 in __kernel_vsyscall ()
#5 0xb62c0ef1 in raise () from /lib/tls/libc.so.6
#6 0xb62c283b in abort () from /lib/tls/libc.so.6
#7 0xb72cc9c3 in kdbgstream::flush () from /usr/lib/libkdecore.so.4
#8 0xb77fd965 in virtual thunk to KIO::Scheduler::~Scheduler$delete() ()
from /usr/lib/libkio.so.4
#9 0xbfd008c0 in ?? ()
#10 0xbfd00888 in ?? ()
#11 0xffffffff in ?? ()
#12 0xb64a66f1 in operator delete () from /usr/lib/libstdc++.so.6
#13 0xb77a14ff in KIO::Scheduler::_scheduleJob () from /usr/lib/libkio.so.4
#14 0x081a325a in QMap<int, QString>::operator[] ()
#15 0x081a3f3f in QMap<int, QString>::operator[] ()
#16 0xb6ca11bf in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb70e7401 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xbfd00a04 in ?? ()
#19 0x00000000 in ?? ()
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb65b532b in __waitpid_nocancel () from /lib/tls/libpthread.so.0
No symbol table info available.
#2 0x081f8acc in amaroK::Crash::crashHandler ()
No symbol table info available.
#3 <signal handler called>
No symbol table info available.
#4 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#5 0xb62c0ef1 in raise () from /lib/tls/libc.so.6
No symbol table info available.
#6 0xb62c283b in abort () from /lib/tls/libc.so.6
No symbol table info available.
#7 0xb72cc9c3 in kdbgstream::flush () from /usr/lib/libkdecore.so.4
No symbol table info available.
#8 0xb77fd965 in virtual thunk to KIO::Scheduler::~Scheduler$delete() ()
from /usr/lib/libkio.so.4
No symbol table info available.
#9 0xbfd008c0 in ?? ()
No symbol table info available.
#10 0xbfd00888 in ?? ()
No symbol table info available.
#11 0xffffffff in ?? ()
No symbol table info available.
#12 0xb64a66f1 in operator delete () from /usr/lib/libstdc++.so.6
No symbol table info available.
#13 0xb77a14ff in KIO::Scheduler::_scheduleJob () from /usr/lib/libkio.so.4
No symbol table info available.
#14 0x081a325a in QMap<int, QString>::operator[] ()
No symbol table info available.
#15 0x081a3f3f in QMap<int, QString>::operator[] ()
No symbol table info available.
#16 0xb6ca11bf in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
No symbol table info available.
#17 0xb70e7401 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
No symbol table info available.
#18 0xbfd00a04 in ?? ()
No symbol table info available.
#19 0x00000000 in ?? ()
No symbol table info available.
==== (gdb) thread apply all bt ====
Thread 1 (Thread -1238825280 (LWP 5684)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb65b532b in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#2 0x081f8acc in amaroK::Crash::crashHandler ()
#3 <signal handler called>
#4 0xffffe410 in __kernel_vsyscall ()
#5 0xb62c0ef1 in raise () from /lib/tls/libc.so.6
#6 0xb62c283b in abort () from /lib/tls/libc.so.6
#7 0xb72cc9c3 in kdbgstream::flush () from /usr/lib/libkdecore.so.4
#8 0xb77fd965 in virtual thunk to KIO::Scheduler::~Scheduler$delete() ()
from /usr/lib/libkio.so.4
#9 0xbfd008c0 in ?? ()
#10 0xbfd00888 in ?? ()
#11 0xffffffff in ?? ()
#12 0xb64a66f1 in operator delete () from /usr/lib/libstdc++.so.6
#13 0xb77a14ff in KIO::Scheduler::_scheduleJob () from /usr/lib/libkio.so.4
#14 0x081a325a in QMap<int, QString>::operator[] ()
#15 0x081a3f3f in QMap<int, QString>::operator[] ()
#16 0xb6ca11bf in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb70e7401 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xbfd00a04 in ?? ()
#19 0x00000000 in ?? ()

==== kdBacktrace() ================

Sapete darmi qualche dritta?

GunMan
14-12-2006, 21:16
il log onestamente non sono in grado di comprenderlo, normalmente quello di aiuto per gli sviluppatori del software, comunque siamo alla 1.4.4 (se non erro) quindi potresti aggiornare la tua versione, puoi anche provare a lanciare un .mp3 da riga di comando usando amarokapp

:ciauz:

cron
14-12-2006, 21:27
ciao, ho provato a fare come dici tu da riga di comando e dopo qualche secondo ecco cosa dice:


[cron@anacron ~]$ amarokapp /home/cron/Documents/02-elisa_e_ligabue-gli_ostacoli_del_cuore.mp3
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QMultiInputContext::changeInputMethod(): index=0, slave=xim
QMultiInputContext::changeInputMethod(): index=0, slave=xim
STARTUP
QMultiInputContext::changeInputMethod(): index=0, slave=xim
kio (Scheduler): FATAL: BUG! _ScheduleJob(): No extraJobData for job!
[cron@anacron ~]$

ho provato anche a reinstallare con la nuova versione ma niente.

:bh:

andy caps
14-12-2006, 21:32
prova a rinominare la dir .kde e riavviare kde

spesso i problemi derivano dai files di configurazione e cosi facendo ripristini tutto al livello iniziale
devi rifare tutte le conf chiaramente

GunMan
14-12-2006, 21:36
potrebbe essere un problema legato al database che usa amarok.

dovresti avere un file chiamato collection.db in ~/.kde/share/apps/amarok prova a fare un backup del file e successivamente cancellarlo.

questo dovrebbe permetterti di riavviare correttamente l'applicazione.

poi eventualmente puoi provare a risistemare anche il database una volta stabilito se l'inghippo li oppure no :)

:ciauz:

cron
15-12-2006, 11:12
grazie a tutti, ho risolto facendo come consigliava GunMan.

:ciauz:

Loading