[Ubuntu-x-swat] [Bug 1943818] Re: mesa built with -O3 on ppc64el has broken EGL
** Also affects: ubuntu-power-systems Importance: Undecided Status: New -- 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/1943818 Title: mesa built with -O3 on ppc64el has broken EGL To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1943818/+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 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)
Had the same issue in Ubuntu 20.04. I plugged in a keyboard with a Numlock key and switch that off. That fixed it for me. -- 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/1783987 Title: German Neo2 Problem with Xubuntu 18.04 (try out mode) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1783987/+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 1878951] Re: [nvidia] Hotplugging HDMI monitor is ignored, needs to be manually re-enabled
Workaround for me was to use external USB-C to HDMI adapter and plug the USB-C to the computer. -- 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/1878951 Title: [nvidia] Hotplugging HDMI monitor is ignored, needs to be manually re- enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878951/+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 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
For me, it doesn't seem to be fixed. I have installed mutter 3.36.4 and rebooted. When I set my external 4k AOC display to 200% and the internal monitor to 100%, it works. However, if I increase the scaling of the internal monitor to 125% in display settings, I get the both screens turn black and reverts to the previous settings shortly after. Please let me know if you need anything more from me. -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
problem seems to appear only with nouveau driver, i installed the propritary (like it is on 18.4) and it works now as. seems anything in nouveau driver is missing for multi-monitor-support -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
mhm, ubuntu-session is same...i see cursor but no background/window while dragging, this time it looks stable, after loggin out (from ubuntu-session), i see login-form on laptop-screen and purple background on external monitor. after logging into flashback it's same as in ubuntu-session with black screen, cursor visible but no windows -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
is maybe this also handled by gnome-flashback directly? -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
https://gitlab.gnome.org/GNOME/mutter/-/issues/1351 but currently it looks related to nvidia/nouveau driver ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1351 https://gitlab.gnome.org/GNOME/mutter/-/issues/1351 -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878718] Re: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable
I would add that "severity" of this issue lies in the confusion. I believed this feature is actually broken, since the fn key works in Plasma and there wasn't any indication that there is another shortcut. -- 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/1878718 Title: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878718/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
anything new here? i see mutter gets an update to 3.36.2, but bug is still present. anything i can do as workaround? -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878718] Re: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable
a) When I do a short press, then immediately after a release, the next option is selected (the dialog does not have time to appear even). b) When I do a long press, then the options start to circle very quickly until I release the key (see the screencast) I think the bug is caused by this: When you do Super+K, you hold Super and press K repeatedly to switch the options. After you release the Super key, the option is confirmed. When you use the fn key, there is just one key, so after releasing, it immediately selects the option. -- 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/1878718 Title: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878718/+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 1878953] [NEW] Display settings is lost when switching between modes with Super+P
Public bug reported: When switching between modes (built-in only, joint, ...) with Super+P, the display settings are lost. That even occurs when selecting already selected mode (selecting "joint" while being in "joint" mode). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 18:12:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 focal 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/1878953 Title: Display settings is lost when switching between modes with Super+P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878953/+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 1878951] [NEW] External monitor won't reconnect after reattaching HDMI cable
Public bug reported: Steps to reproduce: 1. Successfully connect AOC u2879vf external display by attaching HDMI cable 2. Remove the cable, output switches to the built-in display and external display goes black 3. Reconnect the HDMI cable again What is expected: The external screen should display the image (as in step 1) What happened instead: The system thinks the display is connected (see the xrandr output), but the external display is still black (no signal). The clumsy workaround is to use Super+P to switch to "built-in display only" and then back to "joint". After that, the external monitor comes back. xrandr outputs: Step 1 Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0029.9829.9725.0023.98 1920x2160 59.99 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 connected 1920x1080+909+2160 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) Step 2 Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) Step 3 Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0029.9829.9725.0023.98 1920x2160 59.99 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 connected 1920x1080+1097+2160 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 17:43:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A
[Ubuntu-x-swat] [Bug 1878884] [NEW] Fractional scaling results in black screen
Public bug reported: Steps to reproduce == 1. Open display settings 2. Enable fractional scaling 3. Set particular scale for external and internal monitor What is expected Working displays What happened instead = Experiencing a black screen. I can get the output back by switching to another display output with Super+P, which resets the scaling fraction. Additional info === Screencast in the attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 11:19:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 focal ubuntu ** Attachment added: "Screencast from 2020-05-15 11:20:05.webm" https://bugs.launchpad.net/bugs/1878884/+attachment/5371962/+files/Screencast%20from%202020-05-15%2011%3A20%3A05.webm -- 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/1878884 Title: Fractional scaling results in black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878884/+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 1878718] [NEW] Hotkey for switching display output unusable due to switching to next option immediately after release
Public bug reported: Steps to reproduce: 1. Press the functional button for switching output to displays (joint, mirror, bulit-in, external) 2. The dialog is invoked What is expected: I should be able to select the desired option and confirm it What happened instead: While the functional button for invoking the dialog is pressed, it iterates extremely fast over the options. I cannot control it. After releasing the key, the currently selected option is confirmed, which is effectively random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 01:28:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 focal ubuntu ** Attachment added: "Screencast from 2020-05-15 01:45:04.webm" https://bugs.launchpad.net/bugs/1878718/+attachment/5371766/+files/Screencast%20from%202020-05-15%2001%3A45%3A04.webm -- 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/1878718 Title: Hotkey for switching display output unusable due to switching to next option immediately after release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878718/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
from journal log this looks wrong: Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: xf86EnableIOPort s: failed to set IOPL for I/O (Operation not permitted) Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(0): using drv /dev/dri/card0 Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (WW) Falling bac k to old probe method for fbdev Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) Loading sub module "fbdevhw" Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) LoadModule: "fbdevhw" Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so ... Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (EE) open /dev/f b0: Permission denied Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : using drv /dev/dri/card1 Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (WW) VGA arbiter : cannot open kernel arbiter, no multi-card support ... Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (EE) modeset(G0): glamor initialization failed but here it looks like monitor is correctly found (like in gnome-preferences) Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : EDID for output HDMI-1-2 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : Manufacturer: HPN Model: 363a Serial#: 16843009 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : Year: 2019 Week: 41 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : EDID Version: 1.3 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : Digital Display Input -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
after my laptop-screen goes off (automatic locking of workstation) and i retouched it to go on again, i see some flickering on the external monitor with background-image, but it looks like there was heavy load so that login-screen wasn't displayed (see also background on internal screen)...have now switched off external monitor to get login-window again...maybe this helps to get the issue nailed down -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
** Attachment added: "journalctl -b0" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878421/+attachment/5371462/+files/journal.txt -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878421] Re: Using two GPUs with one monitor each, one is always black
dmesg looks clean so far, intel card (internal display) is fb0 and nvidia-card for hdmi (external 4k monitor hp 27f) $ dmesg | grep frame [0.882504] efifb: framebuffer at 0x8000, using 8100k, total 8100k [0.882611] Console: switching to colour frame buffer device 240x67 [0.887919] fb0: EFI VGA frame buffer device [1.392526] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [3.605988] Console: switching to colour frame buffer device 240x67 [3.633864] i915 :00:02.0: fb0: i915drmfb frame buffer device [3.718640] nouveau :01:00.0: fb1: nouveaudrmfb frame buffer device see full dmesg in attachment strange is that i have no X.org.log in /var/log, anything i can try to workaround/test for affected Package? noticed, that on login-screen the background of external monitor is purple and switches to black (default color without background-image) ** Attachment added: "dmesg after starting with 2nd gpu enabled" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878421/+attachment/5371457/+files/dmesg_multigpu.txt -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+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 1878421] [NEW] 20.4 - hybrid-graphics
Public bug reported: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal- output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 focal 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/1878421 Title: 20.4 - hybrid-graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1878421/+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 1850681] Re: Touchpad and touchsrceen not working
Thanks again :-) -- 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/1850681 Title: Touchpad and touchsrceen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1850681/+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 1850681] [NEW] Touchpad and touchsrceen not working
Public bug reported: touchpad not working, only usb-mouse is recognized. touchscreen functionality not working, but that would be rather less important. Everything else is perfectly fine. (18.04 LTS) TREKSTOR Primebook C11B Thanks :-) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 18:43:32 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2019-10-26 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: TREKSTOR Primebook C11B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1.2 dmi.board.asset.tag: Default string dmi.board.name: Apollolake_alk_V01 dmi.board.vendor: TS_weibu dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: Primebook C11B dmi.product.sku: CFALKWW03 dmi.product.version: Default string dmi.sys.vendor: TREKSTOR version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1850681 Title: Touchpad and touchsrceen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1850681/+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 1835459] Re: libgl1-mesa-glx errors
** Summary changed: - libgl1-mesa-glx + libgl1-mesa-glx errors -- 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/1835459 Title: libgl1-mesa-glx errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835459/+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 1835459] [NEW] libgl1-mesa-glx
Public bug reported: I have a VPS with Ubuntu 18.04 (implementation of pure software, Digital Ocean) and I connect through Windows 10 with an X server, Xming and I run Google-Chrome Remote. It works well and opens the Chrome remote control on my Windows, although it is quite slow, but it works. However, it throws some GPU and OpenGL errors that I can not solve. I have reported and are quite frequent errors, as recommended, I reinstalled the mesa-utils and libgl1-glx-mesa packages, and errors persist. Attached capture of these. I have installed (bionic): libgl1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglib2.0-0 libglib2.0-data libglvnd0 liglx-mesa0 libglx0 dbus dbus-x11 I have searched for help in the stackoverflow forums without any success. OpenGL Propierties: ~$ glxinfo | grep "OpenGL versión" libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast X Error of failed request: GLXBadContext Major opcode of failed request: 148 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 46 Current serial number in output stream: 45 And the characteristics of the graphics of my VPS: ~ $ lspci -vk 00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine Physical Slot: 2 Flags: fast devsel, IRQ 10 Memory at f800 (32-bit, non-prefetchable) [size = 64M] Memory at fc00 (32-bit, non-prefetchable) [size = 16M] Memory at fd05 (32-bit, non-prefetchable) [size = 8K] I / O ports at c0a0 [size = 32] Expansion ROM at 000c [disabled] [size = 128K] ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Attachment added: "errores-libgl.jpg" https://bugs.launchpad.net/bugs/1835459/+attachment/5275114/+files/errores-libgl.jpg -- 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/1835459 Title: libgl1-mesa-glx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835459/+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 1835122] Re: gl_surface_glx errors
** Description changed: - I have a VPS with Ubuntu 18.04 (pure software implementation, Digital - Ocean) and I connect through Windows 10 with an X server, Xming, and I - run google-chrome remote. It works well and opens the chrome remote on - my Windows, although quite slow, but it works. However, it throws some - GPU and OpenGL errors that I can not solve. I have reported and are - quite frequent errors, as recommended I have reinstalled the mesa-utils - and libgl1-glx-mesa packages, and errors persist. Attached capture of - these. + Tengo un VPS con Ubuntu 18.04 (implementación de software puro, Digital + Ocean) y me conecto a través de Windows 10 con un servidor X, Xming y + ejecuto Google-Chrome Remote. Funciona bien y abre el control remoto de + Chrome en mi Windows, aunque es bastante lento, pero funciona. Sin + embargo, arroja algunos errores de GPU y OpenGL que no puedo resolver. + He informado y son errores bastante frecuentes, tal como me + recomendaron, reinstalé los paquetes mesa-utils y libgl1-glx-mesa, y los + errores persisten. Se adjunta captura de estos. - I have installed (bionic): - libgl1 - libgl1-mesa-dri - libgl1-mesa-glx - libglapi-mesa - libglib2.0-0 - libglib2.0-data - libglvnd0 - liglx-mesa0 + He instalado (bionic): + libgl1 + libgl1-mesa-dri + libgl1-mesa-glx + libglapi-mesa + libglib2.0-0 + libglib2.0-data + libglvnd0 + liglx-mesa0 libglx0 - dbus + dbus dbus-x11 - I have searched for help in the stackoverflow forums without any - success. + He buscado ayuda en los foros de stackoverflow sin ningún éxito. + + OpenGL Propierties: + ~$ glxinfo | grep "OpenGL versión" + + libGL error: No matching fbConfigs or visuals found + libGL error: failed to load driver: swrast + X Error of failed request: GLXBadContext + Major opcode of failed request: 148 (GLX) + Minor opcode of failed request: 6 (X_GLXIsDirect) + Serial number of failed request: 46 + Current serial number in output stream: 45 + + And the characteristics of the graphics of my VPS: + + ~ $ lspci -vk + + 00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) (prog-if 00 [VGA controller]) + Subsystem: Red Hat, Inc. QEMU Virtual Machine + Physical Slot: 2 + Flags: fast devsel, IRQ 10 + Memory at f800 (32-bit, non-prefetchable) [size = 64M] + Memory at fc00 (32-bit, non-prefetchable) [size = 16M] + Memory at fd05 (32-bit, non-prefetchable) [size = 8K] + I / O ports at c0a0 [size = 32] + Expansion ROM at 000c [disabled] [size = 128K] ** Description changed: Tengo un VPS con Ubuntu 18.04 (implementación de software puro, Digital Ocean) y me conecto a través de Windows 10 con un servidor X, Xming y ejecuto Google-Chrome Remote. Funciona bien y abre el control remoto de Chrome en mi Windows, aunque es bastante lento, pero funciona. Sin embargo, arroja algunos errores de GPU y OpenGL que no puedo resolver. He informado y son errores bastante frecuentes, tal como me recomendaron, reinstalé los paquetes mesa-utils y libgl1-glx-mesa, y los errores persisten. Se adjunta captura de estos. - He instalado (bionic): - libgl1 - libgl1-mesa-dri - libgl1-mesa-glx - libglapi-mesa - libglib2.0-0 - libglib2.0-data - libglvnd0 - liglx-mesa0 + He instalado (bionic): + libgl1 + libgl1-mesa-dri + libgl1-mesa-glx + libglapi-mesa + libglib2.0-0 + libglib2.0-data + libglvnd0 + liglx-mesa0 libglx0 - dbus + dbus dbus-x11 - He buscado ayuda en los foros de stackoverflow sin ningún éxito. + I have searched for help in the stackoverflow forums without any + success. OpenGL Propierties: ~$ glxinfo | grep "OpenGL versión" libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast X Error of failed request: GLXBadContext - Major opcode of failed request: 148 (GLX) - Minor opcode of failed request: 6 (X_GLXIsDirect) - Serial number of failed request: 46 - Current serial number in output stream: 45 + Major opcode of failed request: 148 (GLX) + Minor opcode of failed request: 6 (X_GLXIsDirect) + Serial number of failed request: 46 + Current serial number in output stream: 45 And the characteristics of the graphics of my VPS: ~ $ lspci -vk 00: 02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine Physical Slot: 2 Flags: fast devsel, IRQ 10 Memory at f800 (32-bit, non-prefetchable) [size = 64M] Memory at fc00 (32-bit, non-prefetchable) [size = 16M] Memory at fd05 (32-bit, non-prefetchable) [size = 8K] I / O ports at c0a0 [size = 32] Expansion ROM at 000c [disabled] [size = 128K] ** Description changed: - Tengo un VPS con Ubuntu 18.04 (implementación de software puro, Digital - Ocean) y me conecto a través de Windows 10 con un
[Ubuntu-x-swat] [Bug 1835122] [NEW] gl_surface_glx errors
Public bug reported: I have a VPS with Ubuntu 18.04 (pure software implementation, Digital Ocean) and I connect through Windows 10 with an X server, Xming, and I run google-chrome remote. It works well and opens the chrome remote on my Windows, although quite slow, but it works. However, it throws some GPU and OpenGL errors that I can not solve. I have reported and are quite frequent errors, as recommended I have reinstalled the mesa-utils and libgl1-glx-mesa packages, and errors persist. Attached capture of these. I have installed (bionic): libgl1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglib2.0-0 libglib2.0-data libglvnd0 liglx-mesa0 libglx0 dbus dbus-x11 I have searched for help in the stackoverflow forums without any success. ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: x11 -- 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/1835122 Title: gl_surface_glx errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1835122/+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 1825348] Re: [19.04 FEAT] LLVM 8 optimizations
In a side conversation I was told that LLVM 8.0.0 is sufficient for now. Hence the headline was changed to 19.04 and I'm going to close it as Fix Released. ** Changed in: llvm-toolchain-8 (Ubuntu) Status: Incomplete => Fix Released ** Changed in: ubuntu-z-systems Status: Incomplete => Fix Released ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-8 in Ubuntu. https://bugs.launchpad.net/bugs/1825348 Title: [19.04 FEAT] LLVM 8 optimizations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1825348/+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 1793689] Re: package libgles1 (not installed) failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', que está también en el paquete nvi
frank@dell2:~$ sudo apt-get clean frank@dell2:~$ sudo apt-get update OK:1 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu bionic InRelease OK:2 http://de.archive.ubuntu.com/ubuntu bionic InRelease OK:3 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease OK:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease OK:5 http://ppa.launchpad.net/fengestad/stable/ubuntu bionic InRelease OK:6 http://de.archive.ubuntu.com/ubuntu bionic-security InRelease OK:7 http://archive.canonical.com/ubuntu bionic InRelease OK:8 https://dl.winehq.org/wine-builds/ubuntu bionic InRelease OK:9 http://ppa.launchpad.net/libreoffice/ppa/ubuntu bionic InRelease OK:10 http://ppa.launchpad.net/videolan/master-daily/ubuntu bionic InRelease Paketlisten werden gelesen... Fertig frank@dell2:~$ sudo apt-get upgrade Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Probieren Sie »apt --fix-broken install«, um dies zu korrigieren. Die folgenden Pakete haben unerfüllte Abhängigkeiten: libglvnd-dev : Hängt ab von: libglvnd0 (= 1.0.0-2ubuntu2.1) aber 1.0.0-2ubuntu2.2 ist installiert Hängt ab von: libglvnd-core-dev (= 1.0.0-2ubuntu2.1) aber 1.0.0-2ubuntu2.2 ist installiert Hängt ab von: libegl1 (= 1.0.0-2ubuntu2.1) aber 1.0.0-2ubuntu2.2 ist installiert Hängt ab von: libgles2 (= 1.0.0-2ubuntu2.1) aber 1.0.0-2ubuntu2.2 ist installiert Hängt ab von: libgl1 (= 1.0.0-2ubuntu2.1) aber 1.0.0-2ubuntu2.2 ist installiert Hängt ab von: libglx0 (= 1.0.0-2ubuntu2.1) aber 1.0.0-2ubuntu2.2 ist installiert Hängt ab von: libopengl0 (= 1.0.0-2ubuntu2.1) aber 1.0.0-2ubuntu2.2 ist installiert E: Unerfüllte Abhängigkeiten. Versuchen Sie »apt --fix-broken install« ohne Angabe eines Pakets (oder geben Sie eine Lösung an). frank@dell2:~$ sudo apt --fix-broken install Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Abhängigkeiten werden korrigiert ... Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: libreoffice-style-galaxy libxmlsec1 libxmlsec1-nss Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden zusätzlichen Pakete werden installiert: libgles1 libglvnd-dev Die folgenden NEUEN Pakete werden installiert: libgles1 Die folgenden Pakete werden aktualisiert (Upgrade): libglvnd-dev 1 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen 14,6 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 66,6 kB Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] j Holen:1 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Holen:2 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3.408 B] Es wurden 14,6 kB in 0 s geholt (138 kB/s). (Lese Datenbank ... 303462 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Entpacken von libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1« zu überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist Vorbereitung zum Entpacken von .../libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Entpacken von libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) über (1.0.0-2ubuntu2.1) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): Versuch, »/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so« zu überschreiben, welches auch in Paket nvidia-340 340.106-0ubuntu3 ist Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Description changed: Messages shown when I execute apt upgrade (Leyendo la base de datos ... 603320 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Desempaquetando libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) sobre (1.0.0-2ubuntu2.1) ... dpkg: error al procesar el archivo /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): - intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', que está también en el paquete nvidia-340 340.106-0ubuntu3 + intentando
[Ubuntu-x-swat] [Bug 1792651] [NEW] xWayland & gnome-shell segfaults in Wayland when display is turned off while Kodi running
Public bug reported: I have been trying to report this problem through bug 1789962, but with little luck (.crash files were not uploaded). Now I tried reporting against xwayland instead of gnome-shell. I also installed more .dbg packages for xwayland, wayland, kodi and gnome-shell. So far, it looks like the crash data was not uploaded for this bug either. I don't see it at https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4. Sigh I have opened a bug against apport to report it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 14 17:54:39 2018 DistUpgraded: 2018-08-20 21:14:31,129 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: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0412] InstallationDate: Installed on 2012-12-31 (2082 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu-root ro nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-08-21 (24 days ago) dmi.bios.date: 10/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: Z97M OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd10/13/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97MOCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu wayland-session -- 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/1792651 Title: xWayland & gnome-shell segfaults in Wayland when display is turned off while Kodi running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1792651/+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 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04
Sure, no problem. Separate bug for 16.04 created: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1773581 -- 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/1771204 Title: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+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 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04
I am seeing the exact same problem on a Samsung NP900X3G after the most recent kernel update for Ubuntu 16.04. It works fine on 4.13.0-41 but with 4.13.0-43 I am seeing the same horizontal lines as Thomas. Maybe this helps to find where the problem got introduced. -- 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/1771204 Title: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+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 1770092] [NEW] error
Public bug reported: when I downloading apps some errors and when working OS working so slowy ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 9 15:43:57 2018 DistUpgraded: 2018-05-02 06:58:57,163 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd GF119M [GeForce 610M] [144d:c652] InstallationDate: Installed on 2017-01-31 (462 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e8f1d7ee-2740-4158-977c-6250f43f5995 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-01 (7 days ago) dmi.bios.date: 02/20/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07RAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP07RAC:bd02/20/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4C/300E5C/300E7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 300E4C/300E5C/300E7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Apr 10 08:59:09 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5539 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1770092 Title: error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770092/+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 1507676] Re: Nvidia-Prime not switching from intel to nvidia leading to a black screen
What I find _**DEEPLY**_ disturbing is that this bug has been lurking for roughly two plus years with absolutely _**NO**_ resolution whatsoever. Guys...you're a business and even if it's the "community" working on it, that business is bankrolling the resources you lot are using. If you hadn't figured it out...this rates one of Linus' trademarked vitriolic profanity laced rants. I'd do it, but I'm going to behave and try to figure out how to FIX this instead of "fix" it like you'd fix a dog or cat. -- 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/1507676 Title: Nvidia-Prime not switching from intel to nvidia leading to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1507676/+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 1706936] Re: Wrong version of libgles1-mesa in Xenial-updates
After uninstalling the original NVIDIA-Linux-x86_64-378.13 driver and replacing it with nvidia-graphics-drivers-384.59 from repository ppa :graphics-drivers the problem with Blender is solved for me. Initially I had to use original Nvidia driver because at this time there wasn't a suitable driver for the GTX 1080TI graphic card in the repositories. -- 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/1706936 Title: Wrong version of libgles1-mesa in Xenial-updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1706936/+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 1706936] Re: Wrong version of libgles1-mesa in Xenial-updates
This mesa update brings me seriousley into trouble because I seems to me that the now missing libgles1-mesa runs Blender into an error at program start! framercy@helios ~/bin/blender-2.78c-linux-glibc219-x86_64 $ ./blender Read new prefs: /home/framercy/.config/blender/2.78/config/userpref.blend Received X11 Error: error code: 3 request code: 155 minor code: 4 error text: BadWindow (invalid Window parameter) Error! Blender requires OpenGL 2.1 to run. Try updating your drivers. framercy@helios ~/bin/blender-2.78c-linux-glibc219-x86_64 $ glxinfo name of display: :0.0 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 155 (NV-GLX) Minor opcode of failed request: 4 () Resource id in failed request: 0x523 Serial number of failed request: 37 Current serial number in output stream: 37 I use Linux Mint 18.1 Mate 64bit and all things worked fine until the mesa update! I make my money with Blender so a fast solution would be very nice. THX -- 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/1706936 Title: Wrong version of libgles1-mesa in Xenial-updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1706936/+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 1497585] Re: errors
On 09/19/2015 08:54 PM, Christopher M. Penalver wrote: > Frank, the word error found in dmesg in itself doesn't constitute a bug, nor > necessitate a report here on Launchpad. For more on dmesg, please see via a > terminal: > man dmesg > > If you actually have a functionality problem (ex. suspend doesn't work, > a program crashes, etc.) then please file a new report. > > ** Changed in: xorg (Ubuntu) >Status: New => Invalid > Mr Penalver, Sorry I made an invalid bug report but I am new to Linux and when a dialog box came up and said " File A Bug Report " I thought why not maybe it will help. Chalk it up to my lack of experience with Linux. Thank You for your time -- 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/1497585 Title: errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1497585/+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 1497585] [NEW] errors
Public bug reported: getting many errors in dmesg ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6 Uname: Linux 3.19.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 19 12:00:21 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: alsa-hda, 0.201210261053~natty1: added GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:107b] InstallationDate: Installed on 2014-05-18 (489 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: ASUSTeK COMPUTER INC. Q500A PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-29-generic.efi.signed root=UUID=9ef830c6-0948-429e-9553-d0dbf51949b1 ro plymouth:debug splash quiet drm.debug=0xe acpi=on SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q500A.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q500A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ500A.208:bd11/14/2012:svnASUSTeKCOMPUTERINC.:pnQ500A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ500A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: Q500A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Sep 19 10:08:49 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.17.1-0ubuntu3.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- 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/1497585 Title: errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1497585/+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 1486240] [NEW] fglrx-updates-core failed during softwear updater 08/18/2015
Public bug reported: Was updating the fglrx-updates-core and firmware though software updater and failed to install. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-updates-core 2:15.200-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 DKMSKernelVersion: 3.19.0-26-generic Date: Tue Aug 18 13:25:14 2015 InstallationDate: Installed on 2015-05-05 (104 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) PackageVersion: 2:15.200-0ubuntu4 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: fglrx-installer-updates Title: fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- 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/1486240 Title: fglrx-updates-core failed during softwear updater 08/18/2015 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1486240/+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 1451723] [NEW] Ubuntu 14.04 crush to login screen
Public bug reported: This is turning to happen quite a lot lately, every time I login to and say click on Firefox, after say a few minutes browsing, Firefox freezes then the system crashes and throws me back to login screen.. If I log in again it does the same. Have to shut off computer and unplug leaving it for a few minutes before switching it back on with fingers crossed that it wont crash immediately. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-36-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.125 Mon Dec 1 19:55:52 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 5 09:49:35 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.125, 3.16.0-31-generic, i686: installed nvidia-304, 304.125, 3.16.0-33-generic, i686: installed nvidia-304, 304.125, 3.16.0-34-generic, i686: installed nvidia-304, 304.125, 3.16.0-36-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0370] InstallationDate: Installed on 2015-03-17 (48 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1) MachineType: Dell Inc. Dell DXP051 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic root=UUID=0c61d87e-ac8a-4b5a-9506-502e4287158b ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0FJ030 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0FJ030:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell DXP051 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 5 09:30:35 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt USB Optical Mouse MOUSE, id 8 inputDELL DELL USB Keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty 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/1451723 Title: Ubuntu 14.04 crush to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1451723/+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 1404869] [NEW] Bei HDMI-Anschluss Black Screen
Public bug reported: Seit dem Update auf Kernelversion 3.13.0-43.generic gibt es beim Anschluss eines HDMI-Gerätes immer einen Black Screen, das angeschlossene Gerät zeigt keine Signal an und der Rechner lässt sich nicht mehr bedienen. Auch das Abstecken des HDMI-Kabels bringt keine Änderung, der Bildschirm bleibt schwarz und es hilft nur ein Neustart. Dieser Fehler ist auch nach dem letzten X-Server Update immer noch vorhanden. Es ist nicht möglich, eine HDMI-Gerät anzuschließen. Beim Booten mit dem Kernel 3.13.0-40 funktioniert alles ohne Störung. Since the update to kernel version 3.13.0-43.generic there when connecting an HDMI device always has a black screen, the connected device does not show any signal and the computer can no longer operate. Also disconnecting the HDMI cable makes no changes, the screen stays black and it only helps a restart. This error is also after the last X server upgrade is still available. It is not possible to connect a HDMI device. When booting the kernel 3.13.0-40 everything works without error. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,mousepoll,place,move,grid,imgpng,session,gnomecompat,regex,unitymtgrabhandles,resize,snap,animation,expo,workarounds,fade,scale,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 22 13:12:14 2014 DistUpgraded: 2014-08-17 13:55:01,175 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21ec] InstallationDate: Installed on 2013-08-26 (483 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 002 Device 002: ID 04f2:b2b9 Chicony Electronics Co., Ltd Lenovo Integrated Camera UVC Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO 305167G ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=59a5a1e8-d741-4b6f-8bb6-4b53f9820aed ro quiet splash acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-08-17 (127 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8RET54WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 305167G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8RET54WW(1.17):bd10/24/2012:svnLENOVO:pn305167G:pvrThinkPadX121e:rvnLENOVO:rn305167G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 305167G dmi.product.version: ThinkPad X121e dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 22 12:37:24 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.6 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1404869 Title: Bei HDMI-Anschluss Black Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1404869/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to :
[Ubuntu-x-swat] [Bug 1402360] [NEW] Keine Hdmi- Anschluss mehr möglich/No HDMI connection possible
Public bug reported: Seit dem Update auf Kernel 3.13.0-43 generic kann ich kein Hdmi-Gerät mehr anschließen. Wenn ich das Kabel einstecke, wird das Display schwarz, am Gerät kommt keine Signal an und ich kann auf meinen Rechner nicht mehr zugreifen. Weder abziehen des Kabels noch Fn+F7 noch irgendeine andere Tastenkombinatione helfen etwas, nur ein Neustart bringt eine Lösung. Wenn ich über GRUB mit dem vorherigen Kernel starte (3.13.0.-40 generic) funktioniert alles normal. Freundliche Grüße Frank Boßmann After updating to kernel 3.13.0-43 generic I can not connect a hdmi device more. When I plug in the cable, the screen goes black, the device comes at no signal and I can not access my computer. Neither pull the cable still Fn + F7 keys nor any other combinations will help a little, just restart brings a solution. When I start over GRUB with the previous kernel (3.13.0.-40 generic) everything works normally. Best Regards Frank Boßmann ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,mousepoll,place,move,grid,imgpng,session,gnomecompat,regex,unitymtgrabhandles,resize,snap,animation,expo,workarounds,fade,scale,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Dec 14 11:06:45 2014 DistUpgraded: 2014-08-17 13:55:01,175 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21ec] InstallationDate: Installed on 2013-08-26 (474 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 002 Device 002: ID 04f2:b2b9 Chicony Electronics Co., Ltd Lenovo Integrated Camera UVC Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO 305167G ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=59a5a1e8-d741-4b6f-8bb6-4b53f9820aed ro quiet splash acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-08-17 (118 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8RET54WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 305167G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8RET54WW(1.17):bd10/24/2012:svnLENOVO:pn305167G:pvrThinkPadX121e:rvnLENOVO:rn305167G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 305167G dmi.product.version: ThinkPad X121e dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Dec 14 10:37:27 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.5 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1402360 Title: Keine Hdmi- Anschluss mehr möglich/No HDMI connection possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1402360/+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
[Ubuntu-x-swat] [Bug 1140716]
Hi Chris, meanwhile my current kernel is 3.16.1-46.1.g90bc0f1 I'm wondering (after a reinstall) that the semaphore bug hasn't occured yet, which was the case before (after a fresh install). This leads me to 4 definable possible reasons: 1. the named kernel revision somehow contains a fix for it. looking at the changes I could'nt get an affirmation to that assumption. 2. cgroup_memory=disabled has a relation to it. (That's why I removed it for now). 3. the BIOS settings (which could be different now) might have something to do with it. 4. I haven't installed KVM suppport yet. I'll post again if I find a reproducible explanation. Frank -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+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 1140716]
2. of course I meant cgroup_disable=memory -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+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 1140716]
Hi Chris, OK, nothing of the above was the reason. In my case it's simply this: /etc/X11/xorg.conf.d/20-intel.conf Section Device Identifier Intel Graphics Driver intel Option TearFreetrue EndSection I added it when the tearing scrolling through large webpages annoyed me. As soon as I added it, the problems quickly started. Selfmade problem. Frank -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+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 1041790]
Hi Chris, meanwhile my current kernel is 3.16.1-46.1.g90bc0f1 I'm wondering (after a reinstall) that the semaphore bug hasn't occured yet, which was the case before (after a fresh install). This leads me to 4 definable possible reasons: 1. the named kernel revision somehow contains a fix for it. looking at the changes I could'nt get an affirmation to that assumption. 2. cgroup_memory=disabled has a relation to it. (That's why I removed it for now). 3. the BIOS settings (which could be different now) might have something to do with it. 4. I haven't installed KVM suppport yet. I'll post again if I find a reproducible explanation. Frank -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1041790]
2. of course I meant cgroup_disable=memory -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1041790]
Hi Chris, OK, nothing of the above was the reason. In my case it's simply this: /etc/X11/xorg.conf.d/20-intel.conf Section Device Identifier Intel Graphics Driver intel Option TearFreetrue EndSection I added it when the tearing scrolling through large webpages annoyed me. As soon as I added it, the problems quickly started. Selfmade problem. Frank -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1353640] [NEW] x11vnc segfaults
Public bug reported: x11-vnc segfaults: /usr/bin/x11vnc -rfbport 5900 -rfbauth ~/.vnc/x11vnc.pass -o ~/.vnc/x11vnc.log -display :0 [1]22772 segmentation fault (core dumped) /usr/bin/x11vnc -rfbport 5900 -rfbauth ~/.vnc/x11vnc.pass -o ~/.vnc/x11vnc.lo I'm using ubuntu trusty with the latest updates. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1353640 Title: x11vnc segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1353640/+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 296122] Re: XNEST crashes in X_PolyFillRectangle with error config/hal: NewInputDeviceRequest failed
I get the same using Ubuntu 13.10 and running Flwm over Xnest: X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 70 (X_PolyFillRectangle) Resource id in failed request: 0x0 Serial number of failed request: 4751 Current serial number in output stream: 4755 X I/O error xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server :1 -- 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/296122 Title: XNEST crashes in X_PolyFillRectangle with error config/hal: NewInputDeviceRequest failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/296122/+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 662933] Re: keyboard mapping mixed up upon pressing NumLock
Workaround: Disable NumLock 1. For Disabling it on Login Screen 2. Workaround for Unity-Session 1. For Disabling it on Login Screen === First, ensure that numlockx is installed, by typing these in terminal: sudo apt-get install numlockx Then, edit the file /etc/lightdm/lightdm.conf gksudo gedit /etc/lightdm/lightdm.conf Add the following line to the file: greeter-setup-script=/usr/bin/numlockx off 2. Workaround for Unity-Session = Click on the cog wheel on the top right corner of your screen and choose Startup Applications, or type Startup... in the Dash. Add command /usr/bin/numlockx off as startup application. -- 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/662933 Title: keyboard mapping mixed up upon pressing NumLock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/662933/+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]
Problem was solved for me some time ago. Surely it does not happen with the Linux kernel 3.11 on Ubuntu 13.10. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Confirmed = Fix Released -- 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
[Ubuntu-x-swat] [Bug 993187] Re: ubuntu 12.04 completely freezes frequently.
I think this bug is assigned to the wrong package. It is very likely a kernel problem. On my hardware, the kernel actually detects the lock. I posted extracts from the syslog file recovered after a hard reset in the following two posts to another thread on the same problem: a href=https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154006/comments/42;1154006#42/a and a href=https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154006/comments/46;1154006#46/a. The lines to look for are Apr 10 18:58:51 ceylon kernel: [ 2412.456005] ioatdma :00:08.0: reset Apr 10 18:58:52 ceylon kernel: [ 2412.603756] BUG: soft lockup - CPU#3 stuck for 22s! [svn:5127] in #42 and Apr 14 13:16:12 ceylon kernel: [18557.572005] ioatdma :00:08.0: reset Apr 14 13:16:12 ceylon kernel: [18557.772001] INFO: rcu_sched detected stall on CPU 1 (t=15000 jiffies) Apr 14 13:16:12 ceylon kernel: [18557.772002] sending NMI to all CPUs: in #46. I just went back to 10.04, the instability of 12.04 is just ridiculous. I hope that a kernel developer is following this discussion and might find a hint in the syslog extracts I posted under the other number. -- 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/993187 Title: ubuntu 12.04 completely freezes frequently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+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]
I see the same issue on Raring (13.04) with kernel 3.8.x . -- 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
[Ubuntu-x-swat] [Bug 1103110] [NEW] supertuxkart crashes with SEGFAULT
Public bug reported: I tried to start supertuxkart and it failed with a sgementation fault. It seems to be different than the one mentioned in the other currently open bug, so I decided to report my own. haver@grobi:~$ supertuxkart Irrlicht Engine version 1.7.2 Linux 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 [FileManager] Data files will be fetched from: '/usr/share/games/supertuxkart/' [IrrDriver] Creating NULL device Irrlicht Engine version 1.7.2 Linux 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 [IrrDriver] Trying OpenGL rendering. [IrrDriver] Tring to create device with 32 bits [IrrDriver Temp Logger] Level 1: No doublebuffering available. [IrrDriver Temp Logger] Level 2: Fatal error, could not get visual. Speicherzugriffsfehler (Speicherabzug geschrieben) haver@grobi:~$ Installation is in German, that is why the error messages are localized. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Attachment added: strace output https://bugs.launchpad.net/bugs/1103110/+attachment/3495093/+files/supertuxkart.strace -- 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/1103110 Title: supertuxkart crashes with SEGFAULT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1103110/+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 1103110] Re: supertuxkart crashes with SEGFAULT
haver@grobi:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise ** Attachment added: core dump after setting ulimits to unlimited for core dump files. https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1103110/+attachment/3495097/+files/core -- 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/1103110 Title: supertuxkart crashes with SEGFAULT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1103110/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
I finally found a solution/workaround (I can't believe it)!!! A thread on the nvnews forums discussed a similar problem. One comment suggested setting the option NoExtendedGpuCapabilitiesCheck in xorg.conf to disable mode validation (http://www.nvnews.net/vbulletin/showpost.php?p=2039336postcount=11). I can now use both monitors at full/native resolution :) -- 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/727112 Title: nvidia-current does not detect hardware capabilities correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/727112/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
I tested my graphics card with another external monitor (a Dell 2408WFP) which runs with a native resolution of 1920x1200. Using that monitor does not exhibit the bug and the driver/graphics card is able to run two monitors simultaneously at 1920x1200 (total resolution: 3840x1200). This shows me, that such a high resolution is definitely supported by my hardware (and by the nvidia-current driver?). But I'm still lost … why does one monitor work and another one with lower resolution does not? My current guess is different frequencies trip up the driver. Is there anybody out there with the slightest clue how to properly troubleshoot this problem? Interestingly, the Dell monitor does not show EDID data when queried with xrandr. Output of xrandr --verbose --query can be found below: Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 8192 x 8192 VGA-0 connected 1920x1200+1920+0 (0x2c8) normal (normal left inverted right x axis y axis) 519mm x 324mm Identifier: 0x278 Timestamp: 217095 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 1 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: SignalFormat: VGA supported: VGA ConnectorType: VGA ConnectorNumber: 1 (0x0001) _ConnectorLocation: 1 (0x0001) 1920x1200 (0x2c8) 154.0MHz +HSync -VSync *current +preferred h: width 1920 start 1968 end 2000 total 2080 skew0 clock 74.0KHz v: height 1200 start 1203 end 1209 total 1235 clock 60.0Hz 1600x1200 (0x2c9) 162.0MHz +HSync +VSync h: width 1600 start 1664 end 1856 total 2160 skew0 clock 75.0KHz v: height 1200 start 1201 end 1204 total 1250 clock 60.0Hz 1280x1024 (0x2ca) 135.0MHz +HSync +VSync h: width 1280 start 1296 end 1440 total 1688 skew0 clock 80.0KHz v: height 1024 start 1025 end 1028 total 1066 clock 75.0Hz 1280x1024 (0x2cb) 108.0MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 64.0KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz 1152x864 (0x2cc) 108.0MHz +HSync +VSync h: width 1152 start 1216 end 1344 total 1600 skew0 clock 67.5KHz v: height 864 start 865 end 868 total 900 clock 75.0Hz 1024x768 (0x2cd) 78.8MHz +HSync +VSync h: width 1024 start 1040 end 1136 total 1312 skew0 clock 60.0KHz v: height 768 start 769 end 772 total 800 clock 75.0Hz 1024x768 (0x279) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x2ce) 49.5MHz +HSync +VSync h: width 800 start 816 end 896 total 1056 skew0 clock 46.9KHz v: height 600 start 601 end 604 total 625 clock 75.0Hz 800x600 (0x27e) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 640x480 (0x2cf) 31.5MHz -HSync -VSync h: width 640 start 656 end 720 total 840 skew0 clock 37.5KHz v: height 480 start 481 end 484 total 500 clock 75.0Hz 640x480 (0x282) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz TV-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x286 Timestamp: 217095 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: SignalFormat: unknown supported: unknown ConnectorType: TV ConnectorNumber: 3 (0x0003) _ConnectorLocation: 3 (0x0003) LVDS-0 connected 1920x1200+0+0 (0x288) normal (normal left inverted right x axis y axis) 331mm x 207mm Identifier: 0x287 Timestamp: 217095 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004ca35532 00120103802115780a87f594574f8c27 2750540001010101010101010101 0101010101018c41805871b023406420
[Ubuntu-x-swat] [Bug 1079801] Re: applications like Google Earth or Second Life do not work
It _seems_ to be a hardware related bug. Either the harddisk or the disk controller which causes these mysterious problems. -- 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/1079801 Title: applications like Google Earth or Second Life do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1079801] Re: applications like Google Earth or Second Life do not work
I forgot to add, that I was unable to test install Ubuntu 13.04 with the CD burned from 17.11.2012 and not with one from 08.01.2013. They either freeze before or directly after the selection screen regarding the prerequisites. -- 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/1079801 Title: applications like Google Earth or Second Life do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1079801] Re: mysterious application behaviour for the intel sandy bridge hardware
Okay, sorry, but the mysterious application behaviour was due to a broken harddisk. And since I decided to stop using Google Earth and Second Life we can close the bug report as resolved. ** Summary changed: - mysterious application behaviour for the intel sandy bridge hardware + RESOLVED: mysterious application behaviour for the intel sandy bridge hardware -- 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/1079801 Title: RESOLVED: mysterious application behaviour for the intel sandy bridge hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1079801] Re: RESOLVED: applications like Google Earth or Second Life do not work
** Summary changed: - RESOLVED: mysterious application behaviour for the intel sandy bridge hardware + RESOLVED: applications like Google Earth or Second Life do not work -- 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/1079801 Title: RESOLVED: applications like Google Earth or Second Life do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1079801] Re: RESOLVED: applications like Google Earth or Second Life do not work
Sorry again, I decided to keep the bug open until it is resolved properly. ** Summary changed: - RESOLVED: applications like Google Earth or Second Life do not work + applications like Google Earth or Second Life do not work -- 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/1079801 Title: applications like Google Earth or Second Life do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1079801] Re: Second Life Google Earth do not load for the intel sandy bridge gfx chip
You load youtube and before it finishes the browser freezes. Then you type something into the search bar and the browser freezes again. You visit other websites with javascript interaction and the browser freezes. This happens also when you click the star symbol in the browser to bookmark or when you try to switch tabs. But this is not a browser problem!! The behaviour changed with the dist-upgrade when new mesa and compiz packages arrived. I made sure there really was no code change of the browser. Additionally, the screen snapshotting tool crashed during the file save option when I had the spotify client launched. All in all totally unacceptable for updates to break my system like this. Sad that I can not just switch operating systems like people advise me ** Summary changed: - Second Life Google Earth do not load for the intel sandy bridge gfx chip + mysterious application behaviour for the intel sandy bridge hardware -- 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/1079801 Title: mysterious application behaviour for the intel sandy bridge hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1079801] Re: mysterious application behaviour for the intel sandy bridge hardware
Libre Office shows the same behaviour than Firefox with constant freezes. -- 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/1079801 Title: mysterious application behaviour for the intel sandy bridge hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 1079801] Re: Second Life Google Earth do not load for the intel sandy bridge gfx chip
The graphics driver for the Intel Integrated Graphics Chip seems to have more issues: Since the dist-upgrade of today my applications freeze when they try to open images (screenshot e.g.) or when I browse the web (Youtube, etc.) but also when I enter text in search boxes. And for a weird reason the bug tracker will not allow me to open new bugs. -- 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/1079801 Title: Second Life Google Earth do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1079801/+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 727112] Re: nvidia-current does not detect hardware capabilities correctly
I just performed further tests with a system booted from an USB drive. The bug happens regardless of architecture, both amd64 and i386 are affected. With the nouveau driver I managed to run both monitors with native resolution, but the external monitor showed graphic errors (see the attached screenshot). Also, the system was feeling very sluggish with two monitors. xrandr --query --verbose when using the nouveau driver outputs: Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192 LVDS-1 connected 1920x1200+0+0 (0x65) normal (normal left inverted right x axis y axis) 331mm x 207mm Identifier: 0x61 Timestamp: 27086 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004ca35532 00120103802115780a87f594574f8c27 2750540001010101010101010101 0101010101018c41805871b023406420 26004bcf1019000f 0046d20264fe0059 323834470031353455320a2000fe 0017272f3f5f97afff02010a20200039 dithering depth:auto supported: auto 6 bpc8 bpc dithering mode: auto supported: auto off static 2x2 dynamic 2x2 scaling mode: Full supported: None Full Center Full aspect color vibrance: 150 (0x0096)range: (0,200) vibrant hue: 90 (0x005a)range: (0,180) 1920x1200 (0x65) 167.8MHz -HSync -VSync *current +preferred h: width 1920 start 2020 end 2052 total 2264 skew0 clock 74.1KHz v: height 1200 start 1202 end 1208 total 1235 clock 60.0Hz 1920x1200 (0x66) 193.2MHz -HSync +VSync h: width 1920 start 2056 end 2256 total 2592 skew0 clock 74.6KHz v: height 1200 start 1203 end 1209 total 1245 clock 59.9Hz 1920x1080 (0x67) 173.0MHz -HSync +VSync h: width 1920 start 2048 end 2248 total 2576 skew0 clock 67.2KHz v: height 1080 start 1083 end 1088 total 1120 clock 60.0Hz 1600x1200 (0x68) 161.0MHz -HSync +VSync h: width 1600 start 1712 end 1880 total 2160 skew0 clock 74.5KHz v: height 1200 start 1203 end 1207 total 1245 clock 59.9Hz 1680x1050 (0x69) 146.2MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew0 clock 65.3KHz v: height 1050 start 1053 end 1059 total 1089 clock 60.0Hz 1400x1050 (0x6a) 121.8MHz -HSync +VSync h: width 1400 start 1488 end 1632 total 1864 skew0 clock 65.3KHz v: height 1050 start 1053 end 1057 total 1089 clock 60.0Hz 1280x1024 (0x6b) 109.0MHz -HSync +VSync h: width 1280 start 1368 end 1496 total 1712 skew0 clock 63.7KHz v: height 1024 start 1027 end 1034 total 1063 clock 59.9Hz 1280x960 (0x6c) 101.2MHz -HSync +VSync h: width 1280 start 1360 end 1488 total 1696 skew0 clock 59.7KHz v: height 960 start 963 end 967 total 996 clock 59.9Hz 1152x864 (0x6d) 81.8MHz -HSync +VSync h: width 1152 start 1216 end 1336 total 1520 skew0 clock 53.8KHz v: height 864 start 867 end 871 total 897 clock 60.0Hz 1024x768 (0x6e) 63.5MHz -HSync +VSync h: width 1024 start 1072 end 1176 total 1328 skew0 clock 47.8KHz v: height 768 start 771 end 775 total 798 clock 59.9Hz 800x600 (0x6f) 38.2MHz -HSync +VSync h: width 800 start 832 end 912 total 1024 skew0 clock 37.4KHz v: height 600 start 603 end 607 total 624 clock 59.9Hz 640x480 (0x70) 23.8MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew0 clock 29.7KHz v: height 480 start 483 end 487 total 500 clock 59.4Hz 720x400 (0x71) 22.2MHz -HSync +VSync h: width 720 start 744 end 808 total 896 skew0 clock 24.8KHz v: height 400 start 403 end 413 total 417 clock 59.6Hz 640x400 (0x72) 20.0MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew0 clock 25.0KHz v: height 400 start 403 end 409 total 417 clock 60.0Hz 640x350 (0x73) 17.5MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew0 clock 21.9KHz v: height 350 start 353 end 363 total 366 clock 59.8Hz VGA-1 connected (normal left inverted right x axis y axis) Identifier: 0x62 Timestamp: 27086 Subpixel:
[Ubuntu-x-swat] [Bug 727112] Re: nvidia-current does not detect hardware capabilities correctly
I finally took the time to upgrade my Ubuntu install to the recent release 12.10 (Quantal Quetzal). This bug still occurs, and now seems worse then ever. I have skipped (i.e. not tested) the releases 11.10 and 12.04, but I assume those two releases didn't bring any improvement either. In the past, I've set my builtin monitor (laptop) to a smaller resolution (1680x1050). That way I could run the external monitor at full resolution (1920x1080 full HD) even with nvidia-current driver. Remember: both screens worked fine with full resolution with nvidia-173 (slower) as well as with nouveau (even more slow). Under Quantal, nouveau cannot handle both screens at full resolution and neither can any of the provided nvidia proprietary drivers. I tested all available options: -current, -current-updates, -experimental-304, and -experimental-310. I think nouveau managed to run both screens in mirror/clone mode, but not sure about the exact resolutions was using. What's worse, I cannot set my laptop monitor to the smaller resolution like I did in the past, since only Off, Auto, and 1920x1200 are shown in nvidia-settings as well as in 'Display' system settings (that's using randr, right?). Both monitors run, when I set my external monitor to a smaller resolution (currently 1680x1050), but that's not the native resolution and not the correct aspect ratio (16:10 vs 16:9). And if that was not bad enough, Xorg cannot even start when the external monitor is plugged in. The screen will blink several times and then dump to a black screen with a blinking white cursor. Switching to a VT, unplugging the monitor and starting X (service lightdm start) will finally bring Xorg back up. This is really annoying! (Please imagine a turned on caps lock, to get an idea of my frustration). The external monitor is connected with a VGA cable if that matters. I cannot use DVI, because my laptop only offers VGA out. Relevant details from Xorg.0.log after unsuccessfully trying to start X during boot: [97.253] (II) NVIDIA(0): NVIDIA GPU Quadro FX 360M (G86GL) at PCI:1:0:0 (GPU-0) [97.253] (--) NVIDIA(0): Memory: 524288 kBytes [97.253] (--) NVIDIA(0): VideoBIOS: 60.86.68.00.18 [97.253] (II) NVIDIA(0): Detected PCI Express Link width: 16X [97.253] (--) NVIDIA(0): Interlaced video modes are supported on this GPU [97.359] (--) NVIDIA(0): Valid display device(s) on Quadro FX 360M at PCI:1:0:0 [97.359] (--) NVIDIA(0): QMX Q24 (CRT-0) (connected) [97.359] (--) NVIDIA(0): TV-0 [97.359] (--) NVIDIA(0): Seiko/Epson (DFP-0) (connected) [97.359] (--) NVIDIA(0): DFP-1 [97.359] (--) NVIDIA(0): QMX Q24 (CRT-0): 400.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): TV-0: 400.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): TV encoder: (null) [97.359] (--) NVIDIA(0): Seiko/Epson (DFP-0): 330.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): Seiko/Epson (DFP-0): Internal Dual Link LVDS [97.359] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock [97.359] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS [97.359] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [97.359] (**) NVIDIA(0): device QMX Q24 (CRT-0) (Using EDID frequencies has been [97.359] (**) NVIDIA(0): enabled on all display devices.) [97.371] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [97.371] (**) NVIDIA(0): device Seiko/Epson (DFP-0) (Using EDID frequencies has [97.371] (**) NVIDIA(0): been enabled on all display devices.) [97.372] (==) NVIDIA(0): [97.372] (==) NVIDIA(0): No modes were requested; the default mode nvidia-auto-select [97.372] (==) NVIDIA(0): will be used as the requested mode. [97.372] (==) NVIDIA(0): [97.373] (WW) NVIDIA(0): MetaMode DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select [97.373] (WW) NVIDIA(0): exceeds hardware capabilities; discarding. [97.373] (WW) NVIDIA(0): No valid modes for [97.373] (WW) NVIDIA(0): DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select; [97.373] (WW) NVIDIA(0): removing. [97.373] (WW) NVIDIA(0): [97.373] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode [97.373] (WW) NVIDIA(0): nvidia-auto-select. [97.373] (WW) NVIDIA(0): [97.374] (WW) NVIDIA(0): MetaMode DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select [97.374] (WW) NVIDIA(0): exceeds hardware capabilities; discarding. [97.374] (WW) NVIDIA(0): No valid modes for [97.374] (WW) NVIDIA(0): DFP-0:nvidia-auto-select,CRT-0:nvidia-auto-select; [97.374] (WW) NVIDIA(0): removing. [97.374] (EE) NVIDIA(0): Unable to use default mode nvidia-auto-select. [98.397] (EE) NVIDIA(0): Failing initialization of X screen 0 [99.071] (II) UnloadModule: nvidia [99.071] (II) UnloadSubModule: wfb [99.071] (II) UnloadSubModule: fb [99.071] (EE) Screen(s)
[Ubuntu-x-swat] [Bug 727112] Re: nvidia-current does not detect hardware capabilities correctly
Tested with Quantal and the bug still occurs. See Comment #8 (https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers/+bug/727112/comments/8) -- 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/727112 Title: nvidia-current does not detect hardware capabilities correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/727112/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
-- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
-- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
** Attachment added: SecondLife-i686-3.4.1.266581 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+attachment/3438942/+files/SecondLife.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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
** Attachment added: google-earth-stable_current_i386 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+attachment/3438944/+files/crashlog-50aa7171.txt -- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
** Attachment added: GLX Info https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+attachment/3438945/+files/glxinfo.txt -- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
Other 3D applications like Blender, Red Eclipse and Super Tux Kart work as expected. -- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: Second Life Google Earth do not load for the intel sandy bridge gfx chip
** Summary changed: - 3D apps do not load for the intel sandy bridge gfx chip + Second Life Google Earth do not load for the intel sandy bridge gfx chip -- 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/1079801 Title: Second Life Google Earth do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
Ubuntu 12.10 and 13.04 are affected but not 12.04 - there at least the Second Life viewers are working. Just not Googl Earth. -- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] [NEW] 3D apps do not load for the intel sandy bridge gfx chip
Public bug reported: Neither one of the available 4 different viewers for Second Life nor Google Earth will load. They quit with the command that they fail to load i965. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Nov 16 18:51:17 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-18-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7680] InstallationDate: Installed on 2012-11-15 (1 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c062 Logitech, Inc. LS1 Laser Mouse, corded MachineType: ARLT Computer Produkte GmbH Mr. Business PRO SNB MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=634d3a5a-ca0b-4b91-9821-095392b6ca71 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P25 (MS-7680) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.4:bd02/14/2012:svnARLTComputerProdukteGmbH:pnMr.BusinessPROSNB:pvr5.0:rvnMSI:rnH61M-P25(MS-7680):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: Mr. Business PRO SNB dmi.product.version: 5.0 dmi.sys.vendor: ARLT Computer Produkte GmbH version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 quantal running-unity 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
google-earth-stable_current_i386.deb (from 2012-11-15) SecondLife-i686-3.4.1.266581 Phoenix_Firestorm-Release_i686_4.2.2.29837 Singularity-i686-1.7.2.2956 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device 7680 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at fe00 (64-bit, non-prefetchable) [size=4M] Memory at c000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 -- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 1079801] Re: 3D apps do not load for the intel sandy bridge gfx chip
The board in question is: MSI H61M-P25 (MS-7680) -- 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/1079801 Title: 3D apps do not load for the intel sandy bridge gfx chip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079801/+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 997470] Re: apport-gpu-error-intel.py keep crashing for 4-5 times on every reboot
Same for me. Ubuntu 12.04, 32bits. Lenovo Thinkpad T420s http://thinkwiki.de/T420s Intel HD 3000 Grafik Nvidia NVS 4200M, 1GB VRAM, Optimus After todays update (first since ca. 2 weeks) I went in an endless loop with these dialogs, not only 4-5 of it. One hint: The Hardware Widget shows no proprietary drivers. I am not sure if I had an nvidea driver here, once. lspci shows onboard only: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) System check shows, dito.: OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile x86/MMX/SSE2 OpenGL version string: 3.0 Mesa 8.0.2 Not software rendered: yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: yes More info? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/997470 Title: apport-gpu-error-intel.py keep crashing for 4-5 times on every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/997470/+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 993187] Re: ubuntu 12.04 64bit completely freezes frequently
Same here, X is freezing a couple of times a day, mouse still movable, no clicks/keyboard input accepted, but can switch login on a console via e.g. Alt+F1. Running on an Lenovo R60 with an ATI Radeon X1400, updated 12.04 from 11.10; system was perfectly stable before the dist-upgrade. Happy to provide further input if needed, can't find anything suspicious in dmesg, syslogs or xsession errors etc. -- 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/993187 Title: ubuntu 12.04 64bit completely freezes frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/993187/+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 873495] Re: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed
The workaround does not work for me either. sleep 5 in /etc/init/lightdm.conf still didn't work, but if I put service lightdm start in rc.local that works. Intel i3-550, geforce GT 430, single monitor, Ubuntu 11.10, nvidia-current 280.13-0ubuntu This looks like bug 865768. -- 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/873495 Title: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+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 793764] Re: Top area of screen black when rotating screen
It's working now on my Toshiba Portege M400 with the latest Ubuntu (11.10, 32 bit). -- 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/793764 Title: Top area of screen black when rotating screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/793764/+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 868846] Re: [sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x7b001804
Not Jeff.Frank Jones and same problem gpu hang up.It freezes up randomly and it doesnt matter what you are doing. Mine is freezing up multiple times a day.before it hangs the video Distorts or goes black.after it freezes you can go back to what you are doing but when you scroll down a page it does it with a wave effect.To clear it up you have to restart the comp.Never had this until i dowloaded 11.10 off of updates. On Tue, 2011-10-25 at 23:01 +, Bryce Harrington wrote: Hi Jeff, Have you seen more of these freezes or just this one? Have you seen it since the release? How frequently does it occur? (Daily/Weekly/etc.) Can you tell me what you were doing prior to the freeze (like, resume from suspend, using a 3D application, or whatever)? If you see these freezes often, does it always freeze on the same activity or is it seemingly random? ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed = Incomplete -- 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/868846 Title: [sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x7b001804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/868846/+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 826475] [NEW] package libpciaccess0 0.12.0-1 failed to install/upgrade: ErrorMessage: cannot access archive: No such file or directory
Public bug reported: I don't know what to tell you. I tried to install updates and it said there were problems. Now I'm submitting the error report. Thanks for any help you can give me. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: libpciaccess0 0.12.0-1 ProcVersionSignature: Ubuntu 2.6.35-30.54-generic 2.6.35.13 Uname: Linux 2.6.35-30-generic i686 Architecture: i386 Date: Sun Aug 14 14:50:12 2011 ErrorMessage: ErrorMessage: cannot access archive: No such file or directory InstallationMedia: Lubuntu 10.10 Maverick Meerkat - i386 (20101010) SourcePackage: libpciaccess Title: package libpciaccess0 0.12.0-1 failed to install/upgrade: ErrorMessage: cannot access archive: No such file or directory UpgradeStatus: Upgraded to natty on 2011-08-14 (0 days ago) ** Affects: libpciaccess (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/826475 Title: package libpciaccess0 0.12.0-1 failed to install/upgrade: ErrorMessage: cannot access archive: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/826475/+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 826475] Re: package libpciaccess0 0.12.0-1 failed to install/upgrade: ErrorMessage: cannot access archive: No such file or directory
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/826475 Title: package libpciaccess0 0.12.0-1 failed to install/upgrade: ErrorMessage: cannot access archive: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/826475/+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 826475] Re: package libpciaccess0 0.12.0-1 failed to install/upgrade: ErrorMessage: cannot access archive: No such file or directory
Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/826475 Title: package libpciaccess0 0.12.0-1 failed to install/upgrade: ErrorMessage: cannot access archive: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/826475/+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 795352] [NEW] while enalbled the xinerama the xserver would face a segment fault
Public bug reported:
Binary package hint: xserver-xorg-core
this bug is caused while the root window is visited, then the code still
try to visit the parent drawable.id. so the segment fault is there. the
following code change is about how to fix it and passed the test.
here is the diff file for xorg-server-1.10.1/Xext/panoramiXprocs.c
565,566c565
if((pWin-parent == screenInfo.screens[0]-root) ||
(pWin-parent-drawable.id ==
screenInfo.screens[0]-screensaver.wid))
---
if((pWin-parent == screenInfo.screens[0]-root))
568,570c567,577
rep.x += screenInfo.screens[0]-x;
rep.y += screenInfo.screens[0]-y;
}
---
rep.x += screenInfo.screens[0]-x;
rep.y += screenInfo.screens[0]-y;
}
if(pWin-parent != 0)
{
if((pWin-parent-drawable.id ==
screenInfo.screens[0]-screensaver.wid))
{
rep.x += screenInfo.screens[0]-x;
rep.y += screenInfo.screens[0]-y;
}
}
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
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/795352
Title:
while enalbled the xinerama the xserver would face a segment fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/795352/+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 795352] Re: while enalbled the xinerama the xserver would face a segment fault
please notice that the testing env is enable the desktop env with compiz or unity first, then enable the xinerama. -- 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/795352 Title: while enalbled the xinerama the xserver would face a segment fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/795352/+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 793764] Re: Top area of screen black when rotating screen
I have the same problem on a Toshiba Portege M400. Same version of Natty (i386), same graphics (Intel 945). My screen resolution is 1400x1050. If I toggle it down to 1024x768, it rotates okay. But if I leave it at the native resolution, I get the black bar at the top of the screen. -- 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/793764 Title: Top area of screen black when rotating screen ___ 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 433142] Re: geode driver do not display 1024x600 on (K)UNR Karmic
If you want to support a new mode(i.e. 1024x600@60), add it to your code, and let that mode to be default. See my reply on #75, #82, #84, #93, #95. Thanks, Frank -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Anewangelfades Sent: 2011年5月9日 22:43 To: Huang, FrankR Subject: [Bug 433142] Re: geode driver do not display 1024x600 on (K)UNR Karmic Hello, The bug affects also affects 10.10 Maverick Meerkat and 11.04. Is there a way to fix it? I tried every xorg.conf here, but none works! -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/433142 Title: geode driver do not display 1024x600 on (K)UNR Karmic Status in “xserver-xorg-video-geode” package in Ubuntu: In Progress Bug description: Geode driver do not display 1024x600 resolution in (K)UNR Karmic. Actually, the bug also affects Jaunty, but doesnt affect Intrepid. I used to use a custom xorg.conf in intrepid, but it doesnt work on Jaunty or Karmic. In Jaunty and karmic, I could only use 1024x768 whick makes the screen bigger than the real display and is impossible to open new programs, specially in the menus (they simply disapear in the bottom of the screen). Further investigations on other distros made me think this is a regression from the xserver-xorg-video-geode 2.10.1-2. This bug affects all drivers from 2.10.1 (which is in Intrepid). In fact, Debian Lenny (that uses geode 2.10.1-2) works perfectly, VectorLinux 6.0 lite (that uses geode 2.9 - i think), also works. Jaunty (geode 2.11.1-1) and Karmic (2.11.4.1-1) dont work, they only display 1024x768... Actually, when I use the automatic configuration in Jaunty and Karmic (with no xorg.conf), the screen really seems to be 1024x768, but when I use the custom xorg.conf (the same I use in Intrepid), the screen seems different... like it was 800x768 (I know it's wierd, but it doesnt seem to be 1024x768 at all - everything is really ugly). Hope it will work in Karmic in time. Thanks in advance. [lspci] 00:01.1 VGA compatible controller [0300]: Advanced Micro Devices [AMD] Geode LX Video [1022:2081] Subsystem: Advanced Micro Devices [AMD] Geode LX Video [1022:2081] To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- geode/+bug/433142/+subscribe -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-geode in Ubuntu. https://bugs.launchpad.net/bugs/433142 Title: geode driver do not display 1024x600 on (K)UNR Karmic ___ 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 773484] [NEW] Logs are filling up with one error message
Public bug reported: Binary package hint: xorg This is an example Apr 29 10:08:14 frank-desktop kernel: [ 107.859809] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859816] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859825] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859832] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859840] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859847] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859854] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859862] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859869] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859876] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859885] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times Apr 29 10:08:14 frank-desktop kernel: [ 107.859892] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DRM.card0.VGA.1: status: connected enabled: enabled dpms: On modes: 1680x1050 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1152x864 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 720x400 edid-base64: AP///wAebWhWS7sBAAgRAQNqKxt46s/Fo1pJoCUSUFSna4CVD5UAgYCBQHFPAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAaITmQMGIaJ0BosDYAsg4RAAAc/QA4Sx5TDwAKICAgICAg/ABMMjA2VwogICAgICAgAJk= Date: Fri Apr 29 13:48:21 2011 DistUpgraded: Log time: 2011-02-10 19:54:11.775368 DistroCodename: natty DistroVariant: ubuntu GraphicsCard: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Desktop Board D865GBF [8086:4246] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110202) ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=3012f12a-f637-40be-8a52-71b8d75b2726 ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to natty on 2011-02-23 (64 days ago) dmi.bios.date: 08/04/2005 dmi.bios.vendor: Intel Corp. dmi.bios.version: BF86510A.86A.0077.P25.0508040031 dmi.board.name: D865GBF dmi.board.vendor: Intel Corporation dmi.board.version: AAC28140-405 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBF86510A.86A.0077.P25.0508040031:bd08/04/2005:svn:pn:pvr:rvnIntelCorporation:rnD865GBF:rvrAAC28140-405:cvn:ct2:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 7.10.2-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty regression-update ubuntu unity-2d -- 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/773484 Title: Logs are filling up with one error message ___ 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 773484] Re: Logs are filling up with one error message
-- 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/773484 Title: Logs are filling up with one error message ___ 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 632376] Re: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build
** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Expired = Incomplete -- 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/632376 Title: package nvidia-current 256.53-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build ___ 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 727112] Re: nvidia-current does not detect hardware capabilities correctly
new symptom: last week i had a projector plugged in while booting into ubuntu. when i went home i only put my computer to sleep. when using my monitor at home i was then able to run both monitors in full resolution (nvidia-settings was still thinking the projector was plugged in, it would not recognize my monitor) -- 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/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 738972] [NEW] package nvidia-current 260.19.06-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I tried to install the Nvidia graphics driver, current version. It failed. ProblemType: Package DistroRelease: Ubuntu 10.10 Package: nvidia-current 260.19.06-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Date: Sun Mar 20 21:36:54 2011 DkmsStatus: ErrorMessage: subprocess installed post-installation script returned error exit status 1 GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory LiveMediaBuild: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MachineType: System manufacturer System Product Name ProcCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper persistent initrd=/casper/initrd.lz splash -- BOOT_IMAGE=/casper/vmlinuz SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 260.19.06-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 dmi.bios.date: 01/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1709 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1709:bd01/04/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-22-generic ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package maverick -- 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/738972 Title: package nvidia-current 260.19.06-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ___ 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 738972] Re: package nvidia-current 260.19.06-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- 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/738972 Title: package nvidia-current 260.19.06-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ___ 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 727112] Re: nvidia-current does not detect hardware capabilities correctly
hi bryce, no more luck without an xorg.conf, why would it? there's not much in my config, except the driver. for classic desktop, i am running it already – desktop effects take too much time and resources. i can try if desktop with effects works with nvidia-173 driver, but i'm pretty sure it will (was nvidia-173 updated for the new xserver already?) -- 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/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 727112] [NEW] nvidia-current does not detect hardware capabilities correctly
Public bug reported: nvidia-current is unable to use two monitors in full resolution (wuxga + full hd), one will always stay blank. looking into xorg.log, i can see something like: [ 89444.991] (WW) NVIDIA(0): Due to hardware capability constraints, disabling display [ 89444.991] (WW) NVIDIA(0): device Seiko/Epson (DFP-0) in MetaMode [ 89444.991] (WW) NVIDIA(0): CRT-0:nvidia-auto-select@1920x1080+1920+0,DFP-0:1920x1200@1920x1200+0+0. the same configuration works with nvidia-173, so nvidia-current might not be detecting hardware capabalities correctly. nvidia-173 feels a bit slower than nvidia-current, so i'd like to use nvidia-current. my graphics card is `01:00.0 VGA compatible controller: nVidia Corporation G86M [Quadro FX 360M] (rev a1)` i'll be glad to give further information, this has bugged me for quite a while. i'm currently running natty, but i've seen this bug since nvidia- current was introduced ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nvidia-current 270.29-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic-pae 2.6.38-rc6 Uname: Linux 2.6.38-5-generic-pae i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 270.29 Wed Feb 23 16:16:53 PST 2011 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3) Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] CompositorRunning: None Date: Tue Mar 1 12:34:01 2011 DistUpgraded: Yes, recently upgraded Log time: 2010-12-25 19:00:20.784814 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-5-generic, i686: installed virtualbox-ose, 4.0.4, 2.6.38-5-generic-pae, i686: installed nvidia-current, 270.29, 2.6.38-5-generic-pae, i686: installed GraphicsCard: nVidia Corporation G86M [Quadro FX 360M] [10de:042d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01ff] MachineType: Dell Inc. Precision M4300 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic-pae root=UUID=f957135d-b762-45ac-9e0d-6979595882aa ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: nvidia-graphics-drivers UpgradeStatus: Upgraded to natty on 2011-01-13 (46 days ago) dmi.bios.date: 05/23/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/23/2008:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M4300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.4-0ubuntu2 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu5 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty ubuntu -- 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/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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 727112] Re: nvdia-current does not detect hardware capabilities
** Attachment added: output of nvidia-bug-report.sh https://bugs.launchpad.net/bugs/727112/+attachment/1878462/+files/nvidia-bug-report.log.gz ** Summary changed: - nvdia-current does not detect hardware capabilities + nvidia-current does not detect hardware capabilities correctly -- 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/727112 Title: nvidia-current does not detect hardware capabilities correctly ___ 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
