https://bugzilla.novell.com/show_bug.cgi?id=382036 User funtasyspace@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382036#c1 --- Comment #1 from Jörg Hermsdorf 2008-04-21 10:56:21 MST --- I have to mention, that I called sax2 this way: # init 3 # sax2 -r -m 0=radeonhd This way no xorg.conf file is created. Now, I just tried to call sax2 without params: # init 3 # sax2 After finishing the configuration this way, there is a new xorg.conf and xorg.conf.md5 file in /etc/X11/ afterwards. So I am not sure if this is still a bug or expected behavior if sax2 is called with the '-r' option. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=382036 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |381745 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=382036 User funtasyspace@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382036#c4 --- Comment #4 from Jörg Hermsdorf 2008-04-21 15:41:54 MST --- By the way, this behavior seems to be not deterministic. It seems like the '-r' parameter is not the reason for sax not writing/generating the xorg.conf. I tried without the '-r' option several times now, by just calling: # init 3 # rm /etc/X11/xorg.conf # rm /var/log/SaX2.log # sax2 Sometimes xorg.conf is created and sometimes not. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=382036 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[sax2] no xorg.conf is written to disk |sax2: no xorg.conf is written to disk |(/etc/X11/) |(/etc/X11/) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=382036 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=382036#c8 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de Status|NEEDINFO |NEW Info Provider|funtasyspace@yahoo.com | --- Comment #8 from Christian Boltz 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.

https://bugzilla.novell.com/show_bug.cgi?id=382036 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382036#c10 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | --- Comment #10 from Stephan Kulow 2008-05-02 02:10:01 MST --- this is no good messing all sax bugs that look suspicious to you into the "message boxes are wrapped" bug report ;( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=382036 User ms@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=382036#c12 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |cstender@novell.com --- Comment #12 from Marcus Schaefer 2008-05-02 02:17:43 MST --- in reply to comment #10: I also have fixed many issues related to this one, see the sax2.changelog for all the bugs I don't have marked as duplicate. I will open a new bug to track down the crashes. If you want Christian to do some debugging a needinfo to him sounds useful too -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=382036 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|381745 | -- 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.