Bug 183941 - systemsettings: Display settings program crashes with screen rotated
Summary: systemsettings: Display settings program crashes with screen rotated
Status: RESOLVED DUPLICATE of bug 192129
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-10 21:38 UTC by Bill Frans
Modified: 2009-05-09 18:40 UTC (History)
3 users (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 Bill Frans 2009-02-10 21:38:56 UTC
Version:            (using KDE 4.2.0)
Compiler:          gcc-4.3.2-3mnb2 
OS:                Linux
Installed from:    Mandriva RPMs

Using an Nvidia graphics card with the nvidia driver and screen rotation enabled (RandrRotation), I had tried to rotate the screen using the systemsettings Display program. The program allowed for upside down rotation but not left and right.  I then change my X configuration to rotate "Left" by default.  After resetting X, I logged in and ran the KDE systemsettings->Display program.  The Display program crashed before it ever opened.

How to reproduce:
Set Xorg settings to those below.  Restart X. Login.  Open systemsettings and click on Display.


Expected behavior: 
Display shouldn't crash.  At the least, it should open with the option of not rotating.  

Relevant Xorg:
Section "Device"
    Identifier "device1"
    VendorName "nVidia Corporation"
    BoardName "NVIDIA GeForce FX series"
    Driver "nvidia"
    Option "DPMS"
    Option "TwinViewOrientation" "Clone"
    Option "TwinView"
    Option "AddARGBGLXVisuals"
    # Options to Rotate
    Option "RandRRotation"
    Option "Rotate" "Left" 
EndSection

Log from terminal:
systemsettings(1184) MainWindow::selectionChanged: Selected item:  "Display"
systemsettings(1184) MainWindow::selectionChanged: Comment:        "Display Settings"
systemsettings(1184) MainWindow::selectionChanged: adding
systemsettings(1184)/kutils (KCModuleProxy) KCModuleProxyPrivate::loadModule: Module not already loaded, loading module  "Size & Orientation"  from library  "kcm_randr"  using symbol  "kcm_randr"
systemsettings(1184) KRandRModule::KRandRModule: Error:  ""
systemsettings(1184) MainWindow::selectionChanged: adding
systemsettings(1184) MainWindow::selectionChanged: Selected item:  "Display"
systemsettings(1184) MainWindow::selectionChanged: Comment:        "Display Settings"
systemsettings(1184) KRandRModule::load: Loading KRandRModule...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings path = <unknown> pid = 1184
sock_file=/home/bil_eff/.kde4/socket-queenbee/kdeinit4__0

KDE Bug display:
A Fatal Error Occurred
The application System Settings (systemsettings) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.

Backtrace (maybe not valid):

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(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 0x7f6b6400a700 (LWP 1184)]
[New Thread 0x40e53950 (LWP 1186)]
(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)
0x00007f6b617e46d1 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f6b6400a700 (LWP 1184))]

Thread 2 (Thread 0x40e53950 (LWP 1186)):
#0  0x00007f6b6107f1dd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f6b55bce7e1 in ?? () from /usr/lib64/libxine.so.1
#2  0x00007f6b6107b2a3 in start_thread () from /lib64/libpthread.so.0
#3  0x00007f6b61820f0d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6b6400a700 (LWP 1184)):
#0  0x00007f6b617e46d1 in nanosleep () from /lib64/libc.so.6
#1  0x00007f6b617e44cc in sleep () from /lib64/libc.so.6
#2  0x00007f6b633b1c0a in ?? () from /usr/lib64/libkdeui.so.5
#3  0x00007f6b633b237d in KCrash::defaultCrashHandler () from /usr/lib64/libkdeui.so.5
#4  <signal handler called>
#5  0x00007f6b503cdb30 in ?? () from /usr/lib64/kde4/kcm_randr.so
#6  0x00007f6b503ca7a7 in ?? () from /usr/lib64/kde4/kcm_randr.so
#7  0x00007f6b503c8aa1 in ?? () from /usr/lib64/kde4/kcm_randr.so
#8  0x00007f6b633e7275 in KCModule::qt_metacall () from /usr/lib64/libkdeui.so.5
#9  0x00007f6b62a4b8c5 in QObject::event () from /usr/lib64/libQtCore.so.4
#10 0x00007f6b61fb5826 in QWidget::event () from /usr/lib64/libQtGui.so.4
#11 0x00007f6b61f63a9d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4
#12 0x00007f6b61f6b82a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#13 0x00007f6b63357a7e in KApplication::notify () from /usr/lib64/libkdeui.so.5
#14 0x00007f6b62a3c87f in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4
#15 0x00007f6b62a3d51a in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/libQtCore.so.4
#16 0x00007f6b62a64f93 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007f6b5e10a8d2 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f6b5e10e05d in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f6b5e10e21b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f6b62a64c1f in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#21 0x00007f6b61ff5fbf in ?? () from /usr/lib64/libQtGui.so.4
#22 0x00007f6b62a3b1a2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#23 0x00007f6b62a3b32d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#24 0x00007f6b62a3d7dd in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4
#25 0x0000000000410ebf in ?? ()
#26 0x00007f6b61762316 in __libc_start_main () from /lib64/libc.so.6
#27 0x000000000040c2f9 in _start ()
Comment 1 Nicolas L. 2009-02-17 00:51:30 UTC
can you please install the debug packages from the debug media ?
Comment 2 Christoph Feck 2009-05-09 18:40:02 UTC
The backtrace itself is not useful, but looking at the console output, it crashes right in KRandRModule::load: Loading KRandRModule...

So it is a duplicate.

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