X.org 1.9 crashes with Segmentation fault at address 0x1b
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
Ubuntu 10.10
After running Ubuntu 10.10 some time and browsing with chromium-browser the X.org-Server crashes with Segmentation fault at address 0x1b.
chromium-browser:
Chromium 7.0.517.41 (Entwickler-Build 62167) Ubuntu 10.10
WebKit 534.7
V8 2.3.11.17
User-Agent Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Ubuntu/10.10 Chromium/7.0.517.41 Chrome/7.0.517.41 Safari/534.7
Befehlszeile /usr/lib/
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg (not installed)
ProcVersionSign
Uname: Linux 2.6.35-23-generic i686
NonfreeKernelMo
.proc.driver.
Fast Writes: Supported
SBA: Supported
AGP Rates: 8x 4x
Registers: 0x1f000e1b:
.proc.driver.
Host Bridge: PCI device 1106:3189
Fast Writes: Not Supported
SBA: Supported
AGP Rates: 8x 4x
Registers: 0x1f000a0b:
.proc.driver.
Status: Enabled
Driver: NVIDIA
AGP Rate: 8x
Fast Writes: Disabled
SBA: Enabled
.proc.driver.
NVRM version: NVIDIA UNIX x86 Kernel Module 173.14.28 Wed Sep 29 09:47:25 PDT 2010
GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: i386
Date: Thu Oct 28 07:49:54 2010
DkmsStatus: nvidia-173, 173.14.28, 2.6.35-23-generic, i686: installed
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 04/08/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: K7Upgrade-600
dmi.board.version: 1.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K7Upgrade-600
dmi.product.
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-23-generic
tags: | added: kubuntu |
affects: | xorg (Ubuntu) → xorg-server (Ubuntu) |
Hey Sven,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect <bug-number>
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)