Mailinglist Archive: opensuse-bugs (14006 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=382036

User suse-beta@xxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=382036#c8


Christian Boltz <suse-beta@xxxxxxxxx> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
                 CC|                                                
|suse-beta@xxxxxxxxx
             Status|NEEDINFO                                        |NEW
      Info Provider|funtasyspace@xxxxxxxxx                          |




--- Comment #8 from Christian Boltz <suse-beta@xxxxxxxxx>  2008-04-28 11:31:34 
MST ---
[Jörg, please answer in this bug also. Maybe I found a different one than
you... Nevertheless resetting needinfo so that Marcus gets the bug back on his
list.]


I have found a reproducable crash when running xapi:
- start xapi
- click away message that 3D is not supported on Xinerama
- click away warning "Mindestens eine Anzeige muss aktiv sein" (at least one 
  display must be active)
- click the "Dualhead aktivieren" (activate dualhead) option -> xapi crashes 
  instantly (segfault)

Please note that sax did _not_ crash at this point when started from runlevel
3.

(gdb) bt
#0  0xb75291fc in QPixmap::QPixmap () from /usr/lib/libQtGui.so.4
#1  0x080bec70 in ?? ()
#2  0x080b3e5a in ?? ()
#3  0x080abc0e in ?? ()
#4  0x080df67e in ?? ()
#5  0xb70833aa in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#6  0xb7083922 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#7  0x080dfc75 in ?? ()
#8  0x080bbb68 in ?? ()
#9  0x080dfd4b in ?? ()
#10 0xb70833aa in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb70836a0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb79da111 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4
#13 0xb776b259 in ?? () from /usr/lib/libQtGui.so.4
#14 0x081bfc20 in ?? ()
#15 0x00000001 in ?? ()
#16 0xbfd5aec8 in ?? ()
#17 0xb74fef75 in ?? () from /usr/lib/libQtGui.so.4
#18 0x0810eb18 in ?? ()
#19 0xb710dff4 in ?? () from /usr/lib/libQtCore.so.4
#20 0x081bfc20 in ?? ()
#21 0xb7aa4ff4 in ?? () from /usr/lib/libQtGui.so.4
#22 0x081bfc20 in ?? ()
#23 0x081e7f70 in ?? ()
#24 0xbfd5af08 in ?? ()
#25 0xb776c084 in ?? () from /usr/lib/libQtGui.so.4
#26 0x081e7f70 in ?? ()
#27 0x00000010 in ?? ()
#28 0xbfd5aef8 in ?? ()
#29 0xb7070164 in QBasicTimer::stop () from /usr/lib/libQtCore.so.4
Backtrace stopped: previous frame inner to this frame (corrupt stack?)


Another test:
This time I configured two monitors without the "dualhead" option. xapi crashed
after clicking "Testen" (test) in the dialog that asks if you want to save the
config and/or test the new settings. (This is the point where it also crashed
in runlevel 3.)

(gdb) bt
#0  0xb71340b0 in ?? () from /usr/lib/libQtCore.so.4
#1  0xb808f32b in ?? ()
#2  0xcaa7439b in ?? ()
#3  0xb726eff4 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00016cdf in ?? ()
#5  0x00016ce0 in ?? ()
#6  0xbfabc8d8 in ?? ()
#7  0xb713a26e in QString::indexOf () from /usr/lib/libQtCore.so.4
Backtrace stopped: frame did not save the PC

Seems I need some debuginfo packages to make the backtrace useful. What do you
recommend? ;-)


Another thing - I tested with minimal steps.
a) change nothing, just click OK and save the config - works
b) - click the "Bildschirm 2" (display 2) tab
   - activate "Diese Anzeige aktivieren" (activate this display)
   - then click OK and save the config - crash (segfault)

So it seems activating the second monitor causes the crash.
(To prevent the question: I also tried just switching to the "Bildschirm 2" tab
without changing a setting there - no crash.)

(gdb) bt
#0  0xb70ec0b0 in ?? () from /usr/lib/libQtCore.so.4
#1  0x00007f98 in ?? ()
#2  0x129471d8 in ?? ()
#3  0xb7226ff4 in ?? () from /usr/lib/libQtCore.so.4
#4  0xbfe733c0 in ?? ()
#5  0x00000000 in ?? ()


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.