** Description changed:

  Binary package hint: xorg
  
  I'm not sure where to report this, I think it affects X worst.
  
  OK, I have two laptops here on the table, connected through a LAN. One
  has up-to-date Edgy, the other up-to-date Feisty. The Feisty one (which
  is where the bug occurs) has a Mobile 945GM/GMS/940GML Express
  Integrated Graphics Controller (as reported by hal-device-manager).
  
  On the Feisty I log in (normal Gnome session), I start a terminal, and I
  ssh to the other one, forwarding X:
  
  "ssh -X [EMAIL PROTECTED]"
  
  I authenticate myself, and I get a ssh shell to the Edgy machine. I can
  run pretty much anything now, and it displays correctly on the Feisty
  display. However, if I run glxgears on the Edgy machine, I have two
  issues: First (and not very grave), it complains about DRI not working
  (normal, I suppose), then it starts running in indirect mode; the window
  is correctly displayed on the Feisty screen, but the animation is very
  choppy (on the order of 1fps). However, glxgears reports running at
  ~1000fps (+/-200). I was under the impression that it should look quite
  well, too.
  
  Second -- and this is the problem -- if I kill the first glxgears
  (ctrl-c) and I run another one again, the X server (on Feisty) displays
  a window without any contents (just black), freezes for a bit, and then
  either freezes completely or crashes. (Actually, it restarts; I assume
  it's because it crashes.) I've done this three times in a row; the first
  two times X restarted, the last time it just froze and I rebooted after
  a while.
  
  The Edgy machine kept running normally --- I didn't have to restart it
  when the Feisty X crashed.
  
  I can do this again and gather whatever debug information you might
  need, I'm waiting for instructions. I have a bit of a vague idea of how
  X works, but I really don't know where to start diagnosing this issue.
+ 
+ I don't know if I should mark this as a security vulnerability. It needs
+ a log-in on both machines. It does allow a normal user to crash the X
+ server, so it might be usable as a sort of denial-of-service against
+ other users, but then again, I'm not sure that's that hard to do.

-- 
opengl over remote X (over ssh) crashes X
https://launchpad.net/bugs/83339

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to