| Summary: | some applications crash the x server in multiscreen mode | ||
|---|---|---|---|
| Product: | xorg | Reporter: | tim blechmann <tim> |
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> |
| Status: | RESOLVED NOTOURBUG | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
tim blechmann
2011-05-17 05:12:15 UTC
Hi Tim, First of all the bug report you linked is about a issue relating both the blob (nvidia's proprietary driver) and nouveau Thus: * Most likely the issue is not nouveau related, but nevertheless take a look further down 1. We do *not* handle bug reports of the blob 2. The bug report contains almost no information about nouveau. There are logs of the blob (non relevant to us) 3. Please take a look at "How to report bugs" [1] 4. But beforehand drop by our FAQ [2] and troubleshooting [3] section 5. It appears that the "bug: [mi] EQ overflowing" is already covered [4] Note: We are *not* the maintainers of Ubuntu's stack nor the xorg-edgers. Therefore if you mention them please use the corresponding commits they are based on. Therefore: I'm closing this bug as NOTOURBUG, and please do provide a reasonable bug report, after you have checked that one does not exist [1] http://nouveau.freedesktop.org/wiki/Bugs [2] http://nouveau.freedesktop.org/wiki/FAQ [3] http://nouveau.freedesktop.org/wiki/TroubleShooting [4] http://nouveau.freedesktop.org/wiki/TroubleShooting#Igetthe.22EQoverflowing.22error P.S. I'm a Ubuntu user, to the extent that I do not want to configure all the userspace by myself. I do configure and build the kernel, libdrm, ddx and mesa by myself (simple script does the job for me) sorry for trying to report and resolve a bug, which at least in my case, is definitely related to nouveau Yet another relatively long reply but I believe it is necessary 1. How about looking at the log for about 20 secs - you would have easily seen the issue - "EQ overflow" 2. Then use that information to go through the relevant sections - faq/troubleshooting 3. And provide a simple clear report indicating the issue and following the guides (see the bugs section) 4. I would *not* have pointed out to bug report, that is not well defined - not to mention that your name does not appear in it (i.e. probably lacks information provided by yourself) My approach (not only) would be - spend 5(or less) minutes reading, another up to 5 thinking on how to formulate the issue, and 2 minutes for write up. I realize I sound like a prick although I'm a bit fed up with some users' *lack of interest to actually resolve issues* - they just want to report that "it does not work" Hopefully you will see some of the positive things that have been said in here > 1. How about looking at the log for about 20 secs - you would have easily seen > the issue - "EQ overflow" tim@moka:~/workspace/linux-2.6$ cat /var/log/Xorg.*|grep EQ [ 11.505] (II) Initializing built-in extension BIG-REQUESTS [ 129.374] (II) Initializing built-in extension BIG-REQUESTS [ 42.459] (II) Initializing built-in extension BIG-REQUESTS [ 36.257] (II) Initializing built-in extension BIG-REQUESTS [ 165.193] (II) Initializing built-in extension BIG-REQUESTS either it is a different issue, or it the log is not synced to disc > 2. Then use that information to go through the relevant sections - > faq/troubleshooting > 3. And provide a simple clear report indicating the issue and following the > guides (see the bugs section) * install ubuntu 11.04 * select nouveau * run xrandr --output VGA-1 --off --output DVI-I-1 --mode 1680x1050 --pos 1680x0 --rotate normal --output HDMI-1 --mode 1680x1050 --pos 0x0 --rotate normal * run gitk * see how your x server restarts > 4. I would *not* have pointed out to bug report, that is not well defined - not > to mention that your name does not appear in it (i.e. probably lacks > information provided by yourself) unfortunately, my x debugging capabilities are a bit limited: if i try to attach gdb to the x process, x freezes, which makes it a bit hard to get a good backtrace > I realize I sound like a prick although I'm a bit fed up with some users' *lack > of interest to actually resolve issues* - they just want to report that "it > does not work" * i experience a bug * i check the tracker of my distribution and find a related issue * i subscribe to the bug * nothing happens * i stop using one of my crucial applications * i submit a bug report upstream, pointing to the downstream report * it initially gets `resolved' as `notourbug' i am maintaining an open source project myself. but i have never told any of my users that it is their problem, if my code crashes. On Tue, 17 May 2011 17:34:38 +0100, <bugzilla-daemon@freedesktop.org> wrote: > https://bugs.freedesktop.org/show_bug.cgi?id=37284 > > --- Comment #4 from tim blechmann <tim@klingt.org> 2011-05-17 09:34:37 PDT --- > ... > either it is a different issue, or it the log is not synced to disc The above has been taken from the latest Xorg.log in the bug report and clearly indicated that the issue was experienced using nouveau > ... > * run xrandr --output VGA-1 --off --output DVI-I-1 --mode 1680x1050 --pos > 1680x0 --rotate normal --output HDMI-1 --mode 1680x1050 --pos 0x0 --rotate > normal you kind of missed to mentioned *anywhere* this step > ... > * i check the tracker of my distribution and find a related issue * Ensure that the issue is the same as the one I'm experiensing > ... > * i stop using one of my crucial applications * Or try to find a workaround * I read the bugs section > * i submit a bug report upstream, pointing to the downstream report > * it initially gets `resolved' as `notourbug' > > i am maintaining an open source project myself. but i have never told any of my > users that it is their problem, if my code crashes. > Please read the bugs section [1] and open another bug. Thanks [1] http://nouveau.freedesktop.org/wiki/Bugs > > either it is a different issue, or it the log is not synced to disc > The above has been taken from the latest Xorg.log in the bug report and clearly > indicated that the issue was experienced using nouveau well, this is the reason, why i am reporting the bug here ... after all, this is the bug tracker for nouveau, isn't it? > > ... > > * run xrandr --output VGA-1 --off --output DVI-I-1 --mode 1680x1050 --pos > > 1680x0 --rotate normal --output HDMI-1 --mode 1680x1050 --pos 0x0 --rotate > > normal > you kind of missed to mentioned *anywhere* this step the first sentence of my bug report was: "i am running my x server in multiscreen mode" the subject: "some applications crash the x server in multiscreen mode" > > ... > > * i check the tracker of my distribution and find a related issue > * Ensure that the issue is the same as the one I'm experiencing the symptoms are the same: nouveau + multiscreen + gitk/git gui == crash > > ... > > * i stop using one of my crucial applications > * Or try to find a workaround like stop using gitk? i've been working without it for almost two months ... ... sorry, but i have already spent too much time with this bug today ... will reinstall ubuntu 10.10 and the proprietary driver, since i need to get some work done |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.