Your message dated Tue, 18 Apr 2006 00:52:08 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363083: Check for duplicate
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: nvidia-glx
Version: 1.0.8756-4
Severity: grave
Justification: renders package unusable

After upgrading my kernel, X11 and the nvidia drivers, I can start X with the nv
driver but the nvidia driver causes X to segfault with the following backtrace:

(II) NVIDIA(0): Setting mode "1280x1024"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: X(xf86SigHandler+0x95) [0x4772c5]
1: /lib/libc.so.6 [0x2b2bd5064e90]
2: X(xf86nameCompare+0x9c) [0x49b26c]
3: X(InitInput+0x11e) [0x45ecfe]
4: X(main+0x3c4) [0x430604]
5: /lib/libc.so.6(__libc_start_main+0xda) [0x2b2bd50514ca]
6: X(FontFileCompleteXLFD+0x9a) [0x42fbea]

Fatal server error:
Caught signal 11.  Server aborting

---

Any ideas what may be causing this?

-- Package-specific info:
uname -r:
Linux matta 2.6.16-1-em64t-p4-smp #2 SMP Sun Apr 16 02:26:13 UTC 2006 x86_64 
GNU/Linux


/proc/version:
Linux version 2.6.16-1-em64t-p4-smp (Debian 2.6.16-7) ([EMAIL PROTECTED]) (gcc 
version 4.0.3 (Debian 4.0.3-1)) #2 SMP Sun Apr 16 02:26:13 UTC 2006


/proc/driver/nvidia/version:


0000:01:00.0 VGA compatible controller: nVidia Corporation NV41GL [Quadro FX 
1400] (rev a2)


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-em64t-p4-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages nvidia-glx depends on:
ii  libc6                2.3.6-7             GNU C Library: Shared libraries
ii  nvidia-kernel-2.6.16 1.0.8756-4+2.6.16-7 NVIDIA binary kernel module for Li
ii  x11-common           1:7.0.12            X Window System (X.Org) infrastruc

nvidia-glx recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi Filipus,

Filipus Klutiero wrote:
Hi, could you please check this against #340066.

This does not seem to be related to that bug.

However, I noticed that there were remains of an old upstream nvidia driver installation. When I removed it and the nvidia-glx/kernel packages, reinstalled nvidia-glx/kernel and started X with the nvidia driver, everything worked as normal again. Why the upgrade caused it to fail I don't know, but the problem seems to have been the upstream installation messing things up.

As such, I'm closing this bug as it's invalid.

Regards,

--
Mattias Nordstrom

--- End Message ---

Reply via email to