Bug 412481
Summary: | OOo, other apps fail with sigsegv | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Paul Williams <paulprogrammer+rh> | ||||||||
Component: | xorg-x11 | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||||||
Status: | CLOSED CANTFIX | QA Contact: | |||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | 4.6 | CC: | paulprogrammer+rh | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i386 | ||||||||||
OS: | Linux | ||||||||||
URL: | http://user.services.openoffice.org/en/forum/viewtopic.php?f=16&t=312&p=2399#p2399 | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2007-12-06 14:27:40 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Paul Williams
2007-12-05 17:52:37 UTC
Created attachment 278641 [details]
strace of soffice 2.3 failing (same as soffice 2.2 and ati's catalyst control panel)
There is a long list of issues I have with this bug: a) If you have RH support, please, file an issue through IssueTracker. You will get higher preference when going through there. If not, what kind of distro you have? CentOS? Even if you don't have the real RHEL, it wouldn't be reason to close this bug, but ... b) /opt/openoffice.org2.0/ is not coming from the packages you got with RHEL4, so we cannot resolve it here. If you want us to assist you with fixing this bug, please, reproduce this with the OpenOffice.org packages you got with RHEL4. c) ATI Catalyst Control Center is part of binary only ATI drivers. We are sorry that we cannot help you with your problem, but we are not able to support binary-only drivers. Unfortuantely, b) and c) leads me to closing this bug as CANTFIX (because we really cannot fix something we haven no source code for). If you would be able to reproduce this issue using only open source software, please, reopen this bug with the additional information. The reproducibility and straces lead me to believe there is an issue with the X libraries used by both applications. I understand that RH doesn't have access to the catalyst drivers source, but RH certainly has access to the OOo sources. This kind of attitude is what really drives me away from RH in general. If this were debian or ubuntu (or Slack back in the day), the community would be out there helping. But because it's RH, we're back to corporate only support. Thanks for nothing. Please, note my comments under a) -- I explicitly emphasized that I am not closing this bug because of not having support contract. We have thousands and thousands Fedora (and CentOS) bugs here which are not closed and we are working on them. Concerning community -- just go ahead and ask community to help! Here is the couple of tips where to go: http://www.redhat.com/mailman/listinfo/fedora-list (probably the best option) http://wiki.linuxquestions.org/wiki/Fedora (that's a little bit dated, though) http://www.fedorafaq.org/ http://fedorasolved.org/ http://www.linuxquestions.org/questions/fedora-35/ http://fedoraproject.org/wiki/ (tones of information there) There is a support contract, managed by an overworked IT executive. I don't have access to the bloody contract support portal. I use linux on the desktop -- the only one in my local organization. If I can't get routine support easily it will never propogate beyond this (in fact, because of this issue I may have to go back to windows. I can't not edit my word docs). OK, so remove that OpenOffice.org which is not from us, and reinstall the original packages from RHEL. Try if it works. If not, try again with open source drivers (ati in your case). If *then* it doesn't work, you are very welcome to reopen this bug (as I wrote in comment 2). If you will reopen this bug, please, add to this bug as attachments content of /etc/X11/xorg.conf and /var/log/Xorg.0.log as separate uncompressed attachments, to allow us to debug your problem. As far as I can tell, there was no OOo distributed with RHEL which is why I installed the OOo-provided version. This is obviously a knowledge issue on my part, and I have no access to the RH "channel management" or whatever you call the automanagement tools. Clearly, being an active user of Linux since 1994 is not qualification enough for administrating an Awesome RedHat system. Please advise. Created attachment 280081 [details]
Xorg log
Created attachment 280091 [details]
xorg configuration
(In reply to comment #8) > Please advise. Packages named like openoffice.org2-writer are part of ES and AS channels of RHEL4. (In reply to comment #9) > Created an attachment (id=280081) [edit] > Xorg log This is unfortunately still not good -- I am really sorry, but we really cannot deal with flgrx. I accept all your complaints about quality of open source drivers for ATI cards, and I can see that for somebody with real high end requirements for graphics they might be unacceptably poor, but we really need system clean of fglrx, before we can help you with crashes. I am not saying, that fglrx is of poor quality (ATI engineers can certainly say something similar about ati driver), but we have seen scores of bugs resolved just by using open source drivers instead of fglrx (or nvidia for that matter). Please, follow the instructions on http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers for the way how to make your computer clean of fglrx. This issue was resolved by moving the libGL.so.1.2 library that was replaced by fglrx driver back to the system provided version. <g> Y'all are right -- binary drivers suck. But the OSS radeon driver wedges the system -- not much of a choice. For the record, my options are limited by what the boss will buy, and today that's Dell. If I had the choice it'd be NV -- one of the older ones that works well with the OSS NV driver. Oops.. it's back when I reenable DRI. :( I guess DRI is the source of the issue. How frustrating -- so slooooo without dri. Opened a ticket with ATI: 737-1297028 |