[systemsettings] [Bug 341584] New: systemsettings crash while resetting / selecting display outputs

Rich Coe rcoe at wi.rr.com
Fri Dec 5 16:36:08 GMT 2014 

https://bugs.kde.org/show_bug.cgi?id=341584

            Bug ID: 341584
           Summary: systemsettings crash while resetting / selecting
                    display outputs
           Product: systemsettings
           Version: unspecified
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: rcoe at wi.rr.com

Application: systemsettings (4.11.14)
KDE Platform Version: 4.14.3
Qt Version: 4.8.6
Operating System: Linux 3.18.0-rc6-1.g961dff7-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I have two attached digital displays.  I had been away from the computer and
the blank screen saver had kicked in.   I awoke the display, and the right
display was blank with the monitor is sleep mode.   I tried disabling and
enabling the right display in the 'configure display' option.   When that
didn't work, I unified the outputs and de-unified the inputs.   Then the
application crashed.

- Unusual behavior I noticed:
The right display was displaying a gray screen, it would go black, and then
come back to a gray screen. 

- Temporary resolution:
I suspended the system, reset power on the right display, and resumed.
Both monitors returned to normal.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f12e79d8800 (LWP 10931))]

Thread 3 (Thread 0x7f12c944c700 (LWP 10933)):
#0  0x00007f12e49fa49d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f12dd9e9750 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f12c944bba0, __fd=<optimized out>) at /usr/include/bits/unistd.h:44
#2  0x00007f12dd9e9750 in g_wakeup_acknowledge (wakeup=0x1e848c0) at
gwakeup.c:210
#3  0x00007f12dd9a8714 in g_main_context_check
(context=context at entry=0x7f12c40009a0, max_priority=2147483647,
fds=fds at entry=0x7f12c4003410, n_fds=n_fds at entry=1) at gmain.c:3579
#4  0x00007f12dd9a8b7b in g_main_context_iterate
(context=context at entry=0x7f12c40009a0, block=block at entry=1,
dispatch=dispatch at entry=1, self=<optimized out>) at gmain.c:3778
#5  0x00007f12dd9a8cec in g_main_context_iteration (context=0x7f12c40009a0,
may_block=1) at gmain.c:3842
#6  0x00007f12e51810de in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQtCore.so.4
#7  0x00007f12e5152e6f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#8  0x00007f12e5153165 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#9  0x00007f12e50500bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#10 0x00007f12e5134783 in  () at /usr/lib64/libQtCore.so.4
#11 0x00007f12e505279f in  () at /usr/lib64/libQtCore.so.4
#12 0x00007f12ddc730a4 in start_thread (arg=0x7f12c944c700) at
pthread_create.c:309
#13 0x00007f12e4a067fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f12c8806700 (LWP 10935)):
#0  0x00007f12ddc7705f in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f12e22a88cb in  () at /usr/lib64/libQtScript.so.4
#2  0x00007f12e22a8909 in  () at /usr/lib64/libQtScript.so.4
#3  0x00007f12ddc730a4 in start_thread (arg=0x7f12c8806700) at
pthread_create.c:309
#4  0x00007f12e4a067fd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f12e79d8800 (LWP 10931)):
[KCrash Handler]
#5  0x00007f12c8811c14 in KScreen::Output::id() const () at
/usr/lib64/libkscreen.so.1
#6  0x00007f1243207464 in  () at /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#7  0x00007f12c8811319 in KScreen::ConfigMonitor::Private::updateConfigs() ()
at /usr/lib64/libkscreen.so.1
#8  0x00007f12c881134d in KScreen::ConfigMonitor::notifyUpdate() () at
/usr/lib64/libkscreen.so.1
#9  0x00007f1243204c44 in  () at /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#10 0x00007f12e51681fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#11 0x00007f1243205f17 in  () at /usr/lib64/kde4/plugins/kscreen/KSC_XRandR.so
#12 0x00007f12e6b1ddd8 in  () at /usr/lib64/libkdeui.so.5
#13 0x00007f12e51461ce in QAbstractEventDispatcher::filterEvent(void*) () at
/usr/lib64/libQtCore.so.4
#14 0x00007f12e5e7c4f0 in  () at /usr/lib64/libQtGui.so.4
#15 0x00007f12dd9a8a04 in g_main_context_dispatch (context=0x1ec6f70) at
gmain.c:3111
#16 0x00007f12dd9a8a04 in g_main_context_dispatch
(context=context at entry=0x1ec6f70) at gmain.c:3710
#17 0x00007f12dd9a8c48 in g_main_context_iterate
(context=context at entry=0x1ec6f70, block=block at entry=1,
dispatch=dispatch at entry=1, self=<optimized out>) at gmain.c:3781
#18 0x00007f12dd9a8cec in g_main_context_iteration (context=0x1ec6f70,
may_block=1) at gmain.c:3842
#19 0x00007f12e51810be in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQtCore.so.4
#20 0x00007f12e5e7c676 in  () at /usr/lib64/libQtGui.so.4
#21 0x00007f12e5152e6f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#22 0x00007f12e5153165 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#23 0x00007f12e51585b9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#24 0x000000000040b4bb in  ()
#25 0x00007f12e4942b05 in __libc_start_main (main=0x40b140, argc=5,
argv=0x7fff54d0bb78, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fff54d0bb68) at libc-start.c:285
#26 0x000000000040b50c in _start ()

Report to https://bugs.kde.org/

Reproducible: Didn't try




The crash reporting assistant did not find a dup of this report.

-- 
You are receiving this mail because:
You are the assignee for the bug.

More information about the Unassigned-bugs mailing list