Compiled xvfb (2:1.6.0-0ubuntu14) from deb sources but with debugging
enabled and no stripping..
a...@durum:~/xvfb$ diff rules xorg-server-1.6.0/debian/rules
16c16
CFLAGS += -O0
---
CFLAGS += -O2
181c181
# dh_strip -s --dbg-package=xserver-xorg-core
---
dh_strip -s
valgrind output shows that the immediate problem is that xrealloc in
glx/glxscreen.c:276 causes some colormaps to have a bad pVisual member..
That is : some colormaps STILL point to the old memory .. In other
words.. not all colormaps gets fixed up in AddScreenVisuals. Here is a
gdb session where
The problem still exists and has been reported by others..
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529927
** Bug watch added: Debian Bug tracker #529927
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529927
--
Xvfb crashes with SIGSEGV in FreeColormap()
*** This bug is a duplicate of bug 371191 ***
https://bugs.launchpad.net/bugs/371191
** This bug has been marked a duplicate of bug 371191
Corrupted file system ext3 after Jaunty 64 upgrade
--
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You
Bug #360952 mentioned HPET (in fact I was the only one to comment on
it). In any case.. The problem persists even after messing with HPET. So
this did not solve it.
However, manually installing Linux kernel 2.6.29.3 from source DID solve
the problem (or at least the symptoms).
Seems like a
I am under the assumption that this problem is related to the HPET issues
others are experiencing. With HPET (enabled
by default), the system becomes unstable over time.. Installed Jaunty again and
tried two kernels: one with HPET enabled and one with HPET disabled. So far,
the system, with
Public bug reported:
System is Ubuntu Jaunty amd64. Hardware is Lenovo T61, type 6460-D6G.
System becomes unstable within minutes or a few hours of operation (uptime) and
we see crashes in many
places.. Mostly in apt-get (SEGVs), due to that being used heavily the first
few hours of operation.
dmesg from second laptop.. during 3rd install. Interestingly this laptop was
running for much longer time than
the other one before it the file system was forced read-only.
** Attachment added: dmesg
http://launchpadlibrarian.net/25375608/dmesg.from.gyros
--
Unstable system, EXT3 FS errors
** Attachment added: Hardware details
http://launchpadlibrarian.net/25375526/lshw.txt
--
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
dmesg from first laptop .. during second install.. The dmesg was copied away
from the laptop via ssh because
the FS was forced into read-only mode. After rebooting Grub Error 2 was shown.
** Attachment added: dmesg
http://launchpadlibrarian.net/25375598/dmesg.from.curry
--
Unstable system,
xserver configuration
** Attachment added: /etc/X11/xort.conf
http://launchpadlibrarian.net/24163269/xorg.conf
--
Xvfb crashes with SIGSEGV
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Program received signal SIGSEGV, Segmentation fault.
---Type return to continue, or q return to quit---
[Switching to Thread 0x7facb72e46f0 (LWP 7931)]
0x00507665 in FreeColormap ()
(gdb) bt full
#0 0x00507665 in FreeColormap ()
No symbol table info available.
#1
Public bug reported:
Binary package hint: xvfb
a...@durum:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION=Ubuntu 8.10
a...@durum:~$ apt-cache policy xvfb
xvfb:
Installed: 2:1.5.2-2ubuntu3
Candidate: 2:1.5.2-2ubuntu3
Version
If I specify a screen the crash does not occur.
Xvfb :1 -auth hosts -screen 0 800x600x24
--
Xvfb crashes with SIGSEGV
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
14 matches
Mail list logo
