Summary: | Amarok crashed while joining a new wireless network | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Kenny Kruger <kenneth.j.kruger> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | vahagn.yeghikyan |
Priority: | NOR | ||
Version: | 2.3.1 | ||
Target Milestone: | 2.4.0 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Kenny Kruger
2010-09-21 00:25:30 UTC
The backtrace shows a problem with the Network, but not with Amarok. You should report this downstream in Launchpad. I tried to reproduce this here, switching from Lan to Wirelesss and back several times, no crash. Using Amarok 2.4-git on KDE 4.5.1, Kubuntu 10.04 Created attachment 57212 [details]
New crash information added by DrKonqi
amarok (2.4.0) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0
- What I was doing when the application crashed:
I just refreshed the wifi connection and got the .
-- Backtrace (Reduced):
#6 QMutex::lock (this=0x18) at thread/qmutex.cpp:151
#7 0x00007f7699e8f0e8 in QNetworkConfigurationManagerPrivate::configurationRemoved (this=0x3539660, ptr=) at bearer/qnetworkconfigmanager_p.cpp:313
#8 0x00007f7699eeb368 in QNetworkConfigurationManagerPrivate::qt_metacall (this=0x3539660, _c=<value optimized out>, _id=<value optimized out>, _a=0x7fffd5a49ad0) at .moc/release-shared/moc_qnetworkconfigmanager_p.cpp:105
[...]
#10 0x00007f7699e92565 in QBearerEngine::configurationRemoved (this=0x18, _t1=<value optimized out>) at .moc/release-shared/moc_qbearerengine_p.cpp:101
#11 0x00007f765bf14699 in QNetworkManagerEngine::parseConnection (this=<value optimized out>, service=<value optimized out>, settingsPath=<value optimized out>, map=<value optimized out>) at qnetworkmanagerengine.cpp:740
|