|
Bugzilla – Full Text Bug Listing |
| Summary: | sax2: does not work from yast or command line | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Marian Kechlibar <inglor> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Yast logs immediately after last failed attempt to start sax2
The SaX log immediately after the "init 3" experiment. |
||
|
Description
Marian Kechlibar
2007-12-14 12:14:26 UTC
try to call init 3 sax2 --> does this work ? --> send the log file /var/log/SaX.log thanks Created attachment 187811 [details]
The SaX log immediately after the "init 3" experiment.
When I try to run init 3 and sax, I get the following output from sax: Your current configuration will not be read inů No X-server running. Will start own server if needed. /usr/sbin/xcmd: symbol lookup error: /usr/lib/libsax.so.7: undefined symbol _ZTI11QTextStream terminate called after throwing an instance of std::logic_error what(): basic_string::_S_construct NULL not valid SPP: Prepare device [0] profile: Depth24 SPP: Prepare device [0] profile: NVidia SPP: Including device [0] profile script: NVidia SaX: Startup prepared profiles A flash of screen ... but nothing changes (heh, this last line reminds me of German band Blind Guardian's lyrics ... never mind) *whoops* it seems something in your installation is broken. the QTextStream symbol is part of the Qt3 library which is used by libsax. I guess you installed/uninstalled something in this field you mentioned your system was incompletely updated. I'm pretty sure this is the problem. To get sax2 working again I suggest to install all sax2 and dependent packages again *** This bug has been marked as a duplicate of bug 344237 *** |