[Ubuntu-x-swat] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
I also see it on Ubuntu MATE Jammy. Will the fix come from Xorg, or should we add LightDM to the affected projects list? -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 206924] Re: Make it possible to create a guest account
** No longer affects: ltsp -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/206924 Title: Make it possible to create a guest account To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/206924/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
Hi Timo, if I remember correctly, there were some schools that were affected by this issue, but I wasn't able to reproduce it in the office due to lack of similar hardware. Unfortunately it's not easy to check which were those schools; but I can keep an eye on this issue, in case I hear about black screens in the near future -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment #12 above; and unfortunately I don't have an affected school nearby, where I could test 18.2.8 in cosmic, and installing cosmic in a remote school would be hard. Thanks a lot Timo! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]
Just correcting a wrong comment (#2) I made: > It happens on both 32bit and 64bit installations. I asked the school that reported the issue on 64bit to check again, and they said they have a 32bit installation after all. So the problem has only been reported in 32bit installations; I don't know if it happened on 64bit. And btw everything is fixed now, thanks again to all. :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]
I don't know the software stacks involved: If I understood it correctly, mesa 18.3.3 doesn't work with older kernels while 18.0 did work, and so I'll do a bisection to see which kernel commit fixes the issue, and then distro kernel maintainers may cherrypick it for older kernels. If there's no need for mesa to work with older kernels without the cherrypicked commit, then I guess yes, this issue should be closed, in which case please close it for me or tell me to close it. Thanks again! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]
I tried a small kernel bisection using the ubuntu kernel binaries, 4.19.2-041902=fails, 4.19.3-041903=works -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]
Hello Sergii, I tried with 4.20.7 and it appears to work fine! Thanks! Output of the commands: # uname -a Linux srv-6gym-chalk 4.20.7-042007-generic #201902061234 SMP Wed Feb 6 17:49:39 UTC 2019 i686 i686 i686 GNU/Linux # file /usr/bin/glxinfo /usr/bin/glxinfo: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=6cef7eab38835376734bdc80c5ab1ee786a6157a, stripped # glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) x86/MMX/SSE2 (0x1912) Version: 18.3.3 Accelerated: yes Video memory: 1536MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) x86/MMX/SSE2 OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.3 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 18.3.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.3 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]
I just tried with 4.18.0-14-generic, the same issue happens there as well. And, another school reported the issue on HD Graphics 630: root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] Kernel driver in use: i915 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
I verify that the bionic-proposed package addresses the issue. Tested in: # lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000] Kernel driver in use: i915 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172] [NEW] Black screen on skylake after 18.0 => 18.2 update
Public bug reported: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument ** Affects: mesa Importance: Unknown Status: Unknown ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: mesa (Ubuntu Cosmic) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Bug watch added: freedesktop.org Bugzilla #109583 https://bugs.freedesktop.org/show_bug.cgi?id=109583 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=109583 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1584314] Re: Togo keyboard layout / compose keys
Hi Gunnar, the issue was that in some cases, typing the Greek key for accent (tonos, the key is ";"), and then after releasing it, typing "α", resulted in two separate characters, i.e. ;+α=´α instead of the correct ;+α=ά At first I thought this was because of ibus, because I was seeing the issue only on setups where ibus was installed. But later on I realized that something, maybe /usr/bin/gnome-language-selector, but possibly something else too, was creating a ~/.xinputrc file: # im-config(8) generated on Wed, 25 May 2016 07:25:38 +0300 run_im xim # im-config signature: 5f2367a738e8f9717ddbb719455f7930 - So when that file was present, even when ibus was not installed, I was still having the tonos issue. After running `rm ~/.xinputrc` and logging in again, the issue was gone. Btw note that opening gnome-language-selector and selecting "None" creates that file and causes the issue again!!! So we try to never open gnome-language-selector. That's all I know about the issue; I found out that Ubuntu Mate comes without ibus/fcitx installed, so we've switched to using that one, where the Xorg system-wide keyboard defaults are respected and remain unmodified after login and everything works flawlessly! :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1584314 Title: Togo keyboard layout / compose keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1584314/+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 891793] Re: Login with USB key or smart card
Hi, LDM will be deprecated in LTSP 6, so I don't think anyone's going to work on this issue. So I'm marking it "Won't Fix". ** Changed in: ltsp Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/891793 Title: Login with USB key or smart card To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/891793/+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 1298846] Re: AMD Radeon HD [1002:9834][1002:9830] Unable to boot to desktop without the nomodeset parameter
This bug still exists in a supported release, namely 12.04.5, with the trusty backported xorg stack. # lspci -nn -k | grep -A 2 VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400] [1002:9830] Subsystem: ASUSTeK Computer Inc. Device [1043:8623] Kernel driver in use: radeon I'll attach the Xorg.log as well, which shows the segfault. ** Package changed: xorg-lts-saucy (Ubuntu) => xorg-lts-trusty (Ubuntu) ** Changed in: xorg-lts-trusty (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-lts-saucy in Ubuntu. https://bugs.launchpad.net/bugs/1298846 Title: AMD Radeon HD [1002:9834][1002:9830] Unable to boot to desktop without the nomodeset parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-trusty/+bug/1298846/+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 1463663] Re: [SRU] Enable setting property of type UTF8_STRING
I've verified that x11-utils 7.6+4ubuntu0.2 works as expected in Ubuntu 12.04.1, please push it to precise-updates. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1463663 Title: [SRU] Enable setting property of type UTF8_STRING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1463663/+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 1463663] [NEW] [SRU] Enable setting property of type UTF8_STRING
Public bug reported: [Impact] Xprop added support for UTF8_STRING back in 2009: http://cgit.freedesktop.org/xorg/app/xprop/commit/?id=eb64005382abf6262c913a46e6186e019a179d59 Unfortunately `xprop -f 8u -set` has been broken until 2012: http://cgit.freedesktop.org/xorg/app/xprop/commit/?id=0d069c0edae83f70ac10fab1a3c04d8197e277c4 That patch has not been backported to Ubuntu 12.04.1 (x11-utils 7.6+4), so it's impossible to use 8u there. One notable use case is with LTSP, where we're using xprop as an ad-hoc mechanism for server=thin clients communication, and we were recently asked to add UTF8 support to it: https://bugs.launchpad.net/ltsp/+bug/1451915 [Test Case] This is how to reproduce the issue on Precise 12.04.1: $ lsb_release -r Release:12.04 $ dpkg-query -W x11-utils x11-utils 7.6+4ubuntu0.1 $ xprop -root -f LTSP_COMMAND 8u -set LTSP_COMMAND xterm xprop: error: bad format character: u This is what the correct output looks like on Trusty 14.04.2: $ lsb_release -r Release:14.04 $ dpkg-query -W x11-utils x11-utils 7.7+1 $ xprop -root -f LTSP_COMMAND 8u -set LTSP_COMMAND xterm no output, no error $ xprop -root | grep LTSP_COMMAND LTSP_COMMAND(UTF8_STRING) = xterm [Regression Potential] Low, the patch comes from upstream and it's already included in all Ubuntu versions after 12.04.1. ** Affects: x11-utils (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1463663 Title: [SRU] Enable setting property of type UTF8_STRING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1463663/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
Fix released in LTSP 5.4.5. ** Changed in: ltsp Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
Fix committed in http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp- trunk/revision/2447. ** Changed in: ltsp Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
The committed fix is applied too late, after xorg is loaded. So it's not working on the first login, but only on subsequent logins. The `rm -f /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so` command should be run from some init-ltsp.d script instead. A workaround that doesn't involve updating the chroot is to put this in lts.conf: [Default] RCFILE_01=rm -f /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so ** Changed in: ltsp Status: Fix Committed = In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 496363] Re: Installing nvidia kills xorg on non-nvidia systems, or makes display upside down
Added LTSP to the affected projects, because it's very common there (nvidia drivers on the LTSP server, and e.g. intel-based clients), even though it can't be fixed in that project. ** Also affects: ltsp (Ubuntu) Importance: Undecided Status: New ** Changed in: ltsp (Ubuntu) Status: New = Invalid ** Changed in: ltsp (Ubuntu Lucid) Status: New = Invalid -- 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/496363 Title: Installing nvidia kills xorg on non-nvidia systems, or makes display upside down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/496363/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
Fix committed in http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/revision/1453. It is just a temporary workaround, it should be removed in the future once the nouveau bug is resolved. It'd be nice if someone could SRU this, as many LTSP users are affected. ** Changed in: ltsp Importance: Undecided = High ** Changed in: ltsp Status: New = Fix Committed ** Changed in: ltsp Assignee: (unassigned) = Alkis Georgopoulos (alkisg) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
Another teacher reports the same problem in these clients: root@ltsp135:~# lspci -nn -k | grep -A 2 VGA 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV18 [GeForce4 MX 4000] [10de:0185] (rev c1) Subsystem: Micro-Star International Co., Ltd. Device [1462:9363] Kernel driver in use: nouveau -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
Some people are reporting that this doesn't happen in a fresh 12.04.1 installation, but it happens after they `apt-get update` their server. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
In this case, although with Precise not updated for a couple of months, the problem did NOT happen: # lspci -nn -k | grep -A 2 VGA 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev b2) Kernel driver in use: nouveau Kernel modules: nouveau, nvidiafb, rivafb -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 1072711] Re: LIBGL_ALWAYS_INDIRECT causes firefox crashes
Attaching Xorg.log where the segfault in nouveau_vieux_dri.so can be seen. An easy way to reproduce the problem without LTSP: (from a client with an nvidia card): $ ssh -X server $ LIBGL_ALWAYS_INDIRECT=true firefox One workaround mentioned in #nouveau: (08:34:05 πμ) airlied: got all the accel you are going to get you might just mv the nouveau_vieux_dri.so aside Tested it and it works fine, maybe we can do that on in /usr/share/ldm/rc.d/X51-opengl (inside the if so that it affects thin clients only). ** Attachment added: Xorg.7.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1072711/+attachment/3419496/+files/Xorg.7.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1072711 Title: LIBGL_ALWAYS_INDIRECT causes firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/1072711/+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 541492] Re: MASTER: [i845] GPU lockup
** No longer affects: ltsp -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/541492 Title: MASTER: [i845] GPU lockup To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/541492/+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 891793] Re: Login with USB key or smart card
** Also affects: ltsp Importance: Undecided Status: New ** No longer affects: ldm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/891793 Title: Login with USB key or smart card To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/891793/+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 206924] Re: Make it possible to create a guest account
** Also affects: ltsp Importance: Undecided Status: New ** No longer affects: ldm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdm in Ubuntu. https://bugs.launchpad.net/bugs/206924 Title: Make it possible to create a guest account To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/206924/+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 511001] Re: [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?)
So the best workaround so far for me is to use the https://launchpad.net/~brian-rogers/+archive/experimental kernel which gives me KMS, 3D and XV with no problems. Erm, actually that's true for an older kernel that Brian Rogers had uploaded there: 2.6.34rc3-51-generic With the last kernel there (2.6.35rc4-v9patch1.e467e10), KMS isn't working and X will only start in fail-safe mode (vesa). @Brian, could you please reupload 2.6.34rc3-51-generic because I want to install it to another laptop with 855 and I didn't keep the .deb? Thank you! -- [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?) https://bugs.launchpad.net/bugs/511001 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ 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 476817] Re: [i855] [karmic] X freezes with intel 855GM videocard
@Brian Rogers: I tried the last kernel from your ppa (2.6.35rc4-v9patch1.e467e10) on another laptop with 855, and X wouldn't start unless nomodeset was used. Could you please reupload 2.6.34rc3-51-generic because that works for me, but I didn't keep the .deb? Thank you! The other methods listed in https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes won't give me KMS, XV and 3D simultaneously, so 2.6.34rc3-51-generic is the only way for my graphics card to work properly. -- [i855] [karmic] X freezes with intel 855GM videocard https://bugs.launchpad.net/bugs/476817 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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 476817] Re: [i855] [karmic] X freezes with intel 855GM videocard
Thank you Brian for all the help. I tried linux-image-2.6.35-ppa20+v9patch-generic and the cursor was invisible. I tried linux-image-2.6.35-ppa20+v9+cursorfix-generic and almost everything was working fine: KMS, 3D, XV... glxgears even reported 308 fps instead of 260 fps that it showed with the 2.6.34rc3-51-generic kernel. An annoying glitch with linux-image-2.6.35-ppa20+v9+cursorfix-generic though: every exactly 10 seconds, a process named kslowd000 caused a CPU spike, which resulted in the computer hanging for half a second - mouse not moving, screen not updating etc. So the best solution for me was to clone my hard disk to transfer the old 2.6.34rc3-51-generic to the other laptop. I hope that the CPU glitch above can be fixed so that I can use the newer kernel with its significant performance improvement. Btw, why aren't those kernels mentioned in https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes ? It's the only way to make those laptops work properly in Lucid... Thanks again! -- [i855] [karmic] X freezes with intel 855GM videocard https://bugs.launchpad.net/bugs/476817 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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 476817] Re: [i855] [karmic] X freezes with intel 855GM videocard
Googling revealed a thread that looks relevant to me: http://www.gossamer-threads.com/lists/linux/kernel/1238374 One even mentions the 10 secs interval between each hanging. Post #15 claims to have a solution. -- [i855] [karmic] X freezes with intel 855GM videocard https://bugs.launchpad.net/bugs/476817 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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 511001] Re: [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?)
I tested https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes#GTT%20Incoherency%20Patch on my laptop with: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) While it allowed the system to boot, and KMS / 3D acceleration were working fine, it had problems with XV. E.g. testing XV with gstreamer-properties resulted in a crash: $ gstreamer-properties gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'esdsink' gstreamer-properties-Message: Skipping unavailable plugin 'glimagesink' gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' The program 'gstreamer-properties' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 60 error_code 11 request_code 132 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) So the best workaround so far for me is to use the https://launchpad.net/~brian-rogers/+archive/experimental kernel which gives me KMS, 3D and XV with no problems. -- [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?) https://bugs.launchpad.net/bugs/511001 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ 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 511001] Re: [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?)
Thank you for the tip Willem, with that kernel I'm also able to boot with KMS on and Xv and everything. I only noticed a small glitch, in Xv sometimes (e.g. in totem, but not with fullscreen nor in vlc) there's a black overlay over the video. And if I click on a totem menu, and then I close the totem menu, the black overlay is left where the menu was. Anyway, it's very workable with that kernel, thanks again. -- [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?) https://bugs.launchpad.net/bugs/511001 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ 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 476817] Re: [i855] [i855] [karmic] X freezes with intel 855GM videocard
I can also confirm that the ppa kernel works for me in Lucid, while without it I can't boot my old laptop. My card is: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) 2.6.32-20.30 = Last one that boots, crashes with Xv 2.6.32-21.32 = It hangs when X starts 2.6.32-22.33 = It hangs when X starts 2.6.34rc3-51.2 = Works fine with KMS and Xv and everything. One minor glitch, I'm sometimes seeing a black square over the Xv video (e.g. on totem but not on vlc), covering all of the video. In totem, when I open a menu and close it, that black square goes where the menu was. And when I switch to fullscreen it goes away so I can see the video normally. (for more details see my posts in bug #511001) Please backport that newest patch for Lucid. :) -- [i855] [i855] [karmic] X freezes with intel 855GM videocard https://bugs.launchpad.net/bugs/476817 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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 511001] Re: [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?)
I can't boot with any of the recent kernels. I have this card on my laptop: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) I'm using the linux-image-generic kernels: 2.6.32-20.30 = Last one that boots 2.6.32-21.32 = It hangs when X starts 2.6.32-22.33 = It hangs when X starts I've tried nomodeset, i915.modeset=0 etc with no difference. Also, while 2.6.32-20.30 boots fine, it crashes when I try anything Xv- related (gstreamer-properties, totem, vlc...) -- [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?) https://bugs.launchpad.net/bugs/511001 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ 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 460328] Re: Wrong keyboard settings when console-settings has multiple layouts
Thank you, much appreciated. -- Wrong keyboard settings when console-settings has multiple layouts https://bugs.launchpad.net/bugs/460328 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev 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 460328] Re: Wrong keyboard settings when console-settings has multiple layouts
Before Karmic, I didn't have to configure gnome at all (meaning, all the gconf settings were working fine if they were empty). Console-setup was configured to [us,gr], and X would pick it up and let me work with it, and allow me to switch layouts, no matter if I used an xterm, gnome, or kde session. I could type a mixed English/Greek password in gdm. I think it'd be better if all the involved programs were modified to work correctly when all the gconf keys are empty. I.e. gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard inside a session should not result in a broken layout/ability to switch etc... -- Wrong keyboard settings when console-settings has multiple layouts https://bugs.launchpad.net/bugs/460328 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev 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 283128] Re: Keyboard indicator shows additional layout null
Just wondering, when you're experiencing the problem, what do you get if you give this? gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Because I had similar symptoms, but they were caused by gdm.. -- Keyboard indicator shows additional layout null https://bugs.launchpad.net/bugs/283128 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config 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 517276] Re: [G84] X freezes after pressing ENTER
While X freezes I can't switch to vt1, so I'm sending two directories with the files, one before the freeze, and one after the freeze but also after the X reset. Both of them are while I'm on gdm. Also, when switching to vt1 before the freeze, I'm not seeing the expected console output, but only random characters and colors, like if the 0xB800 segment is filled with random data (it might be the gdm wallpaper). So I had to make a shell script with the dmesg, top etc commands and logon/run it blindly. I tried removing quiet splash from grub.cfg, and also removing my xorg.conf, so that nv is used instead of nvidia, but I only noticed a minor change in the random characters / colors pattern - vt1 was still unusable before the freeze. While switching back to gdm (and before the freeze), I could see two small dots blinking on the top of my screen, which I suppose would be the cursor. After X freezes and I reset it, everything is back to normal: the console is ok, no blinking dots in gdm etc. Thank you for your time! ** Attachment added: logs.tar.gz http://launchpadlibrarian.net/38859978/logs.tar.gz -- [G84] X freezes after pressing ENTER https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 517276] Re: [G84] X freezes after pressing ENTER
*** This bug is a duplicate of bug 516412 *** https://bugs.launchpad.net/bugs/516412 I'm not sure if my initial problem was a duplicate of #516412, but what I'm experiencing now, after the reinstallation, surely is. Removing plymouth solved my problem. Thanks! ** Package changed: xorg-server (Ubuntu) = plymouth (Ubuntu) ** This bug has been marked a duplicate of bug 516412 Pressing Enter causes X to freeze -- [G84] X freezes after pressing ENTER https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 517276] Re: 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
I don't know if it's due to my lack of observation or due to the fact that I've reinstalled Lucid, and I'm using i386 instead of amd64 now, but the symptoms have changed a bit. Now I get an X crash the first time I press the [Enter] key. I'm getting that both with the current xserver-xorg-core 2:1.7.3.902-1ubuntu12 *AND* with the previous -1ubuntu9, which I didn't get when I filed the bug report. So, in order to keep using my PC, I'm usually booting to gdm, pressing [Enter] so that it hangs, pressing Alt+Ctrl+Print screen+K to restart X, and the I'm able to work fine! It doesn't hang after the first time! I also tried enabling autologon, to bypass gdm. Again, X crashes when I e.g. open firefox, write a URL and press [Enter]. Just on the first Enter, it doesn't crash after that. I'm attaching the requested files exactly after the steps mentioned above, and also the output of: gconftool-2 --dump /desktop/gnome/peripherals/keyboard ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/38850338/Xorg.0.log -- 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 517276] Re: 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
** Attachment added: messages http://launchpadlibrarian.net/38850355/messages -- 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 517276] Re: 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
** Attachment added: keyboard http://launchpadlibrarian.net/38850358/keyboard -- 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 517276] Re: 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
I've just seen that this also works for me: * Booting to gdm * Resetting X * Logging on normally I.e. an X reset, even without pressing the [Enter] key so that it hangs first, also allows me to work without problems. -- 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 517276] Re: [G84] X freezes after pressing ENTER
Yes, that Xorg.0.log was just after the X reset while on gdm and before logging in. I'm attaching Xorg.0.log.old. I'm still on the same session, I haven't rebooted since. Thank you for the ACPI-errors notice. :-) ** Attachment added: Xorg.0.log.old http://launchpadlibrarian.net/38851221/Xorg.0.log.old -- [G84] X freezes after pressing ENTER https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 517276] [NEW] 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked
Public bug reported: Using Lucid amd64, after today's updates my PC crashes after 1-2 minutes of usage. Downgrading xserver-xorg-core and xserver-common to 2:1.7.3.902-1ubuntu9 worked fine for me. I also tried with the daily-live 20100203 and I got the same problem. I tried with the nvidia, nv, and the failsafe (vesa) drivers. Symptoms vary: Sometimes X crashes and I get to gdm. Sometimes I see corruption on the top of the screen, like terminal consoles drawn in the wrong bit-plane in the video ram. Sometimes the kernel hangs, caps lock is flashing, and ping/REISUB do not work. My hardware: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03) 00:01.0 PCI bridge [0604]: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port [8086:2a01] (rev 03) 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) 00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 03) 00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 [8086:2849] (rev 03) 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03) 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03) 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03) 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 03) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03) 00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 03) 00:1f.2 SATA controller [0106]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller [8086:2829] (rev 03) 00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 03) 01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) 06:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61) 08:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express [14e4:1693] (rev 02) 0a:09.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 05) 0a:09.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22) 0a:09.2 System peripheral [0880]: Ricoh Co Ltd R5C843 MMC Host Controller [1180:0843] (rev 12) 0a:09.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 12) 0a:09.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev ff) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 2:1.7.3.902-1ubuntu10 crashes for me, up to -ubuntu9 it worked https://bugs.launchpad.net/bugs/517276 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server 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 267269] Re: system GUI turn upside down when visual effects changed from none to normal
For the LTSP client mirrored screen, see this bug, it's because of the proprietary drivers on the server: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/441586 -- system GUI turn upside down when visual effects changed from none to normal https://bugs.launchpad.net/bugs/267269 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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 460328] Re: Wrong keyboard settings when console-settings has multiple layouts
Verifying this for Lucid Alpha 1. Please make gdm use a [Default] layout by default, one which simply doesn't write anything to /desktop/gnome/peripherals/keyboard/kbd/layouts, as opposed to using/forcing the [us] layout. -- Wrong keyboard settings when console-settings has multiple layouts https://bugs.launchpad.net/bugs/460328 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev 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 482875] Re: Since upgrade from jaunty to karmic, one of two thin clients' login broken.
*** This bug is a duplicate of bug 463369 *** https://bugs.launchpad.net/bugs/463369 ** This bug has been marked a duplicate of bug 463369 [RN50] glxinfo breaks with XAA (needs EXA) ** Package changed: ltsp (Ubuntu) = xserver-xorg-video-ati (Ubuntu) -- Since upgrade from jaunty to karmic, one of two thin clients' login broken. https://bugs.launchpad.net/bugs/482875 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati 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
