Bug 324240 - Enable DisplayLink USB Display crashes System Settings
Summary: Enable DisplayLink USB Display crashes System Settings
Status: RESOLVED NOT A BUG
Alias: None
Product: KScreen
Classification: Plasma
Component: libkscreen (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-08-29 22:44 UTC by Allen2
Modified: 2013-12-27 21:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allen2 2013-08-29 22:44:38 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.10.5
Qt Version: 4.8.5
Operating System: Linux 3.10.7-200.fc19.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Enabled DisplayLink USB Display labeled DVI-1 via System Settings

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7ffcd9bee8c0 (LWP 31034))]

Thread 2 (Thread 0x7ffccbf62700 (LWP 31039)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x000000376f5860bb in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x376f883f00 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x000000376f5860f9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x0000003747207c53 in start_thread (arg=0x7ffccbf62700) at pthread_create.c:308
#4  0x00000037466f5ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7ffcd9bee8c0 (LWP 31034)):
[KCrash Handler]
#6  0x00007ffccbf6fd28 in XRandROutput::updateOutput(_XRROutputInfo const*) () from /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#7  0x00007ffccbf701f7 in XRandROutput::update(XRandROutput::PrimaryChange) () from /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#8  0x00007ffccbf6b720 in XRandRConfig::toKScreenConfig() const () from /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#9  0x00007ffccc3a2237 in KScreen::Config::canBeApplied(KScreen::Config*) () from /usr/lib64/libkscreen.so.1
#10 0x00007ffccc3a2de8 in KScreen::Config::setConfig(KScreen::Config*) () from /usr/lib64/libkscreen.so.1
#11 0x00007ffccc5bb3a9 in KCMKScreen::save() () from /usr/lib64/kde4/kcm_kscreen.so
#12 0x000000376ca211b7 in KCModuleProxy::save (this=<optimized out>) at /usr/src/debug/kdelibs-4.10.5/kutils/kcmoduleproxy.cpp:279
#13 0x000000375880efd3 in ModuleView::moduleSave(KCModuleProxy*) () from /usr/lib64/libsystemsettingsview.so.2
#14 0x000000375881125a in ModuleView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.26] () from /usr/lib64/libsystemsettingsview.so.2
#15 0x000000375438df78 in QMetaObject::activate (sender=sender@entry=0x1b922e0, m=m@entry=0x3758691400 <QAbstractButton::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff5093dda0) at kernel/qobject.cpp:3547
#16 0x000000375820eb22 in QAbstractButton::clicked (this=this@entry=0x1b922e0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:219
#17 0x0000003757f74703 in QAbstractButtonPrivate::emitClicked (this=this@entry=0x1baeaa0) at widgets/qabstractbutton.cpp:548
#18 0x0000003757f75903 in QAbstractButtonPrivate::click (this=this@entry=0x1baeaa0) at widgets/qabstractbutton.cpp:541
#19 0x0000003757f759ec in QAbstractButton::mouseReleaseEvent (this=0x1b922e0, e=0x7fff5093e290) at widgets/qabstractbutton.cpp:1123
#20 0x0000003757c17b1e in QWidget::event (this=0x1b922e0, event=0x7fff5093e290) at kernel/qwidget.cpp:8376
#21 0x0000003757bc84dc in QApplicationPrivate::notify_helper (this=0x18c1250, receiver=0x1b922e0, e=0x7fff5093e290) at kernel/qapplication.cpp:4562
#22 0x0000003757bcebdd in QApplication::notify (this=this@entry=0x7fff5093eae0, receiver=receiver@entry=0x1b922e0, e=e@entry=0x7fff5093e290) at kernel/qapplication.cpp:4105
#23 0x0000003759a415ba in KApplication::notify (this=0x7fff5093eae0, receiver=0x1b922e0, event=0x7fff5093e290) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#24 0x000000375437a26d in QCoreApplication::notifyInternal (this=0x7fff5093eae0, receiver=0x1b922e0, event=0x7fff5093e290) at kernel/qcoreapplication.cpp:949
#25 0x0000003757bce393 in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x1b922e0, event=event@entry=0x7fff5093e290, alienWidget=alienWidget@entry=0x1b922e0, nativeWidget=nativeWidget@entry=0x19d02e0, buttonDown=buttonDown@entry=0x37586a3258 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at ../../src/corelib/kernel/qcoreapplication.h:231
#26 0x0000003757c3f92b in QETWidget::translateMouseEvent (this=this@entry=0x19d02e0, event=event@entry=0x7fff5093e600) at kernel/qapplication_x11.cpp:4538
#27 0x0000003757c3e39c in QApplication::x11ProcessEvent (this=0x7fff5093eae0, event=event@entry=0x7fff5093e600) at kernel/qapplication_x11.cpp:3661
#28 0x0000003757c64e54 in x11EventSourceDispatch (s=s@entry=0x18a8df0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#29 0x000000374a247e06 in g_main_dispatch (context=0x18c14b0) at gmain.c:3054
#30 g_main_context_dispatch (context=context@entry=0x18c14b0) at gmain.c:3630
#31 0x000000374a248158 in g_main_context_iterate (context=context@entry=0x18c14b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3701
#32 0x000000374a2481fc in g_main_context_iteration (context=0x18c14b0, may_block=1) at gmain.c:3762
#33 0x00000037543a7166 in QEventDispatcherGlib::processEvents (this=0x187b150, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#34 0x0000003757c64fc6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#35 0x0000003754378ecf in QEventLoop::processEvents (this=this@entry=0x7fff5093e9e0, flags=...) at kernel/qeventloop.cpp:149
#36 0x00000037543791c5 in QEventLoop::exec (this=this@entry=0x7fff5093e9e0, flags=...) at kernel/qeventloop.cpp:204
#37 0x000000375437e45b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#38 0x000000000040ab5b in main ()

Reported using DrKonqi
Comment 1 Alex Fiestas 2013-08-31 12:08:46 UTC
this is not KSCreen but the "old" KRandR, reassigning.
Comment 2 Jekyll Wu 2013-08-31 12:30:13 UTC
(In reply to comment #1)
> this is not KSCreen but the "old" KRandR, reassigning.

>  #6 0x00007ffccbf6fd28 in XRandROutput::updateOutput(_XRROutputInfo const*) () from /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so

Sorry, but both my package manager and the source code tell me it is part of libkscreen.
Comment 3 Daniel Vrátil 2013-08-31 13:12:27 UTC
Alex, this is kscreen (the backtrace is pretty much clear about that).

Also, there is no krandr in Fedora 19, I removed it :-)
Comment 4 Alex Fiestas 2013-08-31 18:27:07 UTC
Lol I brainfucked big time, sorry  :/
Comment 5 Alex Fiestas 2013-11-13 23:14:39 UTC
We have never encountered a case where we get a new "Output", since usually the amount of them is fixed.

Can you please attach the following info?
-execute kdebugdialog and enable kscreen and ksrandr
-execute systemsettings in a terminal

Thanks !
Comment 6 Allen2 2013-11-14 02:07:18 UTC
kdebugdialog has an option for ksrandr but nothing for kscreen.
What action are you expecting after the 'execute systemsettings in a terminal' step?
Comment 7 Daniel Vrátil 2013-11-14 09:04:04 UTC
(In reply to comment #6)
> kdebugdialog has an option for ksrandr but nothing for kscreen.

There's only supposed to be KSRandr. Please enable that.

> What action are you expecting after the 'execute systemsettings in a
> terminal' step?

Run "kcmshell4 kscreen" from terminal, reproduce the crash an provide output from the terminal.
Comment 8 Christoph Feck 2013-11-30 00:52:36 UTC
Allen, can you still reproduce the crash? If yes, please add the information requested in comment #7.
Comment 9 Christoph Feck 2013-12-14 21:49:31 UTC
To further investigate this issue, KDE developers need the information requested in comment #7. If you can provide it, or need help with finding that information, please add a comment.
Comment 10 Christoph Feck 2013-12-27 21:50:47 UTC
No response, changing status. Please reopen, if you have more information.