[Ubuntu-x-swat] [Bug 1909877] [NEW] Clock in top bar doesn't update
Public bug reported: When exiting fullscreen from chromium (YouTube), the clock widget in the top bar seems stuck and only updates after being updated from the mouse hovering over it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 2 21:56:27 2021 DistUpgraded: 2020-12-27 18:29:34,023 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-58-generic, x86_64: installed nvidia, 455.45.01, 5.8.0-33-generic, x86_64: installed virtualbox, 6.1.14, 5.4.0-58-generic, x86_64: installed virtualbox, 6.1.14, 5.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1265] InstallationDate: Installed on 2020-12-11 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=8753fbc2-cbcd-41b4-ad44-9e1a6f940ddf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-12-27 (6 days ago) dmi.bios.date: 08/05/2019 dmi.bios.release: 1.28 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:br1.28:efr1.26:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909877 Title: Clock in top bar doesn't update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1909877/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855570] Re: xdg-desktop-por: Could not get window list: Timeout was reached
** Attachment added: "Ubuntu 20.04 Xorg 0 log by FvB" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+attachment/5310649/+files/Xorg.0.log ** Description changed: - Just installed Ubuntu 20.04 (for testing purpose only): While booting - there is no Gnome showing up. Checking syslog there are these messages - ... + Just freshly installed Ubuntu 20.04 on a bare metal Desktop (for testing + purpose only): While booting there is no Gnome showing up. Checking + syslog there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Description changed: - Just freshly installed Ubuntu 20.04 on a bare metal Desktop (for testing - purpose only): While booting there is no Gnome showing up. Checking - syslog there are these messages ... + Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk + partition (for testing purpose only): While booting there is no Gnome + showing up. Checking syslog there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Description changed: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome - showing up. Checking syslog there are these messages ... + showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed
[Ubuntu-x-swat] [Bug 1855570] Re: xdg-desktop-por: Could not get window list: Timeout was reached
** Attachment added: "Ubuntu 20.04 gpu-manager by FvB" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+attachment/5310648/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: xdg-desktop-por: Could not get window list: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855570] [NEW] xdg-desktop-por: Could not get window list: Timeout was reached
Public bug reported: Just freshly installed Ubuntu 20.04 on a bare metal Desktop disk partition (for testing purpose only): While booting there is no Gnome showing up. Checking syslog for error's there are these messages ... Dec 8 07:51:43 deblnxsrv100 xdg-desktop-por[1287]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: Timeout was reached Dec 8 07:51:43 deblnxsrv100 at-spi-bus-launcher[1245]: X connection to :0 broken (explicit kill or server shutdown). Dec 8 07:51:44 deblnxsrv100 gsd-wacom[1522]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 gsd-xsettings[1538]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Failed with result 'exit-code'. Dec 8 07:51:44 deblnxsrv100 systemd[]: gsd-xsettings.service: Triggering OnFailure= dependencies. Dec 8 07:51:44 deblnxsrv100 systemd[]: Stopped target GNOME XSettings. Dec 8 07:51:44 deblnxsrv100 systemd[]: Started GNOME Session Failed lockdown screen (user). Dec 8 07:51:44 deblnxsrv100 systemd[]: Reached target GNOME Session Failed. Dec 8 07:51:44 deblnxsrv100 update-notifier[1815]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Ubuntu 20.04 syslog by FvB" https://bugs.launchpad.net/bugs/1855570/+attachment/5310647/+files/syslog -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1855570 Title: xdg-desktop-por: Could not get window list: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855570/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1796447] [NEW] package libgles1 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340
Public bug reported: E: /tmp/apt-dpkg-install-mc273t/57-libgles1_1.0.0-2ubuntu2.2_amd64.deb: poging tot overschrijven van '/usr/lib/x86_64-linux- gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44 nvidia ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libgles1:amd64: Install libglvnd-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Oct 6 05:48:39 2018 DpkgTerminalLog: Uitpakken van .../libgles1_1.0.0-2ubuntu2.2_amd64.deb wordt voorbereid... Bezig met uitpakken van libgles1:amd64 (1.0.0-2ubuntu2.2) ... [1mdpkg:[0m fout bij verwerken van archief /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit ErrorMessage: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit InstallationDate: Installed on 2014-09-03 (1493 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit UpgradeStatus: Upgraded to bionic on 2018-09-16 (19 days ago) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1796447 Title: package libgles1 (not installed) failed to install/upgrade: poging tot overschrijven van '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', wat ook in pakket nvidia-340 340.106-0ubuntu3 zit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1796447/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 861268] Re: text corruption in terminals (xterm, urxvt) and emacs
Just some additional info that might help narrowing down the cause. I see this same effect on a machine running Arch Linux. On this machine I use urxvt on top of the i3 window manager. (So not Gnome, KDE or Unity). It happens when text gets scrolled in the terminal window. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/861268 Title: text corruption in terminals (xterm, urxvt) and emacs To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/861268/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1181651] Re: ldconfig problem with 64-bit nvidia driver packages
** Description changed: - On Ubuntu 13.04 64-bit, this package as well as others (including - nvidia-current and nvidia-current-updates from the main ubuntu package + On Ubuntu 13.04 64-bit, nvidia-319 as well as others (including nvidia- + current and nvidia-current-updates from the main ubuntu package repositories) don't play nice with applications that use 32-bit OpenGL libraries. When such an application tries to load the nvidia 32-bit libGL.so library, they don't load the nvidia libGL.so but some other non-nvidia libGL.so. This means a 32-bit application running on Ubuntu Raring 64-bit will never use the nvidia libGL.so library. After a lot of monkey business, I figured out what the problem is. Which libGL.so a 32-bit application uses on a 64-bit system is controlled by the file /etc/ld.so.conf.d/i386-linux-gnu_GL.conf which is just a symlink to /etc/alternatives/i386-linux-gnu_gl_conf which is another symlink to /usr/lib/nvidia-319/alt_ld.so.conf or something similar for other versions of the nvidia drivers. This file is blank in a clean install, so ldconfig doesn't know that 32-bit applications asking for libGL.so should get linked with the version in /usr/lib32/nvidia-319, so it links them with some other version. This breaks 32-bit programs like Steam (which throws a warning about not using direct rendering when it starts up) and 32-bit games like Team Fortress 2 (which fails to start altogether). Of course, this isn't specific to Steam and Team Fortress 2 but will affect any 32-bit program trying to use libGL.so and its associated libraries on a 64-bit machine. fortunately, the fix for this is pretty simple: in the file /usr/lib/nvidia-319/alt_ld.so.conf in the nvidia-319 package add the lines: /usr/lib32/nvidia-319 /usr/lib/nvidia-319 This will tell ldconfig to use the nvidia libGL.so and associated libraries for 32-bit applications. For the other versions of the nvidia driver (such as nvidia-304 and nvidia-304-updates in the main ubuntu repositories) it's a simple matter of replacing nvidia-319 with nvidia-304, nvidia-304-updates, nvidia-313, etc. in the directory names. Although I reported this bug for the nvidia-319 package, I have checked and this bug applies at least to the nvidia-304 and nvidia-304-updates packages for Ubuntu 13.04 amd64 in the main ubuntu package repositories as well. It probably also applies to other nvidia driver packages as well, but I haven't checked those. I suppose all you'd have to look for is a blank /usr/lib//alt_ld.so.conf file to check for the bug. The file I've included is the output of ldd (which prints the dynamic library dependencies of a program) when it's used on a 32-bit program that needs the 32-bit libGL.so on an Ubuntu 13.04 64-bit machine. In this case, the program I used ldd on is the 32-bit version of glxinfo from mesa-utils:i386. The nvidia driver version I had installed when I did this is nvidia-319. However, you will get a very similar result for other nvidia driver versions/packages. Also, I said "I don't know" for the package because 1.) it affects multiple packages and 2.) it didn't accept the package name nvidia-319. ** Description changed: - On Ubuntu 13.04 64-bit, nvidia-319 as well as others (including nvidia- - current and nvidia-current-updates from the main ubuntu package - repositories) don't play nice with applications that use 32-bit OpenGL - libraries. When such an application tries to load the nvidia 32-bit - libGL.so library, they don't load the nvidia libGL.so but some other - non-nvidia libGL.so. This means a 32-bit application running on Ubuntu - Raring 64-bit will never use the nvidia libGL.so library. + On Ubuntu 13.04 64-bit, the nvidia-319 package as well as others + (including nvidia-current and nvidia-current-updates from the main + ubuntu package repositories) don't play nice with applications that use + 32-bit OpenGL libraries. When such an application tries to load the + nvidia 32-bit libGL.so library, they don't load the nvidia libGL.so but + some other non-nvidia libGL.so. This means a 32-bit application running + on Ubuntu Raring 64-bit will never use the nvidia libGL.so library. After a lot of monkey business, I figured out what the problem is. Which libGL.so a 32-bit application uses on a 64-bit system is controlled by the file /etc/ld.so.conf.d/i386-linux-gnu_GL.conf which is just a symlink to /etc/alternatives/i386-linux-gnu_gl_conf which is another symlink to /usr/lib/nvidia-319/alt_ld.so.conf or something similar for other versions of the nvidia drivers. This file is blank in a clean install, so ldconfig doesn't know that 32-bit applications asking for libGL.so should get linked with the version in /usr/lib32/nvidia-319, so it links them with some other version. This breaks 32-bit programs like Steam (which throws a warning about not using direct rendering when it starts u
[Ubuntu-x-swat] [Bug 1181651] [NEW] ldconfig problem with 64-bit nvidia driver packages
Public bug reported: On Ubuntu 13.04 64-bit, this package as well as others (including nvidia-current and nvidia-current-updates from the main ubuntu package repositories) don't play nice with applications that use 32-bit OpenGL libraries. When such an application tries to load the nvidia 32-bit libGL.so library, they don't load the nvidia libGL.so but some other non-nvidia libGL.so. This means a 32-bit application running on Ubuntu Raring 64-bit will never use the nvidia libGL.so library. After a lot of monkey business, I figured out what the problem is. Which libGL.so a 32-bit application uses on a 64-bit system is controlled by the file /etc/ld.so.conf.d/i386-linux-gnu_GL.conf which is just a symlink to /etc/alternatives/i386-linux-gnu_gl_conf which is another symlink to /usr/lib/nvidia-319/alt_ld.so.conf or something similar for other versions of the nvidia drivers. This file is blank in a clean install, so ldconfig doesn't know that 32-bit applications asking for libGL.so should get linked with the version in /usr/lib32/nvidia-319, so it links them with some other version. This breaks 32-bit programs like Steam (which throws a warning about not using direct rendering when it starts up) and 32-bit games like Team Fortress 2 (which fails to start altogether). Of course, this isn't specific to Steam and Team Fortress 2 but will affect any 32-bit program trying to use libGL.so and its associated libraries on a 64-bit machine. fortunately, the fix for this is pretty simple: in the file /usr/lib/nvidia-319/alt_ld.so.conf in the nvidia-319 package add the lines: /usr/lib32/nvidia-319 /usr/lib/nvidia-319 This will tell ldconfig to use the nvidia libGL.so and associated libraries for 32-bit applications. For the other versions of the nvidia driver (such as nvidia-304 and nvidia-304-updates in the main ubuntu repositories) it's a simple matter of replacing nvidia-319 with nvidia-304, nvidia-304-updates, nvidia-313, etc. in the directory names. Although I reported this bug for the nvidia-319 package, I have checked and this bug applies at least to the nvidia-304 and nvidia-304-updates packages for Ubuntu 13.04 amd64 in the main ubuntu package repositories as well. It probably also applies to other nvidia driver packages as well, but I haven't checked those. I suppose all you'd have to look for is a blank /usr/lib//alt_ld.so.conf file to check for the bug. The file I've included is the output of ldd (which prints the dynamic library dependencies of a program) when it's used on a 32-bit program that needs the 32-bit libGL.so on an Ubuntu 13.04 64-bit machine. In this case, the program I used ldd on is the 32-bit version of glxinfo from mesa-utils:i386. The nvidia driver version I had installed when I did this is nvidia-319. However, you will get a very similar result for other nvidia driver versions/packages. Also, I said "I don't know" for the package because 1.) it affects multiple packages and 2.) it didn't accept the package name nvidia-319. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: xorg-edgers -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1181651 Title: ldconfig problem with 64-bit nvidia driver packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1181651/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 921139] Re: mouse scroll left<->right inverted since 1.11
Upstream bug #45614 is a duplicate of upstream bug #46205. Launchpad is
showing the status of 45614 ('invalid' as it's a duplicate) rather than
that of 46205 ('New'). This is misleading as the bug /is/ valid, so I'm
manually updating the reference to upstream and will report a bug
against launchpad.
** Bug watch added: freedesktop.org Bugzilla #46205
https://bugs.freedesktop.org/show_bug.cgi?id=46205
** Changed in: xorg-server
Importance: Medium => Unknown
** Changed in: xorg-server
Status: Invalid => Unknown
** Changed in: xorg-server
Remote watch: freedesktop.org Bugzilla #45614 => freedesktop.org Bugzilla
#46205
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/921139
Title:
mouse scroll left<->right inverted since 1.11
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/921139/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 928313] Re: Horizontal scrolling inverted for Microsoft Intellimouse Explorer for Bluetooth
*** This bug is a duplicate of bug 921139 *** https://bugs.launchpad.net/bugs/921139 ** This bug has been marked a duplicate of bug 921139 mouse scroll left<->right inverted since 1.11 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/928313 Title: Horizontal scrolling inverted for Microsoft Intellimouse Explorer for Bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/928313/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 928313] Re: Horizontal scrolling inverted for Microsoft Intellimouse Explorer for Bluetooth
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-mouse in Ubuntu. https://bugs.launchpad.net/bugs/928313 Title: Horizontal scrolling inverted for Microsoft Intellimouse Explorer for Bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-mouse/+bug/928313/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 928313] [NEW] Horizontal scrolling inverted for Microsoft Intellimouse Explorer for Bluetooth
Public bug reported: Horizontal scrolling by tilting the mouse wheel is backwards for Microsoft Intellimouse Explorer for Bluetooth. xev reports tilt left as button 7 and tilt right as button 6, but tilting left scrolls right and tilting right scrolls left. This used to work correctly on oneiric. I'm using Kubuntu, in case it's possible that something in KDE might cause this ;-) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-mouse 1:1.7.1-1build3 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic-pae 3.2.3 Uname: Linux 3.2.0-14-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Tue Feb 7 15:32:40 2012 ProcEnviron: LANGUAGE=en_GB PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-input-mouse UpgradeStatus: Upgraded to precise on 2011-12-09 (60 days ago) ** Affects: xserver-xorg-input-mouse (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-mouse in Ubuntu. https://bugs.launchpad.net/bugs/928313 Title: Horizontal scrolling inverted for Microsoft Intellimouse Explorer for Bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-mouse/+bug/928313/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 803992] Re: Natty update introduced crasher in xorg
I've just been told on irc that my responses above are are only partially or not applicable here. The original bug is on gnome3; my problem and fix was with gnome 2.32 apologies for any confusion. Frans -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/803992 Title: Natty update introduced crasher in xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/803992/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 803992] Re: Natty update introduced crasher in xorg
no source code analysis. Otherwise I would have probably come up with a fix. At some point I suspected that my session type was wrong, but since I used autologon I could not change it to test it. Therefore I turned autologon off and noticed that things started to work. Sometimes it is just that simple. BTW I still sometimes get "Oh no something has gone wrong"; although ubuntu does not have auto logon, gnome still has this. If I get that clicking on logout will give me the gnome login screen again, it will still autologin and then things go ok. I suspect this is a startup timing related issue, probalby between gnome and X11. If it matters, I have an i7-2600 with a hard disk (no ssd). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/803992 Title: Natty update introduced crasher in xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/803992/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 803992] Re: Natty update introduced crasher in xorg
I had the very same problem (CRITICAL: gdm_session_direct_get_username: assertion `session != NULL' failed) in syslog, startx works), only the line number in the message was different. I found that my problem was caused by using autologin. As a workaround I went to administration/user accounts and put the autologin off for my account After that a reboot brought be to the gdm sesssion selection screen. Now I can specify the session to start and gnome classic does work for me (didn't try the others). You might get a message the first reboot that gnome failed or so. Note that my gnome login screen is still on autologin; it is just uer accounts/autologin that I turned off. (btw turning it on again made the problem reappear, I hoped that after setting a proper session things would work, but to no avail; guess it has to be kept off for now). Hope this helps for you guys too. Frans -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/803992 Title: Natty update introduced crasher in xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/803992/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 256021] Re: glxinfo crashed with SIGSEGV in __libc_start_main()
Why did you have the nvidia drivers installed, then? Barring a bug in jockey, these drivers should not have been automatically installed for you. Steve, this is explained by my apt logs, which indicate that this affects people upgrading from karmic to lucid who have libmyth installed. The latest package versions and dependencies should have removed this problem. Here's where I get the nvidia driver: /var/log/dist-upgrade/apt.log: Installing nvidia-current as Depends of nvidia-185-libvdpau These are from karmic /var/log/dist-upgrade/20091031-0847/apt.log:Installing nvidia-185-libvdpau as dep of libmyth-0.22-0 /var/log/dist-upgrade/20091031-0933/apt.log:Installing nvidia-185-libvdpau as dep of libmyth-0.22-0 This is from karmic-lucid upgrade. /var/log/dist-upgrade/20100319-0647/apt.log:Installing nvidia-185-libvdpau as dep of libmyth-0.22-0 Currently libmyth is at 0.3-2 and depends on libvdpau1-0.3-2 which replaces nvidia-185-libvdpau, so this shouldn't cause further problems. -- glxinfo crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/256021 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 256021] Re: glxinfo crashed with SIGSEGV in __libc_start_main()
This doesn't affect me if I remove the NVidia drivers (I use Intel graphics, so I don't need them.) -- glxinfo crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/256021 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 256021] Re: glxinfo crashed with SIGSEGV in __libc_start_main()
I seem to have encountered this in Lucid beta 1. Is it supposed to be fixed for Lucid? -- glxinfo crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/256021 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
