On Sat, Nov 06, 2004 at 01:22:44AM +0100, Kevin Price wrote: > I think I have this same bug here with xfree 4.3.0.dfsg.1-8. After > switching the xserver-xfree86 package back to dfsg.1-4 it worked fine. 1.8 > locks up my X from time to time when I have a couple of "Konsole" windows > in use. This somaetimes happens after a few minutes and sometimes after a > few hours. > > I cannot verify the "gettimeofday" problem since I didn't strace. My kernel > is > debian 2.6.8-1-686 2.6.8-4 my graphics is rage128. > > The only way for me to access the locked computer is via ttyS0 (network > might also work) and kill -9 the xserver and /etc/init.d/kdm restart. > > Please let me know if I can help you spot the problem. Otherwise I'll just > go back to dfsg.1-4 which worked fine. I'm sorry it has taken a while to get back to you. In my opinion, it's a bit soon to decide you're seeing the same bug. There is some information you could collect that would help us decide that, however: 1) You could run strace on the X server as the original submitter did. You can use strace's "-p" option to trace an already-running process. 2) You could send us information about your system configuration. The following form letter explains how, at some length. (Just FYI, you can use reportbug to follow-up to an existing bug report, so more of the following is applicable that it may appear at first blush.) [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more information is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#275117 followup" 275117@bugs.debian.org < /tmp/output If you do not have a "mailx" command on your system, you can get it by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you're receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <275117@bugs.debian.org>. Thank you! -- G. Branden Robinson | Religion is regarded by the common Debian GNU/Linux | people as true, by the wise as branden@debian.org | false, and by the rulers as useful. http://people.debian.org/~branden/ | -- Lucius Annaeus Seneca
Attachment:
signature.asc
Description: Digital signature