Bug 174931 - kwin crashes when using xrandr to configure dual-head
Summary: kwin crashes when using xrandr to configure dual-head
Status: RESOLVED DUPLICATE of bug 173017
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-12 10:18 UTC by Dan Bohr
Modified: 2008-11-19 09:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Bohr 2008-11-12 10:18:54 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

The installation is a Kubuntu Interpid Ibex, 64 bit kernel on a Lenovo X61s with all updates from the Kubuntu repositories.

I can trigger the crash by issuing
xrandr --output LVDS --mode 1024x768 --pos 0x0 --output VGA  --mode 1024x768 --pos 1024x0

which switches on the second monitor correctly, but also makes KWin crash.


Here is the (full) backtrace from the KDE crash handler:

Application: KWin (kwin), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9cb511c700 (LWP 7506)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f9cb4931fd5 in raise () from /lib/libc.so.6
#6  0x00007f9cb4933b43 in abort () from /lib/libc.so.6
#7  0x00007f9cb3c916b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007f9cb3c917fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007f9cb4cdc747 in ?? () from /usr/lib/libkdeinit4_kwin.so
#10 0x00007f9cb4cdc98c in ?? () from /usr/lib/libkdeinit4_kwin.so
#11 0x00007f9cb4cdcdc1 in ?? () from /usr/lib/libkdeinit4_kwin.so
#12 0x00007f9cb4cdd094 in ?? () from /usr/lib/libkdeinit4_kwin.so
#13 0x00007f9cb4ce52d2 in ?? () from /usr/lib/libkdeinit4_kwin.so
#14 0x00007f9cb4ce6638 in ?? () from /usr/lib/libkdeinit4_kwin.so
#15 0x00007f9cb4c9778d in ?? () from /usr/lib/libkdeinit4_kwin.so
#16 0x00007f9cb3d96134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#17 0x00007f9cb2ee963e in QDesktopWidget::resized ()
   from /usr/lib/libQtGui.so.4
#18 0x00007f9cb29d0fab in QApplication::x11ProcessEvent ()
   from /usr/lib/libQtGui.so.4
#19 0x00007f9cb29f82f4 in ?? () from /usr/lib/libQtGui.so.4
#20 0x00007f9caffc3d3b in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#21 0x00007f9caffc750d in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00007f9caffc76cb in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#23 0x00007f9cb3daa15f in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#24 0x00007f9cb29f7a9f in ?? () from /usr/lib/libQtGui.so.4
#25 0x00007f9cb3d80682 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#26 0x00007f9cb3d8080d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#27 0x00007f9cb3d82cbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#28 0x00007f9cb4cb0731 in kdemain () from /usr/lib/libkdeinit4_kwin.so
#29 0x00007f9cb491d466 in __libc_start_main () from /lib/libc.so.6
#30 0x0000000000400659 in _start ()
#0  0x00007f9cb49a7621 in nanosleep () from /lib/libc.so.6
Comment 1 Oliver Putz 2008-11-19 09:03:09 UTC
Hello,

Thanks for your report. It sounds as if you are able to reproduce the crash. So could you please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports, try to install the debugging packages for your distribution and post a more detailed backtrace?
Comment 2 lucas 2008-11-19 09:06:06 UTC

*** This bug has been marked as a duplicate of bug 173017 ***