Hide Forgot
Description of problem: Launching xfig causes system to freeze. System freezes as soon as xfig loads and its window appears. There is no response to mouse or keyboard activity, and keyboard gets no power. Cannot switch to virtual consoles (Ctrl-Alt-F<num>). A reboot is necessary. /var/log/messages has no relevant output. Version-Release number of selected component (if applicable): xfig-3.2.5-25.b.fc14.i686 How reproducible: Always Steps to Reproduce: 1. Launch xfig Actual results: System freezes Expected results: Additional info: From lspci output 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] (rev 01)
Sounds like an X-server issue to me, changing component.
Created attachment 474390 [details] Xorg.0.log.old Attaching Xorg.0.log.old. I couldn't find any messages in it related to the crash though.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 475556 [details] dmesg
Created attachment 475557 [details] Xorg.0.log after crash
Created attachment 475558 [details] Xorg.0.log.old after crash
Created attachment 475559 [details] Xorg.1.log after crash
Created attachment 475560 [details] Xorg.9.log after crash
Created attachment 475561 [details] /var/log/messages after crash
Added drm.debug=0x04 to kernel command line, rebooted, ran xfig, and reproduced freeze. Recycled system, and attached log files above are from immediately after that.
(In reply to comment #3) > Thanks for the bug report. We have reviewed the information you have provided > above, and there is some additional information we require that will be helpful > in our diagnosis of this issue. > > Please add drm.debug=0x04 to the kernel command line, restart computer, and > attach > > * your X server config file (/etc/X11/xorg.conf, if available), I don't have an /etc/X11/xorg.conf In addition, xfig doesn't cause a freeze if launched from an xinit session (xinit -- :1).
Any progress on this? I can still reproduce this problem xorg-x11-drv-openchrome-0.2.904-8.fc14.i686
It is strange, I don’t see anything wrong in the Xorg world anywhere in your logs (only pulseaudio and NetworkManager having various problems). Is it certainly caused by xfig? Isn't it for example timing (e.g., xfig being a first program you run after loing)? If you run program before xfig does it change anything? Or if you just wait a minute after login? Thank you for the patience with us
(In reply to comment #13) > It is strange, I don’t see anything wrong in the Xorg world anywhere in your > logs (only pulseaudio and NetworkManager having various problems). > > Is it certainly caused by xfig? Isn't it for example timing (e.g., xfig being a > first program you run after loing)? If you run program before xfig does it > change anything? Or if you just wait a minute after login? > It is certainly not caused due to timing. I've reproduced it with xfig being run at different times; sometimes with the machine being up for several days and many graphical applications including firefox, konsole being run. It always happens when xfig is launched -- whether the first thing after starting desktop env, several hours or days later, and with or without any other applications running. However, the problem doesn't exist if xfig is run from a barebone X session (xinit -- :1) and run xfig without starting anything else. Any explanation for this? What's different here? It's the same X driver with all the same extensions. I feel better logging can help here.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping