xrdb crashed with SIGSEGV in __libc_start_main()

Bug #645644 reported by Jason Ward
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Expired
Medium
Unassigned

Bug Description

????????

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: x11-xserver-utils 7.5+2ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 256.53 Fri Aug 27 20:27:48 PDT 2010
 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4)
Architecture: amd64
Date: Wed Sep 22 21:07:27 2010
DkmsStatus:
 virtualbox-ose, 3.2.8, 2.6.32-24-generic, x86_64: installed
 virtualbox-ose, 3.2.8, 2.6.35-22-generic, x86_64: installed
 nvidia-current, 256.53, 2.6.32-24-generic, x86_64: installed
 nvidia-current, 256.53, 2.6.35-22-generic, x86_64: installed
ExecutablePath: /usr/bin/xrdb
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
Lsusb:
 Bus 002 Device 002: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Compaq dx2450 Microtower PC
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=1a678485-90cb-4f46-921a-193644f33505 ro quiet splash
ProcCmdline: xrdb -merge /etc/X11/Xresources/x11-common
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x402983: mov 0x30(%rbx),%esi
 PC (0x00402983) ok
 source "0x30(%rbx)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nvidia-graphics-drivers
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: xrdb crashed with SIGSEGV in __libc_start_main()
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
Xrandr:
 Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension "RANDR" missing on display ":0.0".
 RandR extension missing
dmi.bios.date: 08/15/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.16
dmi.board.name: 2A72h
dmi.board.vendor: OEM_MB
dmi.board.version: 3.02
dmi.chassis.asset.tag: CZC8356NK9
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.16:bd08/15/2008:svnHewlett-Packard:pnHPCompaqdx2450MicrotowerPC:pvr:rvnOEM_MB:rn2A72h:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: HP Compaq dx2450 Microtower PC
dmi.sys.vendor: Hewlett-Packard
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

Revision history for this message
Jason Ward (jason-jasonward) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Process (scrno=0, doScreen=<value optimized out>,
 main (argc=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nvidia-graphics-drivers (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
bugbot (bugbot) wrote :

Hey Jason,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in nvidia-graphics-drivers (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.