Bug#551166: xserver-xorg-video-intel: X not starting - driver linked against libpthread-stubs.so.0 and it should be libpthread.so.0
Package: xserver-xorg-video-intel Version: 2:2.9.0-1 Severity: critical Justification: breaks unrelated software Hello, Having upgraded Debian (sid), X was not starting. The Intel driver complained about a missing library (libpthread-stubs.so.0) I have solved it provisionally by: # ln -s /lib/libpthread.so.0 /lib/libpthread-stubs.so.0 and X works well, but I guess that driver should be linked against libpthread.so.0... or perhaps I'm in a transition of changes to libpthread? Regards, Josep -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Mar 13 2008 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1689944 Oct 13 13:31 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1670 Mar 13 2008 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "es" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "Intel Corporation 82945G/GZ Integrated Graphics Controller" Driver "intel" BusID "PCI:0:2:0" EndSection Section "Monitor" Identifier "HP L1706" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Intel Corporation 82945G/GZ Integrated Graphics Controller" Monitor "HP L1706" DefaultDepth24 SubSection "Display" Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 27419 Apr 28 17:13 /var/log/Xorg.20.log -rw-r--r-- 1 root root 39232 Oct 16 10:42 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30.8-dsa-ia32 i686 Debian Current Operating System: Linux e214-ioc 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 i686 Build Date: 13 October 2009 11:25:51AM xorg-server 2:1.6.5-1 (bui...@murphy.debian.org) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 16 09:36:46 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "HP L1706" (**) | |-->Device "Intel Corporation 82945G/GZ Integrated Graphics Controller" (**) |-->Input Device "Generic Keyboard" (**) |--&g
Bug#494172: searching a workaround
I have downloaded the Debian Mesa sources to try to compile Mesa and OSMesa like the standard Mesa package. I see that the Mesa make command show me some configurations like the standard package linux-* but som that not are in the standard debian-*. Now looking in the debian/rules I found debian-* configurations, I changed it for linux-* but compilation process fails. Any idea? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#494172: libosmesa6: libOSMesa / libGl symbol collision
Package: libosmesa6 Version: 7.1~rc3-1 Severity: normal -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libosmesa6 depends on: ii libc6 2.7-13 GNU C Library: Shared libraries libosmesa6 recommends no packages. libosmesa6 suggests no packages. -- no debconf information I'm integrating osmesa with an application that use Qt/OpenGl to do Off Screen rendering. But there is somthing that fails. First something strange happends in the link proces. The linking proces is: g++ -o qgreco release/com.o release/crono.o release/dbas.o release/dbasv2.o release/error.o release/fam.o release/full_rt_rcs.o release/gid.o release/grabar.o release/grecoPost.o release/ideas.o release/iges.o release/image.o release/init.o release/input.o release/mialloc.o release/neutral.o release/octree.o release/oiges.o release/param.o release/po_rcs.o release/ptd_rcs.o release/qt_win.o release/rcs.o release/reflexiones.o release/rt_rcs.o release/teselar.o release/vertex_arrays.o release/xogdibuj.o release/glwidget.o release/glwindow.o release/logowidget.o release/twindow.o release/gwindow.o release/initrcs.o release/memoryrc.o release/moc_glwidget.o release/moc_glwindow.o release/moc_logowidget.o release/moc_twindow.o release/moc_gwindow.o release/moc_initrcs.o-L/usr/X11R6/lib -L/usr/lib -lOSMesa -lXext -lX11 -lm -lQtXml -lQtOpenGL -lQtGui -lQtCore -lQtUiTools -lGLU -lGL -lpthread The important part are the linked libraries, first I noticied that depending on the order of the libraries the program fails with segmentation fault (linking GL after OSMesa ) or drawing bad images (linking OSMesa after GL). Then I found that if I link with the Mesa Libraries compiled from the original sources my program run well. The difference I noticied: Using: nm -D /usr/lib/libOSMesa.so (from Debian Packages) Returns a lot of symbols included gl* And ldd. linux-vdso.so.1 => (0x7fff1e7fe000) libm.so.6 => /lib/libm.so.6 (0x7fad15f38000) libpthread.so.0 => /lib/libpthread.so.0 (0x7fad15d1c000) libc.so.6 => /lib/libc.so.6 (0x7fad159c8000) /lib64/ld-linux-x86-64.so.2 (0x7fad1664) nm -D mycompiledlibOSMesa.so (compiled from sources) Returns only some symbols without gl* And ldd. linux-vdso.so.1 => (0x7fff467fe000) ->libGL.so.1 => /usr/lib/libGL.so.1 (0x7f6a3e297000) libc.so.6 => /lib/libc.so.6 (0x7f6a3df44000) libX11.so.6 => /usr/lib/libX11.so.6 (0x7f6a3dc37000) libXext.so.6 => /usr/lib/libXext.so.6 (0x7f6a3da26000) libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x7f6a3d821000) libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x7f6a3d61e000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x7f6a3d519000) libdrm.so.2 => /usr/lib/libdrm.so.2 (0x7f6a3d31) libm.so.6 => /lib/libm.so.6 (0x7f6a3d08c000) libpthread.so.0 => /lib/libpthread.so.0 (0x7f6a3ce7) libdl.so.2 => /lib/libdl.so.2 (0x7f6a3cc6c000) /lib64/ld-linux-x86-64.so.2 (0x7f6a3e742000) libxcb-xlib.so.0 => /usr/lib/libxcb-xlib.so.0 (0x7f6a3ca6a000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0x7f6a3c84e000) libXau.so.6 => /usr/lib/libXau.so.6 (0x7f6a3c64c000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x7f6a3c446000) I think that libOSMesa.so have compiled in the same libgl code and then there are symbols colision. Can you make the libOSMesa package didn't link libGL static? Otherwise, can you explain myself how to build the package from Debian sources but linking GL libraries dynamically? There ara any other workarrounds to prevent this? Thanks, Josep -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
