** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/39457954/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/39457955/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39457956/Dependencies.txt
** A
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-180
(Ubuntu)
--
x11vnc able to segfault xorg
https://bugs.launchpad.net/bugs/525066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
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?
--
x11vnc able to segfault xorg
https://bugs.launchpad.net/bugs/525066
You received this bug notification because you are a member of
This bug was fixed in the package xorg-server - 2:1.10.0-0ubuntu1
---
xorg-server (2:1.10.0-0ubuntu1) natty; urgency=low
* Update to new upstream final release.
+ Drop 16-construct-paths-in-doxygen.conf.diff; included in new upstream.
* debian/patches/216_fix_sdksyms_build.dif
Are you able to reproduce this issue easily? If so, please collect a
full backtrace - see http://wiki.ubuntu.com/X/Backtracing for
directions. If not, could you describe the conditions under which the
crash tends to occur?
If this is an nvidia-specific crash, there may be nothing we can do at
the
I am using Intel Q965.
This issue can't be triggered very quickly on my machine. Normal I would
work using vnc client connected to x11vnc for a while, then close vnc
client. After about 1 minute, X would crash.
I've managed to reproduce it twice with gdb attached, here is log for
the second time.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
--
x11vnc able to segfault xorg
https://bugs.launchpad.net/bugs/525066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Triaged
--
x11vnc able to segfault xorg
https://bugs.launchpad.net/bugs/525066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
__
This bug is still there. And seems I can triggered it through some other
way days ago, e.g. open a big picture in the gwenview. But after the
recent update, I can only trigger it by x11vnc, after using vnclient for
a period of time.
--
You received this bug notification because you are a member o
Hi Sheng,
Thanks for providing the detailed backtrace. Looks like it's a stack
overflow in the client callback code when the client disappeared. The
leftover callback resulted in an endless loop.
** Description changed:
Binary package hint: xorg
Lots of discussion over at:
http://ubunt
Think the next action here is to attempt reproducing it on natty, and
then forward it upstream.
--
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/525066
Title:
x11vnc able to segfault xorg
Can't believe it just affect nvidia card, because I am not using the
nvidia card but intel ones.
** Package changed: nvidia-graphics-drivers-180 (Ubuntu) => xorg
(Ubuntu)
--
x11vnc able to segfault xorg
https://bugs.launchpad.net/bugs/525066
You received this bug notification because you are a m
I've suffered this since upgrade to 10.10. But I can't find the crash
log on Xorg.0.log.old. Can anyone help to indicate where I can find some
useful log for this issue?
--
x11vnc able to segfault xorg
https://bugs.launchpad.net/bugs/525066
You received this bug notification because you are a mem
** Tags added: karmic
--
x11vnc able to segfault xorg
https://bugs.launchpad.net/bugs/525066
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
___
Mailing list: https:
14 matches
Mail list logo
