[Bug 257323] New: Sax2 messes up Xorg setup (resolution)
https://bugzilla.novell.com/show_bug.cgi?id=257323 Summary: Sax2 messes up Xorg setup (resolution) Product: openSUSE 10.3 Version: Alpha 2 Platform: 64bit OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: SaX2 AssignedTo: ms@novell.com ReportedBy: one_way@online.de QAContact: qa@suse.de As of version 8.1-117, Sax2 seems to mess up my xorg.conf: Once Sax2 has been started, it decides that only 800x600 is the resolution to go for my 1280x1024 LCD. If I try to change to another, higher resolution, Sax2 quits without any message. This is an AMD64, Xorg 7.2 and the proprietary NVidia drivers. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal Status|NEW |NEEDINFO Info Provider| |one_way@online.de ------- Comment #1 from ms@novell.com 2007-03-26 01:54 MST ------- Well a bit more information is appreciated init 3 sax2 -r ---> /var/log/SaX.log Thanks -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ------- Comment #2 from one_way@online.de 2007-03-26 11:23 MST ------- Created an attachment (id=126554) --> (https://bugzilla.novell.com/attachment.cgi?id=126554&action=view) Logfile of SaX2 As requested, here is the log of SaX. I use the proprietary NVidia driver, as you see. However, the problem might be related to #256276: Suddenly, despite not having changed my configuration, the framebuffer device, like SaX, also doesn't allow higher resolutions than 800x600. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ------- Comment #3 from ms@novell.com 2007-03-27 02:22 MST ------- Hmm, I can't see why the configuration should be messed up ? Your monitor wasn't detected that's correct so the default of your active frame buffer which runs at 800x600 is chosen. I think if you call the command hwinfo --monitor you will get pretty much the same information. - So was this monitor detected correctly in former times ? - Is there a regression ? According to the log the configuration is as good as it can be. - Does manually selecting the monitor model from the list work for you ? Thanks -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ------- Comment #4 from one_way@online.de 2007-03-27 08:53 MST ------- You're right, "hwinfo" gives the same output. So the problem is probably not because of SaX, but somewhere else. Maybe the report should be reassigned? To answer your questions: 1. The monitor has been detected correctly for several major SuSE versions now (hardware configuration has not changed for years). But with the factory distribution some time in Jan/Feb, the bootsplash stopped working - a minor annoyance I didn't really take seriously. Looking back this was probably the time when the monitor-os communication got screwed up. I probably just didn't notice the problem with SaX as I use it very seldom. 2. I don't know. 3. Manually selecting a higher resolution LCD preset from the list makes SaX crash without any error message. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 one_way@online.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|one_way@online.de | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |one_way@online.de ------- Comment #5 from ms@novell.com 2007-03-27 09:11 MST ------- ok, so two problems here whereas the first one is not in my scope. Concerning 3) that's bad and should not happen. Could you give me a detailed work flow which GUI elements of sax you have used so that I have a chance to reproduce the crash ? Thanks -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ------- Comment #6 from one_way@online.de 2007-03-27 10:47 MST ------- Created an attachment (id=126812) --> (https://bugzilla.novell.com/attachment.cgi?id=126812&action=view) logfile as created if launched as "sax2" from runlevel 3 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ------- Comment #7 from one_way@online.de 2007-03-27 10:53 MST ------- Created an attachment (id=126814) --> (https://bugzilla.novell.com/attachment.cgi?id=126814&action=view) logfile as created if launched by yast2 (gui) from runlevel 5 I attached two /var/log/SaX.log-attachements. 1. SaX2 launched from runlevel 3 text console: SaX starts up its X-Server, but as soon as you try to select another monitor from the list, it crashes without any hint why. 2. SaX2 launched from YaST2 on a graphical GUI (KDE): YaST2 either quits quietly as in 1., or, as it just happened with the given logfile, it freezes the whole GUI (mouse pointer movable, STRG+ALT+Fx switches you to a working text console, but nothing else in X is working). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 one_way@online.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|one_way@online.de | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |sndirsch@novell.com ------- Comment #8 from ms@novell.com 2007-03-28 01:15 MST ------- - I will track down the mentioned problem of 1) in the bug report you opened for it thanks. - Spoken about 2) I don't think it's a sax problem it looks like a severe X11 problem: xapi: xcb_xlib.c:42: xcb_xlib_lock: Assertion `!c->xlib.lock' failed. Stefan is this a known issue ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ms@novell.com Status|NEW |NEEDINFO Info Provider| |ms@novell.com ------- Comment #9 from sndirsch@novell.com 2007-03-28 01:28 MST -------
xapi: xcb_xlib.c:42: xcb_xlib_lock: Assertion `!c->xlib.lock' failed. This is a known issue in X11 apps or libs on top of X11, which make unbalanced use of LockDisplay/UnlockDisplay. It might be libqt. I need at least a gdb backtrace to investigate this.
-- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fruell@novell.com ------- Comment #10 from ms@novell.com 2007-03-28 01:31 MST ------- *** Bug 258107 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 fruell@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ms@novell.com | ------- Comment #11 from fruell@novell.com 2007-03-28 04:30 MST ------- The bugtrace Marcus requested in Bug 258107. (NB: I updated everything to Factory, it happened with alpha 2 as well.) linux-5ahs:~ # rpm -aq sax2\* sax2-tools-8.1-121 sax2-libsax-perl-8.1-121 sax2-libsax-8.1-121 sax2-debuginfo-8.1-121 sax2-gui-8.1-121 sax2-ident-8.1-121 sax2-8.1-121 linux-5ahs:~ # gdb /usr/sbin/xapi GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-suse-linux"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/sbin/xapi [Thread debugging using libthread_db enabled] [New Thread -1221956848 (LWP 3893)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1221956848 (LWP 3893)] 0xb7d14cdc in operator== () from /usr/lib/libqt-mt.so.3 (gdb) bt #0 0xb7d14cdc in operator== () from /usr/lib/libqt-mt.so.3 #1 0xb7add06b in QComboBox::setCurrentText () from /usr/lib/libqt-mt.so.3 #2 0x080b746d in SaXGUI::SCCMonitorDisplay::setMonitorResolution ( this=0x81d73a8, res=@0x8cedec8) at monitor/monitordisplay.cpp:562 #3 0x080cbdf7 in SaXGUI::SCCMonitorModel::slotOk (this=0x81f21d8) at monitor/monitormodel.cpp:508 #4 0x080e4458 in SaXGUI::SCCMonitorModel::qt_invoke (this=0x81f21d8, _id=46, _o=0xbf901d58) at monitor/moc_monitormodel.cpp:127 #5 0xb7a417cd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #6 0xb7a4240d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #7 0xb7daa04c in QTabDialog::applyButtonPressed () from /usr/lib/libqt-mt.so.3 #8 0xb7daa46b in QTabDialog::qt_emit () from /usr/lib/libqt-mt.so.3 #9 0xb7a41789 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #10 0xb7a4240d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0xb7d85fbc in QButton::clicked () from /usr/lib/libqt-mt.so.3 #12 0xb7ad5a5d in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3 #13 0xb7a7a120 in QWidget::event () from /usr/lib/libqt-mt.so.3 #14 0xb79e20f7 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #15 0xb79e30f1 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #16 0xb7980c37 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #17 0xb797fa1d in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #18 0xb7990ab4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #19 0xb79f8be0 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 ---Type <return> to continue, or q <return> to quit--- #20 0xb79f8a76 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #21 0xb79e1abf in QApplication::exec () from /usr/lib/libqt-mt.so.3 #22 0x08066ce8 in main (argc=Cannot access memory at address 0x1 ) at xapi.cpp:225 #23 0xb7432e5c in __libc_start_main () from /lib/libc.so.6 #24 0x080595d1 in _start () (gdb) next Single stepping until exit from function _ZeqRK7QStringS1_, which has no line number information. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@novell.com AssignedTo|sndirsch@novell.com |ms@novell.com Status|ASSIGNED |NEW ------- Comment #12 from sndirsch@novell.com 2007-03-28 04:38 MST ------- Hmm ... this is a segfault, not an assertion in libxcb. Reassigning to Marcus for now. I think we should investigate the libxcb assertion seperately from this one. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257323 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #13 from ms@novell.com 2007-03-28 06:56 MST ------- yes there is a bug, fixed this one. Please open up a new bug for the libxcb assertion problem. Thanks -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com