mesa dbg packages still have CRC mismatch in lucid

Bug #584477 reported by Dimitri John Ledkov on 2010-05-23
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)

Bug Description

I am not sure if this bug is reported. I've reinstalled lucid from scratch & updated it.

Here is how to reproduce this:

$ glxinfo
name of display: :0.0
Segmentation fault
dmitrij@surgut:~$ gdb glxinfo
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
Reading symbols from /usr/bin/glxinfo...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/glxinfo
warning: the debug information found in "/usr/lib/debug//usr/lib/mesa/" does not match "/usr/lib/mesa/" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/lib/mesa/" does not match "/usr/lib/mesa/" (CRC mismatch).

[Thread debugging using libthread_db enabled]
name of display: :0.0

Program received signal SIGSEGV, Segmentation fault.
0x004ebf83 in i915_state_draw_region () from /usr/lib/dri/
(gdb) ^CQuit
(gdb) quit
A debugging session is active.

 Inferior 1 [process 3903] will be killed.

Quit anyway? (y or n) y

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mesa-utils 7.7.1-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sun May 23 08:58:39 2010
DkmsStatus: Error: [Errno 2] No such file or directory
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Apple Computer, Inc. MacBook1,1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=df5dc3b0-35d1-4af5-b306-f6bf209cf755 ro quiet splash
 PATH=(custom, user)
SourcePackage: mesa 10/12/06
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MB11.88Z.0061.B03.0610121324
dmi.board.asset.tag: Base Board Asset Tag Mac-F4208CC8
dmi.board.vendor: Apple Computer, Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.version: Mac-F4208CC8
dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMB11.88Z.0061.B03.0610121324:bd10/12/06:svnAppleComputer,Inc.:pnMacBook1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208CC8:rvrPVT:cvnAppleComputer,Inc.:ct10:cvrMac-F4208CC8: MacBook1,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.
glxinfo: Error: command ['glxinfo'] failed with exit code -11:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-22-generic

Dimitri John Ledkov (xnox) wrote :
Bryce Harrington (bryce) on 2010-05-23
Changed in mesa (Ubuntu):
status: New → Confirmed
summary: - glxinfo is messed up
+ mesa dbg packages are still have CRC mismatch in lucid
summary: - mesa dbg packages are still have CRC mismatch in lucid
+ mesa dbg packages still have CRC mismatch in lucid
Tormod Volden (tormodvolden) wrote :

Thanks for your report. This is a known issue, the underlying issue in bug #566602 was fixed and it will be solved next time the mesa packages are rebuilt. However this will probably only happen next time there is an important update. I am currently working on an SRU'able patch for a mesa bug so hopefully this will happen soon.

For now, you can fix the CRC like this:

sudo objcopy -R .gnu_debuglink --add-gnu-debuglink=/usr/lib/debug/usr/lib/mesa/ /usr/lib/mesa/

sudo objcopy -R .gnu_debuglink --add-gnu-debuglink=/usr/lib/debug/usr/lib/dri/ /usr/lib/dri/


Dimitri John Ledkov (xnox) wrote :

well, because we do not keep debug symbols for all package releases.... it will be sometimes have a scew. Which is a blueprint type of work aimed to be fixed sometime.

Changed in mesa (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers