x11vnc able to segfault xorg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Fix Released
|
High
|
Bryce Harrington |
Bug Description
Binary package hint: xorg
Lots of discussion over at: http://
But the gist of it is, x11vnc is able to segfault xorg. Quite simple to reproduce. Find a "victim" machine and boot it up to the gdm login prompt. Then ssh into the machine and run:
# DISPLAY=:0 x11vnc
(notice logged in as root) and then connect with a vnc client. Try to log in and very quickly the vnc connection will be closed and when you reconnect you will be at a new login prompt. That's because the last X11 server crashed. Check out /var/log/
(gdb) attach 3038
...
0x00007f7652ee9485 in ?? () from /lib/libdrm_
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00007f765395b662 in RecordAReply (pcbl=0x7e29a0, nulldata=0x0, calldata=
in ../../record/
(gdb)
[K(gdb) bt
#0 0x00007f765395b662 in RecordAReply (pcbl=0x7e29a0, nulldata=0x0, calldata=
#1 0x000000000043191c in _CallCallbacks (pcbl=0x7e29a0, call_data=
#2 CallCallbacks (pcbl=0x7e29a0, call_data=
#3 0x0000000000460091 in WriteToClient (who=0x41c8270, count=60, __buf=0x3d0b838) at ../../os/io.c:800
#4 0x00007f765395a8d2 in RecordFlushRepl
at ../../record/
#5 0x00007f765395a946 in RecordFlushAllC
at ../../record/
#6 0x000000000043191c in _CallCallbacks (pcbl=0x7e29a8, call_data=0x0) at ../../dix/
#7 CallCallbacks (pcbl=0x7e29a8, call_data=0x0) at ../../dix/
#8 0x000000000045ffd4 in WriteToClient (who=0x41c8270, count=60, __buf=0x3d0b838) at ../../os/io.c:824
#9 0x00007f765395a8d2 in RecordFlushRepl
at ../../record/
#10 0x00007f765395a946 in RecordFlushAllC
at ../../record/
#11 0x000000000043191c in _CallCallbacks (pcbl=0x7e29a8, call_data=0x0) at ../../dix/
#12 CallCallbacks (pcbl=0x7e29a8, call_data=0x0) at ../../dix/
#13 0x000000000045ffd4 in WriteToClient (who=0x41c8270, count=60, __buf=0x3d0b838) at ../../os/io.c:824
#14 0x00007f765395a8d2 in RecordFlushRepl
at ../../record/
[Repeats endlessly...]
ProblemType: Bug
Architecture: i386
Date: Sat Feb 20 17:09:35 2010
DistroRelease: Ubuntu 9.10
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelMo
Package: xorg 1:7.4+3ubuntu10
ProcCmdLine: auto BOOT_IMAGE=ubuntu root=/dev/
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu10
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SourcePackage: xorg
Uname: Linux 2.6.31-19-generic i686
dmi.bios.date: 10/23/2003
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080009
dmi.board.name: P4P800S
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-19-generic
Related branches
affects: | xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu) |
tags: | added: karmic |
affects: | xorg (Ubuntu) → xorg-server (Ubuntu) |
Changed in xorg-server (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in xorg-server (Ubuntu): | |
status: | Confirmed → Triaged |
Really? This is an nvidia specific crash? Can I ask how you came to that conclusion, just for my education, so that I can better diagnose failures in the future?