Bug 130168 - Can't start "Graphics cards and Monitors" - log file attached
Summary: Can't start "Graphics cards and Monitors" - log file attached
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: PC SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: Klaus Kämpf
URL: http://www.xfree86.org/4.5.0/I1284.ht...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-22 20:28 UTC by Bryce Nesbitt
Modified: 2005-11-07 09:33 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Log from failed "sax2" startup. Run without -r flag. (1.60 KB, text/plain)
2005-11-04 18:16 UTC, Bryce Nesbitt
Details
xorg.conf that causes sax2 to fail (includes corrected modelline for SGI 1600SW). (5.29 KB, application/octet-stream)
2005-11-04 18:18 UTC, Bryce Nesbitt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bryce Nesbitt 2005-10-22 20:28:36 UTC
The "Graphics cards and Monitors" section of YaST no longer functions on my
computer.  It worked for a while,  not now it fails silently.  /var/log/YaST shows:


2005-10-22 13:19:27 <1> linux(8015) [YCP] CommandLine.ycp:1141
----------------------------------------
2005-10-22 13:19:27 <1> linux(8015) [YCP] CommandLine.ycp:1142 Command line
interface started
2005-10-22 13:19:27 <1> linux(8015) [wfm] Y2CCWFM.cc(createInLevel):153 Parsing
finished
2005-10-22 13:19:27 <1> linux(8015) [Interpreter] clients/x11.ycp:47 Calling
YaST client XMain (arguments: [true, true])
2005-10-22 13:19:35 <1> linux(8015) [YCP] clients/XMain.ycp:47 SaX finished with
exit code: <0>
2005-10-22 13:19:35 <1> linux(8015) [Interpreter] clients/x11.ycp:47 Called YaST
client returned: `next
2005-10-22 13:19:35 <1> linux(8015) [YCP] clients/x11.ycp:51 Running
displaymanager SuSEconfig module
2005-10-22 13:19:35 <2> linux(8015) [qt-ui] YQUI_core.cc(qMessageHandler):640
qt-warning: Session management error: Authentication Rejected, reason : None of
the authentication protocols specified are supported and host-based
authentication failed
2005-10-22 13:19:35 <2> linux(8015) [qt-ui]
YQUI_x11.cc(loadPredefinedQtTranslations):417 Can't load translations for
predefined Qt dialogs from /usr/lib/qt3/translations/qt_en.qm
2005-10-22 13:19:35 <1> linux(8015) [qt-ui]
YQUI_core.cc(processCommandLineArgs):214 Qt argument: qt
2005-10-22 13:19:35 <1> linux(8015) [qt-ui] YQUI_core.cc(calcDefaultSize):326
Default size: 1119x681
2005-10-22 13:19:35 <3> linux(8015) [Interpreter] clients/x11.ycp:113 Can't
convert value 'true' to type 'symbol'
2005-10-22 13:19:35 <1> linux(8015) [wfm] WFMSubAgent.cc(~WFMSubAgent):41
Deleting SubAgent: 0 scr
2005-10-22 13:19:35 <1> linux(8015) [liby2] genericfrontend.cc(main):497
Finished YaST2 component 'y2base'


My system is US english, with Gnome.
I'm stuck.
What can I do short of reinstalling from scratch?
Comment 1 Michael Gross 2005-10-24 12:31:20 UTC
Stanlislav: Can you help here?
Comment 2 Marcus Schaefer 2005-10-24 14:15:38 UTC
to solve your problem simply call sax2 from a shell instead of the
control center.

I assume this is the tty problem already solved but
honestly;  "It worked for a while, not now it fails silently"
is not a report I can provide a fix for

I don't have any clue what is going on here

*** This bug has been marked as a duplicate of 117439 ***
Comment 3 Bryce Nesbitt 2005-10-24 16:40:43 UTC
What is at genericfrontend.cc line 497, which is causing the program to exit?

You should know that I get the exact same failure when starting sax2 from a shell.
Comment 4 Marcus Schaefer 2005-10-24 17:33:09 UTC
Hmm, genericfrontend.cc is code from liby2util. I don't know about
that code it's not written by me. I think we are a bit off topic right
now. The problem is that you cannot start sax2 is this correct ?

If so please call:

    sax2 -r

and send me the log file /var/log/SaX.log. You should know that sax2
has nothing to do with yast2. In principal these are two different
applications whereas yast2 is using libsax for X11 related tasks

Thanks
Comment 5 Bryce Nesbitt 2005-11-04 18:14:34 UTC
CAUGHT IT!

Ok: it appears that sax2 got upset that I modified the xorg.conf file by myself.  In such a case, it quits silently halfway through startup:

bryce@linux:~> sax2
SaX: root Password:
SaX: initializing done, using cache data...
SaX: startup

bryce@linux:~>

Adding the "-r" flag causes sax2 to work.  Log files attached.
Comment 6 Bryce Nesbitt 2005-11-04 18:16:12 UTC
Created attachment 56515 [details]
Log from failed "sax2" startup.  Run without -r flag.
Comment 7 Bryce Nesbitt 2005-11-04 18:18:59 UTC
Created attachment 56516 [details]
xorg.conf that causes sax2 to fail (includes corrected modelline for SGI 1600SW).

Modelines from http://www.xfree86.org/4.5.0/I1284.html
See also
Comment 8 Marcus Schaefer 2005-11-07 09:33:24 UTC
ok, I added a check for that, fixed

Thanks for testing