[Ubuntu-x-swat] [Bug 210458] Re: nVidia GLX-driver breaks console
Could you please try a newer and supported Ubuntu version with the latest drivers? Thank you very much! ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-drivers-ubuntu Status: New => Invalid ** Changed in: nvidia-drivers-ubuntu Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/210458 Title: nVidia GLX-driver breaks console To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/210458/+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
Marking as confirmed because it affects several users. ** Changed in: accountsservice (Ubuntu) Status: New => Confirmed -- 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 1099846] Re: with dual monitors connected, ubuntu will not shutdown
[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Expired -- 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/1099846 Title: with dual monitors connected, ubuntu will not shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1099846/+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 1180646] Re: cairo-dock rendering issues using openGL backend on intel GPU
u have changed the address to cairo-dock render problem but isn't that photo shows an ubuntu bug ? http://imageshack.us/photo/my-images/844/screenshotfrom201305160.png/ ty -- 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/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+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 1180646] Re: cairo-dock rendering issues using openGL backend on intel GPU
what is going on now ? can any one explain ? ty -- 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/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+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 1098561] Re: "Unsupported hardware" watermark appears when FGLRX is installed on 13.04
I have the same fglrx-updates version. All the output of fglrxinfo is the same as yours except for the renderer string and the compatibility profile context (mine is 9.012). If the second workaround didn't work, I would first uninstall the proprietary driver and used the FOSS driver. If the FOSS driver doesn't work (doesn't work for me, either), then try the first workaround. In the rare event that something goes wrong, sudo apt-get purge fglrx- updates and reinstall. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1098561 Title: "Unsupported hardware" watermark appears when FGLRX is installed on 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1098561/+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 990265] Re: Desktop Setup: Black screen with blinking cursor
I had this problem with 12.04.1 using the HDMI but it seems to be corrected in 12.04.2 ASUS EB1033 which uses the Nvidia 610M graphics. -- 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/990265 Title: Desktop Setup: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/990265/+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 1098561] Re: "Unsupported hardware" watermark appears when FGLRX is installed on 13.04
I have installed fglrx-updates and I still have the "Unsupported hardware" watermark. According to synaptic the fglrx-updates version is: 2:9.012 I'm using Linux Mint 15 (upgraded from 14). fglrxinfo outputs: display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon (TM) HD 8500M/8700M OpenGL version string: 4.2.12002 Compatibility Profile Context 12.104 I have an HP Sleekbook with dual graphics card (Radeon HD 7600G + Radeon HD 8500M) and an A8 processor. I have tested the 2nd workaround copying the "control" file from the previous driver (12.X, can't remember correctly which one it was). Any other suggestions? Or updates? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1098561 Title: "Unsupported hardware" watermark appears when FGLRX is installed on 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1098561/+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 1180986] Re: X Segmentation fault with dual-head config on Matrox G45FMDVP32DB /32MB /DVI /VGA
Hello Tormod. This was the first time I tested Matrox dual-head with Ubuntu. I'm not 100% sure if i remember that correctly, but I think it worked correctly with Mageia 2. Of course they could have completely different component versions and local patches. I tried to figure out what component the issue lies in by testing an ATI Radeon 7000 card with dual-head in the same computer and it worked without problems. Both screens worked correctly and I could manage them with xrandr ... so I believe it must be the MGA driver. As the Xorg guys still doing enhancements and forget to redesign drivers dependent on removed obsolete features, it's kinda expectable. Anyway, according to the manuals on the Internet, this feature worked correctly in the past. If you have any questions or request, don't hesitate to ask. I'm willing to do any tests, if you want. Thanks and regards, Jaromir. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in Ubuntu. https://bugs.launchpad.net/bugs/1180986 Title: X Segmentation fault with dual-head config on Matrox G45FMDVP32DB /32MB /DVI /VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1180986/+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 801952] Re: problem with ATI Catalyst Control Center (Administrative Mode) launcher
Same probleme with last version of ubuntu (13.04) and Catalyst (13.4). My last configuration was fine. I reinstalled completely ubuntu and began to install Catalyst first. Still the samedi issue ! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/801952 Title: problem with ATI Catalyst Control Center (Administrative Mode) launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/801952/+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 628727] Re: Screen corruption make UNE unusable (xorg issue)
https://wiki.ubuntu.com/Releases ** Changed in: unity (Ubuntu Maverick) Status: New => Invalid ** Changed in: mesa (Ubuntu Natty) Status: Triaged => Invalid ** Changed in: mesa (Ubuntu Maverick) Status: New => Invalid ** Changed in: xserver-xorg-video-ati (Ubuntu Maverick) Status: New => Invalid ** Changed in: xserver-xorg-video-ati (Ubuntu Natty) Status: Triaged => Invalid ** Tags removed: maverick -- 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/628727 Title: Screen corruption make UNE unusable (xorg issue) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/628727/+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 1127915] Re: Installing libxrandr-dev-lts-quantal will remove libxrandr-dev and related deps i.e. libgtk2.0-dev or libgtk-3-dev etc.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libxrandr-lts-quantal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxrandr-lts-quantal in Ubuntu. https://bugs.launchpad.net/bugs/1127915 Title: Installing libxrandr-dev-lts-quantal will remove libxrandr-dev and related deps i.e. libgtk2.0-dev or libgtk-3-dev etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr-lts-quantal/+bug/1127915/+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 686388] Re: [i965gm] GPU lockup - Invalid GTT entry during Display B Fetch
** Changed in: linux (Ubuntu Natty) Status: Confirmed => Invalid -- 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/686388 Title: [i965gm] GPU lockup - Invalid GTT entry during Display B Fetch To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/686388/+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 573275] Re: tc1100 stylus buttons regression
** Changed in: xf86-input-wacom (Ubuntu Natty) Status: In Progress => Invalid ** Tags removed: natty ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/573275 Title: tc1100 stylus buttons regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/573275/+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 800778] Re: Unexplained X Crash On Intel Sandybridge
** Changed in: mesa (Ubuntu Natty) Status: Triaged => Invalid -- 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/800778 Title: Unexplained X Crash On Intel Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/800778/+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 780961] Re: Xorg crash in PlayReleasedEvents with Sawfish when using keyboard-based window management
https://wiki.ubuntu.com/Releases ** Changed in: xorg-server (Ubuntu Oneiric) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu Natty) Status: Confirmed => Invalid -- 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/780961 Title: Xorg crash in PlayReleasedEvents with Sawfish when using keyboard- based window management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/780961/+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 1139636] Re: fglrx drivers freeze Xorg
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer-updates (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1139636 Title: fglrx drivers freeze Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1139636/+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 742683] Re: on upgrade, keyboard config changed to use deadkeys
** Changed in: xkeyboard-config (Ubuntu Natty) Status: Triaged => Invalid -- 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/742683 Title: on upgrade, keyboard config changed to use deadkeys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/742683/+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 742673] Re: after upgrade to natty, X only sees external USB keyboard/mouse
https://wiki.ubuntu.com/Releases ** Changed in: xserver-xorg-input-evdev (Ubuntu Natty) Status: Incomplete => Invalid -- 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/742673 Title: after upgrade to natty, X only sees external USB keyboard/mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/742673/+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 649809] Re: the session settings manager can try starting before the login screen one exits
https://wiki.ubuntu.com/Releases ** Tags removed: maverick natty ** Changed in: gnome-settings-daemon (Ubuntu Natty) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/649809 Title: the session settings manager can try starting before the login screen one exits To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/649809/+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 1092623] Re: touchpad multipoint touching opens Unity Dash
Fixed after upgrading to 13.04. I am cursing a lot less now... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1092623 Title: touchpad multipoint touching opens Unity Dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1092623/+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 1092615] Re: X server crashes repeatedly with touchpad movements
Updated to 13.04 and have not seen this problem since the upgrade. This bug was almost enough to make Windows look good; nice to see it is finally fixed in the new release. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1092615 Title: X server crashes repeatedly with touchpad movements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1092615/+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 990265] Re: Desktop Setup: Black screen with blinking cursor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Confirmed -- 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/990265 Title: Desktop Setup: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/990265/+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 786952] Re: Wacom Bamboo Pen - Pressure too sensitive (Needs kernel 3.1 patch backported)
** Changed in: linux (Ubuntu Oneiric) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/786952 Title: Wacom Bamboo Pen - Pressure too sensitive (Needs kernel 3.1 patch backported) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/786952/+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 855124] Re: XRANDR operations very slow unless (phantom) HDMI1 disabled
kernel fix ** Tags removed: oneiric ubuntu ** Changed in: ubuntu-boot-speed Status: Triaged => Invalid -- 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/855124 Title: XRANDR operations very slow unless (phantom) HDMI1 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/855124/+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 855124] Re: XRANDR operations very slow unless (phantom) HDMI1 disabled
** Changed in: linux (Ubuntu Oneiric) Status: Triaged => Invalid -- 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/855124 Title: XRANDR operations very slow unless (phantom) HDMI1 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/855124/+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 1142733] Re: Nvidia: unknown chipset
OK, here is what I obtained. Hope this helps :) ** Attachment added: "current-trace.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1142733/+attachment/3680175/+files/current-trace.txt -- 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/1142733 Title: Nvidia: unknown chipset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1142733/+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
Re: [Ubuntu-x-swat] [Bug 1180965] Re: mouse frozen
yes it looks similar, but switching to a virtual terminal does not help for me 2013/5/18 Adolfo Jayme Barrientos > Likely a dupe of bug report 1030244? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1180965 > > Title: > mouse frozen > > Status in “xorg” package in Ubuntu: > New > > Bug description: > mouse pointer unexpectedly frozen, keyboard still works. After log out > log in cursor works fine > > ProblemType: Bug > DistroRelease: Ubuntu 12.10 > Package: xorg 1:7.7+1ubuntu4 > ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9 > Uname: Linux 3.5.0-28-generic x86_64 > .tmp.unity.support.test.0: > > ApportVersion: 2.6.1-0ubuntu10 > Architecture: amd64 > CompizPlugins: > [core,bailer,detection,gtkloader,composite,opengl,imgjpeg,decor,text,mousepoll,move,imgsvg,compiztoolbox,snap,regex,place,imgpng,vpswitch,grid,gnomecompat,dbus,resize,animation,wall,unitymtgrabhandles,session,expo,fade,workarounds,ezoom,scale,unityshell] > CompositorRunning: kwin > Date: Thu May 16 21:35:41 2013 > DistUpgraded: 2013-05-13 10:37:15,444 DEBUG enabling apt cron job > DistroCodename: quantal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD > 4500/5100 Series] [1002:9553] (prog-if 00 [VGA controller]) > Subsystem: Acer Incorporated [ALI] Device [1025:0205] > MachineType: Acer Aspire 5738 > MarkForUpload: True > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-28-generic > root=UUID=885bdba1-475a-40cd-b7f0-da5287b28588 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: Upgraded to quantal on 2013-05-13 (3 days ago) > dmi.bios.date: 05/06/2010 > dmi.bios.vendor: Phoenix Technologies LTD > dmi.bios.version: V1.33 > dmi.board.name: JV50 > dmi.board.vendor: Acer > dmi.board.version: Rev > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnPhoenixTechnologiesLTD:bvrV1.33:bd05/06/2010:svnAcer:pnAspire5738:pvr0100:rvnAcer:rnJV50:rvrRev:cvnAcer:ct10:cvrN/A: > dmi.product.name: Aspire 5738 > dmi.product.version: 0100 > dmi.sys.vendor: Acer > version.compiz: compiz N/A > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.43-0ubuntu0.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.7.3-0ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati > 1:6.99.99~git20120913.8637f772-0ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.20.9-0ubuntu2.1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.2-0ubuntu3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1180965/+subscriptions > -- 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/1180965 Title: mouse frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1180965/+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 1070677] Re: Xorg fails to start because of Radeon Issue [(EE) RADEON(0): [drm] failed to set drm interface version]
For me on 13.04, although the error message in Xorg.log was the same, it turned out to be caused by #714492 (plymouth). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1070677 Title: Xorg fails to start because of Radeon Issue [(EE) RADEON(0): [drm] failed to set drm interface version] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1070677/+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
