Your message dated Mon, 2 May 2011 23:23:53 +0200
with message-id <20110502212353.gw2...@radis.liafa.jussieu.fr>
and subject line Re: Bug#624856: rxvt-unicode causes X to segfault
has caused the Debian Bug report #624856,
regarding rxvt-unicode causes X to segfault
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
624856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rxvt-unicode
Version: 9.10-2
Severity: grave
Justification: renders package unusable


After recently rebooting my machine, I could no longer log into XDM... it took a
while to track it down, but it was the rxvt-unicodes I was executing in
.xsession.

Anytime I launch an rxvt-unicode, I get the following segfault:

Backtrace:
[   587.865] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80edefb]
[   587.865] 1: /usr/bin/X (0x8048000+0x58915) [0x80a0915]
[   587.865] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb77a740c]
[   587.865] 3: /usr/bin/X (ProcessWorkQueue+0x30) [0x80980e0]
[   587.865] 4: /usr/bin/X (WaitForSomething+0x56) [0x80a7e26]
[   587.865] 5: /usr/bin/X (0x8048000+0x3ae0e) [0x8082e0e]
[   587.865] 6: /usr/bin/X (0x8048000+0x1e695) [0x8066695]
[   587.865] 7: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb74b4c76]
[   587.865] 8: /usr/bin/X (0x8048000+0x1e271) [0x8066271]
[   587.865] Segmentation fault at address 0x3845d9c
[   587.865] 
Fatal server error:
[   587.865] Caught signal 11 (Segmentation fault). Server aborting
[   587.865] 
[   587.865] 


Before I tracked it down to rxvt-unicode, I thought there might have been a bug
in the unstable release of nvidia, so I tried the experimental versions of
nvidia-kernel-source and nvidia-glx.

Once I narrowed it down to rxvt-unicode, I tried the experimental version of
rxvt-unicode, but that didn't fix it either.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.37-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages rxvt-unicode depends on:
ii  base-passwd                3.5.22        Debian base system master password
ii  libc6                      2.11.2-11     Embedded GNU C Library: Shared lib
ii  libfontconfig1             2.8.0-2.1     generic font configuration library
ii  libgcc1                    1:4.4.5-12    GCC support library
ii  libgdk-pixbuf2.0-0         2.22.1-1+sid1 GDK Pixbuf library
ii  libglib2.0-0               2.28.6-1      The GLib library of C routines
ii  libperl5.10                5.10.1-19     shared Perl library
ii  libx11-6                   2:1.4.3-1     X11 client-side library
ii  libxft2                    2.2.0-2       FreeType-based font drawing librar
ii  libxrender1                1:0.9.6-1     X Rendering Extension client libra
ii  ncurses-base               5.9-1         basic terminal type definitions

Versions of packages rxvt-unicode recommends:
ii  ttf-dejavu                    2.33-1     Metapackage to pull in ttf-dejavu-
pn  ttf-sazanami-gothic           <none>     (no description available)

rxvt-unicode suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On Mon, May  2, 2011 at 01:36:49 -0700, Phil Dibowitz wrote:

> After recently rebooting my machine, I could no longer log into XDM... it 
> took a
> while to track it down, but it was the rxvt-unicodes I was executing in
> .xsession.
> 
> Anytime I launch an rxvt-unicode, I get the following segfault:
> 
> Backtrace:
> [   587.865] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80edefb]
> [   587.865] 1: /usr/bin/X (0x8048000+0x58915) [0x80a0915]
> [   587.865] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb77a740c]
> [   587.865] 3: /usr/bin/X (ProcessWorkQueue+0x30) [0x80980e0]
> [   587.865] 4: /usr/bin/X (WaitForSomething+0x56) [0x80a7e26]
> [   587.865] 5: /usr/bin/X (0x8048000+0x3ae0e) [0x8082e0e]
> [   587.865] 6: /usr/bin/X (0x8048000+0x1e695) [0x8066695]
> [   587.865] 7: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb74b4c76]
> [   587.865] 8: /usr/bin/X (0x8048000+0x1e271) [0x8066271]
> [   587.865] Segmentation fault at address 0x3845d9c
> [   587.865] 
> Fatal server error:
> [   587.865] Caught signal 11 (Segmentation fault). Server aborting
> [   587.865] 
> [   587.865] 
> 
> 
> Before I tracked it down to rxvt-unicode, I thought there might have been a 
> bug
> in the unstable release of nvidia, so I tried the experimental versions of
> nvidia-kernel-source and nvidia-glx.
> 
> Once I narrowed it down to rxvt-unicode, I tried the experimental version of
> rxvt-unicode, but that didn't fix it either.
> 
An X crash is not a client bug.  I'm guessing you have an entry for a
font server in your xorg.conf, and this is a dupe of a known X bug.
Remove that entry and it'll stop crashing.

Cheers,
Julien


--- End Message ---

Reply via email to