Red Hat Bugzilla – Bug 67117
xosview does not work
Last modified: 2007-11-30 17:06:51 EST
Description of Problem:
xosview does not work. Looks like it gets stuck when reading /proc/stat
Version-Release number of selected component (if applicable):
An xosview window popping up
Probably should be dropped from the distribution.
i assume you have installed kernel-smp-2.4.18-4. You have to install
xosview-1.8.0-3. It should work. You find xosview-1.8.0-3 in rawhide
This should be rebuilt for 7.x, AS as well as the rawhide package has some
error: failed dependencies:
libgcc_s.so.1 is needed by xosview-1.8.0-8
libgcc_s.so.1(GCC_3.0) is needed by xosview-1.8.0-8
libstdc++.so.5 is needed by xosview-1.8.0-8
libstdc++.so.5(GLIBCPP_3.2) is needed by xosview-1.8.0-8
I should have written "Advanced Server" instead of AS in the last comment. Doh.
Works with xosview-1.8.0-11 for me. Closing bug.
Reopening bug, because -- as far as I can see -- there is no package for 7.3 and
Advanced Server available which fixes that problem. The 1.8.0-11 package is not
an official erratum for these versions, is it?
*** Bug 76950 has been marked as a duplicate of this bug. ***
Changing product to Advanced Server (as this is probably where it matters more
because AS will be around for wuite some time). Please fix it for 7.3, too --
should work with the same src.rpm, I guess.
Report from a customer via web ticket indicates that xosview-1.7.3-5 gives a
"Segmentation Fault" after he updated to errata kernel 2.4.9-e.16smp. I could
not reproduce a "Segmentation Fault" on my test unit, but the only option of
xosview I could make work was 'xosview -v' (prints the version). I ran an strace
of xosview and captured the output, (attached, or will be soon).
Created attachment 91021 [details]
it's fixed in xosview-1.7.3-6.72.1, which you can find it in
Chris/Nils: could you please test it?
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.