Actually, this would be the correct output order (copy paste mistake):
ButtonPress event, serial 37, synthetic NO, window 0x4a2,
root 0x291, subw 0x0, time 2876858, (164,178), root:(167,233),
state 0x10, button 3, same_screen YES
MotionNotify event, serial 37, synthetic NO, window 0x4
I have fixed this bug in my git branch and I'll upload a new package as
soon as we get a driver that is compatible with Natty.
Here's the relevant commit:
https://github.com/tseliot/nvidia-graphics-drivers/commit/6c587668d7c6904e955bd7acecc6511c47ca4d5b
--
You received this bug notification beca
*** This bug is a duplicate of bug 626967 ***
https://bugs.launchpad.net/bugs/626967
Yeah, looks quite similar to 626967; there were a lot of reports of that
issue on maverick. I think it's largely sorted out in natty so worth
retesting. It was apparently fixed by this commit:
http://cgit.f
** Summary changed:
- [i965gm] GPU lockup cd4b7311
+ [i965gm] GPU lockup playing DVD movie with VLC (no gpu error codes)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/716739
Mind retesting this on natty? I seem to recall other bug reports about
X lockups when closing skype video that are thought to be fixed now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-
*** This bug is a duplicate of bug 711999 ***
https://bugs.launchpad.net/bugs/711999
** This bug has been marked a duplicate of bug 711999
[i915g] GPU lockup - (ESR: 0x0001 IPEHR: 0x0211) Hangcheck timer
elapsed... failed to reset chip
* You can subscribe to bug 711999 by followin
Ok, thanks for following up. Possibly was addressed by the gpu fix in
2:2.14.0-1ubuntu8 - bug report #719751 is almost identical to this one
and was reportedly improved by that. In fact I think I'll dupe that one
here.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete =>
Could be this is a dupe of bug #711999 which is now believed fixed.
If not, well see my previous comment for directions. :-)
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => New
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
--
Y
Thanks for following up
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/719061
Title:
upgrade
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => Medium
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.l
The X server is also sometimes reseting itself (and thus closing the
current X session) or even freezing the system. syslog entries at the
relevant time:
Feb 18 23:07:08 obiwan kernel: [ 2582.965683] NVRM: Xid (0001:00): 6, PE0001
Feb 18 23:07:08 obiwan kernel: [ 2582.985837] NVRM: Xid (0001:00):
Public bug reported:
Binary package hint: xorg
On Maverick when openning some applications the xorg crashes, it seems
to be related to a high CPU or memory load. It could also be related to
multimedia or audio, because it happens a lot when i was using flash
video, virtualbox or skype, it also ha
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/721577
Title:
xorg crashes on heavy load
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to
One other question - is this a regression? If so any ideas what the
last working version(s) was?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/718019
Title:
XRender not wor
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => New
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubunt
** Changed in: xserver-xorg-video-intel (Ubuntu Natty)
Status: Incomplete => New
** Changed in: xserver-xorg-video-intel (Ubuntu Natty)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-in
i forgot to say, that before, when i got a heavy load, the system just freezed
for a second until it was able to continue
with the initial maverick packages it was not happening, so i ignore if it is a
kernel or xorg update
--
You received this bug notification because you are a member of Ubunt
Well I have compiled new drivers I have installed in debug mode and to
my surprise I could run without xorg.conf first! This debug mode
attempts to do so without the debug mode to see. I mine the log file
** Attachment added: "Running without xorg.conf"
https://bugs.launchpad.net/ubuntu/+sourc
*** This bug is a duplicate of bug 711409 ***
https://bugs.launchpad.net/bugs/711409
** This bug has been marked a duplicate of bug 711409
[MASTER] -nvidia broken after Jan 31st updates, because it does not yet
support xserver 1.10
* You can subscribe to bug 711409 by following this link:
Heya,
We've updated quite a few bits and pieces the past couple weeks
including fixes for several gpu lockups, including one that has an IPEHR
value close to yours. Would you mind updating to latest natty and
confirming whether or not you still see this X lockup?
** Changed in: xserver-xorg-vide
Hi Vadim,
We've posted several gpu fixes in the couple weeks since you filed this
report, including one or two that fix memory errors, although none that
exactly match your case. But would you mind updating to latest natty
and see if you can reproduce the lockup, and report here either way?
If y
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
https://bugs.launchpad.net/bugs/720381
Title:
Xorg crashed with SIGSEGV in _start()
___
Mailin
no prob, thanks for the extra data.
So, at this stage, assuming that apw, stefano, kees, and eric are all
seeing roughly the same bug, taking all their observations into account,
the picture starts to look like this:
It appears there was a regression introduced with the introduction of
the 2.6.38
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/718019
Title:
XRender not working on i945
*** This bug is a duplicate of bug 720381 ***
https://bugs.launchpad.net/bugs/720381
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 720381
Xorg crashed with SIGSEGV in _start()
* You can subscribe to bug 720381 by following this link:
https://bugs.launchp
*** This bug is a duplicate of bug 720381 ***
https://bugs.launchpad.net/bugs/720381
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 720381
Xorg crashed with SIGSEGV in _start()
* You can subscribe to bug 720381 by following this link:
https://bugs.launchp
Hmm, unfortunately the retracer wasn't able to generate a useful stack
trace. I've asked them to turn it off, so I can manually get a
stacktrace next time someone reports this bug. If you or one of the
folks on dupes wouldn't mind creating a new install with latest natty
bits and reproducing the
This can't be right...
Identical results on a Maverick live session.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/718019
Title:
XRender not working on i945GM
** Also affects: openchrome
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
https://bugs.launchpad.net/bugs/665463
Title:
[VX800] White screen after installin
Hi Daniel,
I think you have have stumbled onto our elusive out-of-memory-
whoops-X-crashes bug. I have a *suspicion* that X crashing is just a
symptom here, and that the bug is not actually in X, but something else
unique to the livecd environment which leaks memory badly. Once memory
gets low e
Public bug reported:
Binary package hint: xserver-xorg-video-intel
this happens immediately after log in the gnome desktop
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-1ubuntu9
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
https://bugs.launchpad.net/bugs/721631
Title:
[gm45] GPU lockup 9a66a985 (EIR: 0x0010 ESR: 0x0010 PGTBL_ER:
0x0001 IPEHR: 0x0100)
___
Same here ...
Thx for the info ...
BTW, I used the Synaptic Package Manager to remove xserver-xorg-video-
nouveau and it also removed xserver-xorg-video-all.
Running just fine so far w/o them ... will only reinstall if something
claims to need them.
Thanks for your help.
John
--
You received
Hey aanno,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey gogo,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issue
Hey Fsolda,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey Alumni,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey iwtctw,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey Diska,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey BojanNS,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an is
Hey Josef,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey M0ses,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey Collin,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
Hey siucdude,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an i
Hey Scott,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
Hey scorpionslack,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still
Hey David,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey jukarimov,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an
Hey Mzombira,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an i
Hey Owais,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey HacKurx,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an is
Hey slxviper,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an i
Hey Sloth.Spot,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an
Hey martyfelker,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still a
Hey Facundo,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an is
Hey Dmitry,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirms
Hey Susan,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey Matteo,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey Adam,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issue
Hey Serge,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey Dmity,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey kennedy,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an is
Hey Ken,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issue
Hey alexandre,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an
Hey alexandre,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an
Hey Daniel,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey Steve,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey Douglas,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an is
Hey Douglas,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an is
Hey martyfelker,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still a
Hey John,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issue
Hey Thomas,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey Rollo,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey Aislan,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey wim,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issue
Hey Tommi,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issu
Hey bp,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issue f
Hey Sascha,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an iss
Hey Mike,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an issue
Hey Charlie,
Thanks for testing maverick during its development period. Unfortunately it
looks like this bug report didn't get attention during the maverick development
period. But I see there's not been more comments on the bug since the release,
which makes me wonder if this is still an is
101 - 200 of 386 matches
Mail list logo
