Summary: | Crash in MassStorageDeviceHandlerFactory::createHandler() | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Xavier Fung <xavier114fch> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | aikawarazuni, mahajan.nilu, mitchell, rapsys |
Priority: | HI | Keywords: | release_blocker |
Version: | 2.3-GIT | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Xavier Fung
2009-05-20 09:52:49 UTC
this was fixed in rev 966203 by mitchell *** Bug 194148 has been marked as a duplicate of this bug. *** *** Bug 194843 has been marked as a duplicate of this bug. *** This doesn't seem to be fixed. A user just got the same crash with current trunk: Thread 1 (Thread 0x7f18a1d72850 (LWP 6934)): [KCrash Handler] #5 0x00007f189e94df05 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00007f189e94fa73 in abort () at abort.c:88 #7 0x00007f189f6a1605 in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>) at global/qglobal.cpp:2017 #8 0x00007f189f6a174b in qFatal (msg=<value optimized out>) at global/qglobal.cpp:2216 #9 0x00007f186f2c7462 in MassStorageDeviceHandlerFactory::createHandler (this=0x1151bb0, device=@0x28a5690, udi=@0x7fffc46c8420) at /home/panzi/software/amarok/src/collection/device/massstorage/MassStorageDeviceHandler.cpp:131 #10 0x00007f18a13264ca in MountPointManager::createHandlerFromDevice (this=0x108a330, device=@0x28a5690, udi=@0x7fffc46c8420) at /home/panzi/software/amarok/src/MountPointManager.cpp:520 #11 0x00007f18a1328255 in MountPointManager::init (this=0x108a330) at /home/panzi/software/amarok/src/MountPointManager.cpp:137 Changed priority to high Any news on this? iirc, this was happening only on the first start after a database version update. And since there haven't been any reports about this with beta1 I think it's fixed. But I might be wrong... Yeah -- unless someone can tell me how to reliably reproduce this (I've never seen it) I can't do much. |