| Summary: | Amarok crashed after removing android phone | ||
|---|---|---|---|
| Product: | [Unmaintained] krandr | Reporter: | fabian.sabau |
| Component: | general | Assignee: | Gustavo Pichorim Boiko <gustavo.boiko> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | blow0184, bugzilla, cbj, cfeck, g.testard, greenrd, healiseu, masterroz, mgolden, mransolin, myriam, piet.delaney, thomas.pasch, Tobias |
| Priority: | NOR | ||
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
fabian.sabau
2011-10-13 19:45:00 UTC
*** Bug 284599 has been marked as a duplicate of this bug. *** Created attachment 65196 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed: Closed my laptop and carried it with me to my desk.
-- Backtrace (Reduced):
#7 QMap (other=..., this=0xbfe206f8) at /usr/include/qt4/QtCore/qmap.h:185
#8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231
#9 0xa9a7842e in RandrMonitorModule::outputs (this=0x864fae8, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250
#10 0xa9a78658 in RandrMonitorModule::connectedOutputs (this=0x864fae8, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232
#11 0xa9a786ca in RandrMonitorModule::resumedFromSuspend (this=0x864fae8) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 65197 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed: Closed my laptop and carried it with me to my desk.
-- Backtrace (Reduced):
#7 QMap (other=..., this=0xbfe206f8) at /usr/include/qt4/QtCore/qmap.h:185
#8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231
#9 0xa9a7842e in RandrMonitorModule::outputs (this=0x864fae8, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250
#10 0xa9a78658 in RandrMonitorModule::connectedOutputs (this=0x864fae8, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232
#11 0xa9a786ca in RandrMonitorModule::resumedFromSuspend (this=0x864fae8) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 65198 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed: Closed my laptop and carried it with me to my desk.
-- Backtrace (Reduced):
#7 QMap (other=..., this=0xbfe206f8) at /usr/include/qt4/QtCore/qmap.h:185
#8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231
#9 0xa9a7842e in RandrMonitorModule::outputs (this=0x864fae8, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250
#10 0xa9a78658 in RandrMonitorModule::connectedOutputs (this=0x864fae8, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232
#11 0xa9a786ca in RandrMonitorModule::resumedFromSuspend (this=0x864fae8) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
*** Bug 285693 has been marked as a duplicate of this bug. *** *** Bug 287892 has been marked as a duplicate of this bug. *** *** Bug 288382 has been marked as a duplicate of this bug. *** *** Bug 288456 has been marked as a duplicate of this bug. *** Created attachment 66730 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
Closed my laptop to carry it. This happens each time it suspends to ram.
-- Backtrace (Reduced):
#6 QMap (other=..., this=0x7fffa80d17c0) at /usr/include/QtCore/qmap.h:185
#7 RandRScreen::outputs (this=0x0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/randrscreen.cpp:231
#8 0x00007f7034140517 in RandrMonitorModule::outputs (this=<optimized out>, display=..., connected=true, active=false, validCrtc=false) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:250
#9 0x00007f70341406c4 in RandrMonitorModule::connectedOutputs (this=<optimized out>, display=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:232
#10 0x00007f703414072c in RandrMonitorModule::resumedFromSuspend (this=0x9c90f0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 66729 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
Closed my laptop to carry it. This happens each time it suspends to ram.
-- Backtrace (Reduced):
#6 QMap (other=..., this=0x7fffa80d17c0) at /usr/include/QtCore/qmap.h:185
#7 RandRScreen::outputs (this=0x0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/randrscreen.cpp:231
#8 0x00007f7034140517 in RandrMonitorModule::outputs (this=<optimized out>, display=..., connected=true, active=false, validCrtc=false) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:250
#9 0x00007f70341406c4 in RandrMonitorModule::connectedOutputs (this=<optimized out>, display=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:232
#10 0x00007f703414072c in RandrMonitorModule::resumedFromSuspend (this=0x9c90f0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 66984 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed:
Going into Sleep mode or coming out of Sleep mode (not sure)
- Custom settings of the application:
Dual headed display
-- Backtrace (Reduced):
#7 QMap (other=..., this=0xbfe1a4e8) at /usr/include/qt4/QtCore/qmap.h:185
#8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231
#9 0xa998642e in RandrMonitorModule::outputs (this=0x904bcb0, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250
#10 0xa9986658 in RandrMonitorModule::connectedOutputs (this=0x904bcb0, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232
#11 0xa99866ca in RandrMonitorModule::resumedFromSuspend (this=0x904bcb0) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
*** Bug 294581 has been marked as a duplicate of this bug. *** *** Bug 294685 has been marked as a duplicate of this bug. *** Created attachment 69209 [details]
New crash information added by DrKonqi
kded4 ($Id$) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4
- What I was doing when the application crashed:
Waking up the system after sleep.
- Unusual behavior I noticed:
It always happens.
-- Backtrace (Reduced):
#6 QMap (other=..., this=0x7fff9ad9fe80) at /usr/include/qt4/QtCore/qmap.h:185
#7 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231
#8 0x00007fa961dd0787 in RandrMonitorModule::outputs (this=<optimized out>, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250
#9 0x00007fa961dd0934 in RandrMonitorModule::connectedOutputs (this=<optimized out>, display=<optimized out>) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232
#10 0x00007fa961dd099c in RandrMonitorModule::resumedFromSuspend (this=0x15bc220) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
*** Bug 296124 has been marked as a duplicate of this bug. *** *** Bug 296131 has been marked as a duplicate of this bug. *** *** Bug 300552 has been marked as a duplicate of this bug. *** Thank you for your bug report or feature request. Unfortunately, we did not have a maintainer for the "krandr" components, which are used to manage displays and monitors in the KDE Workspaces. The "krandr" components has been superseded by "KScreen" in newer releases of the KDE Workspaces. It is compatible with all versions since 4.11, and is also used with Plasma 5. Please check with your distribution how to update to KScreen. If this issue or feature request is still applicable to KScreen version 1.0.5 or newer, please add a comment. We will then reassign this ticket to KScreen developers. If you are already using KScreen to manage displays or monitors, and found a different bug or need a specific feature, please create a new ticket for "KScreen" product in this bugzilla using this link: https://bugs.kde.org/enter_bug.cgi?product=KScreen (This is an automatic message from the KDE Bug Triaging Team) |