[Ubuntu-x-swat] [Bug 2003140] Re: Ubuntu laptop can't use external monitors
** Description changed: # What happens (Steps to reproduce): 1. Install a clean version of Ubuntu onto a laptop: Hardware="https://www.dell.com/support/manuals/en-uk/precision-15-3541-laptop/precision_3541_setupspecs/video?guid=guid-0712681b-956e-4229-96a7-545baca605fc=en-us; VERSION="20.04.5 LTS (Focal Fossa)" nick@Precision-3541:~$ sudo lshw -C display [sudo] password for nick: *-display description: 3D controller product: GP107GLM [Quadro P620] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:168 memory:ec00-ecff memory:c000-cfff memory:d000-d1ff ioport:3000(size=128) memory:ed00-ed07 *-display description: VGA compatible controller product: UHD Graphics 630 (Mobile) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:166 memory:eb00-ebff memory:8000-8fff ioport:4000(size=64) memory:c-d 2. Connect a monitor and laptop with an HDMI cable 3. Result - The monitor should display "No Signal" - Ubuntu should recognize the monitor, but not display anything on it. # What should happen Ubuntu should send signal to external monitors connected to the HDMI port. It should automatically configure discrete graphics cards. The same hardware works when booted from the Windows partition. # What I've tried ## Things that worked + None + + ## Things that worked temporarily https://askubuntu.com/questions/1105332/external-monitor-not-working-ubuntu-nvidia/1134579#1134579 - Edit /lib/modprobe.d/nvidia-kms.conf to enable modsetting - - ## Things that worked temporarily - Installing NVidia-Prime, Setting "Performance Mode" to always use the discrete GPU + Installing NVidia-Prime, Setting "Performance Mode" to always use the + discrete GPU ## Things that did not work (from various forums) 1. Using multiple different drivers via "Software/Additional Drivers" 2. Using the driver from NVidia's website 3. Enabling NVidia via a modprob parameter at startup 4. Varius xorg configuration files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 16:58:33 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.161.03, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a] Subsystem: Dell GP107GLM [Quadro P620] [1028:091a] InstallationDate: Installed on 2023-01-06 (11 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 3541 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=90df9afc-2dd2-439d-a69c-3aa27146e9fc ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 09/13/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.23.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.23.0:bd09/13/2022:br1.23:svnDellInc.:p
[Ubuntu-x-swat] [Bug 1998639] Re: MESA-INTEL: warning:
** Package changed: ubuntu-release-upgrader (Ubuntu) => mesa (Ubuntu) -- 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/1998639 Title: MESA-INTEL: warning: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1998639/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926860/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Patch added: "apport-lp-1952947-impish.debdiff" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561447/+files/apport-lp-1952947-impish.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** Description changed: + [Impact] + + This bug makes it more difficult for Wayland users to report bugs with + apport. When a Wayland user tries to use the -w,--window option, apport + fails silently. We do not want users to face a high barrier to + submitting bug reports. + + The patch for this bug adds a message explaining that the -w,--window + option cannot be used on Wayland, and suggests a method for finding the + window's PID instead. + + [Test Plan] + + * Log on to Ubuntu on Wayland. You can check that $XDG_SESSION_TYPE=="wayland" in your current session. + * Open a terminal, and run `ubuntu-bug -w`. + * Click on any other window, and observe that the apport UI will not respond. + + [Where problems could occur] + + The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to + 'wayland'. If either of these strings in the patch were wrong, or the + environment variable was not used in the target release, the condition + would likely never be true. + + [Original Description] + I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed - What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: - + ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) ** Patch added: "apport-lp-1952947-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561446/+files/apport-lp-1952947-focal.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1917806] Re: [amdgpu] Freezes after submitting the login password
** Attachment added: "prevboot log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+attachment/5473726/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1917806 Title: [amdgpu] Freezes after submitting the login password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+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 1917806] [NEW] Xorg freeze
Public bug reported: Freezes after submitting the login password. If I shutdown the system it usually works afterwards on the first boot, but not subsequent reboots. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-lowlatency 5.4.86 Uname: Linux 5.4.0-66-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 06:39:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2314] InstallationDate: Installed on 2020-12-07 (87 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-lowlatency root=UUID=d8850dd9-0462-4a0b-a22c-24c0df1551a7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/01/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3405:bd02/01/2021:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 freeze third-party-packages 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/1917806 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1917806/+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 1890863] Re: Display does not come on after suspend
Hello, here is the log as requested ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1890863/+attachment/5400918/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1890863 Title: Display does not come on after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1890863/+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 1890863] [NEW] Display does not come on after suspend
Public bug reported: After coming out of suspend the display is not receiving any data and stays in power saving mode. Only power cycling the system brings it back. Unsure whether this is related to amdgpu or something else. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 12:51:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2314] InstallationDate: Installed on 2020-01-08 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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 third-party-packages 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/1890863 Title: Display does not come on after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890863/+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 1827428] Re: Mouse cursor left frozen copy of itself
Also FWIW it also happens with amdgpu so I think it's probably mutter and not nvidia -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 1827428] Re: Mouse cursor left frozen copy of itself
Been experiencing this on multiple distributions but haven't been able to find an upstream bug report -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
I am going to disagree with #62. I am running Lubuntu 18.04 fully updated as of the date of this message. My system is a Dell Optiplex 9020. I have tested with a Logitech M325 wireless mouse, a Dell usb mouse and an old hp PS/2 mouse (the Optiplex 9020 is a modern system but does indeed have PS/2 ports.) Symptoms: Periodically I see the mouse cursor run uncommanded to the upper left corner of the screen and it takes a while to get back down to where it should be. This happens with all 3 of the mice previously mentioned. I intend to try to the solution in #32. -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1750973] Re: Program sub menus dark gray on black, thus illegible
This issue (which did not occur with a fresh install of 16.04) appears
to be related to the contents of file:
/usr/share/themes/Ambiance/gtk-2.0/gtkrc
At line 346 (at present) there is the following:
style "menu" = "dark" {
Changing it to:
style "menu" {
... resolves this particular issue, however I'm not sure what side-
effects that would have. In the original release the line was like that
in the first place, so it would have been changed for a reason.
Screenshots of "before" and "after" that change can be seen here:
https://askubuntu.com/a/1014016/425017
--
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/1750973
Title:
Program sub menus dark gray on black, thus illegible
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750973/+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 1734794] Re: Install of ubuntu-desktop login loop
** Package changed: xorg (Ubuntu) => ubuntu-meta (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/1734794 Title: Install of ubuntu-desktop login loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1734794/+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 1734794] [NEW] Install of ubuntu-desktop login loop
Public bug reported: Tested on clean VM. To repro install ubuntu-17.10 server edition > sudo apt update > sudo apt upgrade > sudo apt install ubuntu-desktop --no-install-recommends > sudo reboot # Reboots to graphical login screen. After entering username password returns to graphical login for both Ubuntu and Ubuntu on Xorg # Switch to tty2 > sudo apt install gsettings-ubuntu-schemas # Switch to tty1 # Login now works ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Mon Nov 27 19:50:24 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2017-11-28 (0 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 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 artful crash 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/1734794 Title: Install of ubuntu-desktop login loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734794/+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 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.
This bug happens again after I've done a fresh install. ** Attachment added: "Xorg.0.log.problem_wait" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+attachment/4947065/+files/Xorg.0.log.problem_wait -- 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/1664979 Title: EQ overflowing. Additional events will be discarded until existing events are processed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+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 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.
It happened when I unlock 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/1664979 Title: EQ overflowing. Additional events will be discarded until existing events are processed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+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 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.
After another reboot, EQ overflowing occurs again, it seems random to me now. ** Summary changed: - Xorg freeze EQ overflow... + EQ overflowing. Additional events will be discarded until existing events are processed. -- 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/1664979 Title: EQ overflowing. Additional events will be discarded until existing events are processed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+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 1664979] [NEW] Xorg freeze EQ overflow...
Public bug reported: I was on 14.04 and had no problem, but I started to have EQ overflow after upgrading to 14.04.3. Then I did fresh install of 16.04 on the same PC, but still EQ overflow occurs after closing SMPlayer. [640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078) [640417.566] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0x4078) [640421.680] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0xf5d4) [640428.680] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0xf5d4) [640439.704] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc1, 0x3d14, 0xf680) [640446.704] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc1, 0x3d14, 0xf680) [640449.705] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf7, 0x3d14, 0xf680) [640456.705] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf7, 0x3d14, 0xf680) [640459.706] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc2, 0x3d14, 0xf724) [640466.706] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc2, 0x3d14, 0xf724) [640469.707] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf8, 0x3d14, 0xf724) [640476.707] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf8, 0x3d14, 0xf724) [640479.708] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640486.708] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640489.709] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640496.709] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640499.710] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640506.710] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640509.711] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640516.711] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640519.712] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc5, 0x3d14, 0xf910) [640526.712] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc5, 0x3d14, 0xf910) [640529.713] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfb, 0x3d14, 0xf910) [640536.713] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfb, 0x3d14, 0xf910) [640539.714] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640546.714] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640549.715] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfc, 0x3d14, 0xf9b4) (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55b19d04a583] (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 6: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47] (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61] (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc] (EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 4: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47] (EE) 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61] (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc] (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2] (EE) (EE) [mi] EQ overflow continuing. 200 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d)
[Ubuntu-x-swat] [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine
I'm possibly experiencing this bug, but I'm using the Nvidia proprietary driver, particularly the 367.57 version. I tried to switch the clocksource to acpi_pm, as suggested in some forums, but it doesn't help. While that's EQ overflowing, I couldn't check anything but reboot. Attached is the Xorg.0.log.old file. ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+attachment/4808950/+files/Xorg.0.log.old ** Changed in: xorg (Ubuntu) Status: Expired => New -- 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/1587730 Title: graphic system freezes after a while, can still ssh into machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+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 1587730] Re: graphic system freezes after a while, can still ssh into machine
P.S. mine is also GT710 and Xubuntu 16.04, with kernel 4.4.0-59-generic. -- 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/1587730 Title: graphic system freezes after a while, can still ssh into machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+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 1656674] [NEW] package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: i was running sudo apt-get install mesa-utils for working with my amd driver ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libxatracker2:amd64 11.2.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 AptOrdering: mesa-utils: Install libxatracker2: Configure mesa-utils: Configure NULL: ConfigurePending Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jan 15 09:27:42 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.59, 4.4.0-59-generic, x86_64: installed DuplicateSignature: package:libxatracker2:amd64:11.2.0-1ubuntu2 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libxatracker2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] [1002:9830] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8400 / R3 Series] [1025:0800] InstallationDate: Installed on 2017-01-15 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gateway DX4375G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=82028627-51f0-4612-98d1-f0557bc85e0c ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: mesa Title: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-A3 dmi.board.name: DX4375G dmi.board.vendor: Gateway dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-A3:bd06/27/2013:svnGateway:pnDX4375G:pvr:rvnGateway:rnDX4375G:rvr:cvnGateway:ct3:cvr: dmi.product.name: DX4375G dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jan 15 09:14:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: radeon ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 need-duplicate-check ubuntu xenial -- 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/1656674 Title: package libxatracker2:amd64 11.2.0-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1656674/+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 1639180] Re: no login possible after update to nvidia 304.132
Just hit this and judging from various comments online lots of other people have to. You might want to withdraw version 304.132... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1196239] Re: Add support for fake modes on laptop screens which only have one
I was just including my example as another plus point for fake modes ("scale"
in this case didn't mean "output scaling".
If we had the fake modes then output scaling wouldn't really be required in
this case, as we would have a set of mutually inclusive modes to chose from.
--
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/1196239
Title:
Add support for fake modes on laptop screens which only have one
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+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 1196239] Re: Add support for fake modes on laptop screens which only have one
This is also an issue when we have cloned displays. We need to be able to scale down to a fake mode. My laptop screen only runs at 1080p and if I have an external monitor plugged in with a lower resolution (eg 720), the only valid resolution will be the lower one. -- 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/1196239 Title: Add support for fake modes on laptop screens which only have one To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+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 1638139] [NEW] xvfb fails to launch
Public bug reported: The system for this bug is running Trusty with xvfb 2:1.15.1-0ubuntu2.7 Xvfb fails to launch after being used for a couple days and I can't see any reason to why it wont launch. We have inetd.conf setup to run an x11vnc script with the following command whenever a connection comes in on port 5902 (assumed to be a tunneled VNC). /usr/bin/x11vnc -inetd -oa /tmp/x11vnc.log -once -noxrecord -env FD_GEOM=1024x768 -env FD_XDMCP_IF=127.0.0.1 -create_xsrv Xvfb.xdmcp -gone 'pkill -f "Xvfb.*`echo $DISPLAY | cut -d . -f 1`\>"' x11vnc is attempting to launch xvfb but it's failing after having worked for multiple connections and there doesn't seem to be any indication on why. The log files show this error: 28/10/2016 20:22:28 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 30524 28/10/2016 20:22:28 28/10/2016 20:22:28 wait_for_client: WAIT:cmd=FINDCREATEDISPLAY-Xvfb.xdmcp 28/10/2016 20:22:28 28/10/2016 20:22:28 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560 28/10/2016 20:22:28 28/10/2016 20:22:28 initialize_screen: -inetd mode: F_GETFL(stdin): 0x2 28/10/2016 20:22:28 initialize_screen: -inetd mode: F_GETFL(stdout): 0x2 28/10/2016 20:22:28 initialize_screen: -inetd mode and stdio is O_RDWR 28/10/2016 20:22:28 other clients: 28/10/2016 20:22:28 Normal socket connection 28/10/2016 20:22:28 incr accepted_client=1 for 127.0.0.1:40110 sock=3 28/10/2016 20:22:28 wait_for_client: got client 28/10/2016 20:22:28 client progressed=0 in 15/10 0.009395 s 28/10/2016 20:22:28 client useCopyRect: 127.0.0.1 0 28/10/2016 20:22:28 client_set_net: 127.0.0.1 0.0002 28/10/2016 20:22:28 wait_for_client: running: env X11VNC_SKIP_DISPLAY='' /bin/sh /tmp/x11vnc-find_display.6APOWs xauth: unable to generate an authority file name 28/10/2016 20:22:28 wait_for_client: find display cmd failed. 28/10/2016 20:22:28 wait_for_client: FINDCREATEDISPLAY cmd: /bin/sh /tmp/x11vnc-find_display.6APOWs Xvfb.xdmcp trying N=20 ... /root redir_daemon= /usr/bin/xauth: unable to generate an authority file name
[Ubuntu-x-swat] [Bug 1624903] [NEW] Apport conflict, shows up in dmesg log
Public bug reported: Slows boot time in Ubuntu to over 1 minute 40 seconds. The system appears to hang when loading Apport. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 18 18:14:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:161c] InstallationDate: Installed on 2015-10-27 (326 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) LightdmGreeterLogOld: init: indicator-bluetooth main process (6277) killed by TERM signal init: indicator-power main process (6282) killed by TERM signal init: indicator-datetime main process (6284) killed by TERM signal init: indicator-application main process (6307) terminated with status 1 MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=74e5a5b7-cc3f-4a7f-a7e0-779ba66c45c4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.61 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.61:bd06/11/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 18 17:57:45 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5223 vendor CMO xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1624903 Title: Apport conflict, shows up in dmesg log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1624903/+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 1547599] Re: legacy nvidia drivers fail to work with latest kernel
I was able to fix this problem on a MacBook Pro 4,1 with a GeForce 8600M GT by following these instructions: https://ubuntuforums.org/showthread.php?t=2209602 In this case, installing the current version of Ubuntu (16.04.1) via USB with a GUID partition table was not a problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1547599 Title: legacy nvidia drivers fail to work with latest kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1547599/+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 1576546] Re: random letters don't display after resume from sleep
That's correct. And it hadn't happened for a while now but just happened again yesterday. -- 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/1576546 Title: random letters don't display after resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1576546/+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 1243642] Re: .Xmodmap not automatically loaded on start
I just switched to Ubuntu from Debian (using xfce not gnome). .Xmodmap has worked on Debian since ... forever. I can't do without it. I thought Ubuntu was based on Debian? -- 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/1243642 Title: .Xmodmap not automatically loaded on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+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 1499416] Re: xterm freeze when accepting input from usb scanner
I worked with Zebra on this and was able to get the scanner working by reducing the USB polling interval on the scanner to 8msec, the default is to poll every 3msec. I still believe this is a bug in how xterm accepts input because of the following: A) This issue does not occur when accepting input as root. B) This issue does not occur on older versions of xterm (261 was tested) C) This issue does not occur when accepting input into other applications or windows. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1499416 Title: xterm freeze when accepting input from usb scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+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 1499416] Re: xterm freeze when accepting input from usb scanner
Thanks for the response Thomas. The DS4208 has multiple cables that it can be plugged in with, the xterm issues are when it is plugged in over USB. RS232 is not used for doing direct-text input. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1499416 Title: xterm freeze when accepting input from usb scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+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 1499416] [NEW] xterm freeze when accepting input from usb scanner
Public bug reported: I have a symbol DS4208 Wired USB barcode scanner hooked up to a machine running Ubuntu 14.04 via a USB connector. When using xterm and attempting to scan a 1D or 2D barcode the xterm window will accept in a couple characters from the USB scanner not in the correct order, and then lockup. The number of characters accepted varies, and is never in the correct order. This also happens from any child process launched from the xterm window. This issue is not present when I first sudo -s to obtain a root shell. Scans will be interpreted properly and characters are entered into child processes, or command line correctly depending on where the cursor is situated. This issue is not present in other terminal emulators such as lxterminal. ** Affects: xterm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1499416 Title: xterm freeze when accepting input from usb scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+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 1499416] Re: xterm freeze when accepting input from usb scanner
Thanks, I'll try running with -k8 and other settings to see if I can't get it to respond differently! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1499416 Title: xterm freeze when accepting input from usb scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+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 1499416] Re: xterm freeze when accepting input from usb scanner
Thomas, The characters being sent/received are normal ASCII characters, we're doing Vin code scanning so it's even in the domain A-Z 0-9 like I said, it was working fine on an older version of xterm. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1499416 Title: xterm freeze when accepting input from usb scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+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 1499416] Re: xterm freeze when accepting input from usb scanner
Thomas: This issue is reproducible simply by attempting to scan a barcode into the xterm window NOT a child process, I was simply indicating that it happened in both places. The USB scanner is acting as a basic character-input device when used like this. There's no special application running it's just detected by Ubuntu as a Symbol Scanner and then I'm opening an xterm window and trying to scan something, at this point xterm completely locks up, can't cntrl-c can't click X to kill it. Have to manually open another terminal and kill the xterm process. However, the Scanner will work properly using any other application that was not launched using xterm. For instance I can launch lxterminal and it accepts the scan as text input just fine, same with a web browser, or leafpad. Also, this is not an issue on our previous system installation which uses Ubuntu Maverick & has xterm 261-1ubuntu3 installed, it's only happening on Trusty with xterm 297-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1499416 Title: xterm freeze when accepting input from usb scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+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 1499416] Re: xterm freeze when accepting input from usb scanner
Here's what xterm is apparently seeing when I scan a barcode and use the -l option to log the output. ^[]0;isisup@LUBE151: ~^Gisisup@LUBE151:~$ 1G The 1G is the first 2 printed characters of the barcode in this case, but there are 15 more it should have kept reading instead locking up. Using another barcode I get this: ^[]0;isisup@LUBE151: ~^Gisisup@LUBE151:~$ 3B5 The 3B5 is actually incorrect in this case, the barcode I scanned is should be showing 3B7 then another 14 characters. Now I tried the same thing on the older version of xterm and it also has the same control characters in the log to start with, but will finish scanning the full barcode to the command line. Any ideas on this? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1499416 Title: xterm freeze when accepting input from usb scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+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 1468373] Re: GPU driver issues when waking up from suspend mode
I have exactly the same issue with Kubuntu 15.04 (clean install, all updates). lspci: 00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller (rev 01) 00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge (rev 01) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: NVIDIA Corporation GF104 [GeForce GTX 460] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF104 High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) 03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II / PATA Controller (rev b2) 05:00.0 Multimedia audio controller: Creative Labs CA0106 Soundblaster -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1468373 Title: GPU driver issues when waking up from suspend mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1468373/+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 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
Could you guys fix this already? Using an excuse that it's not broken in 15.04 is total BS. 14.04.2 is supposed to be a LONG TERM SUPPORT version and one of the most important parts of a desktop system has been unable to be installed for like 2-3 months now. This is pathetic. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1424491/+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 1435587] Re: System slows down to almost unusable then freezes during usage (High kworker cpu usage etc)
Hi Christopher, Thanks for your response. Actually in the end I re-installed a debian system, so I can't really help with any more diagnostics from the system that was having the problem. I can report that I'm not seeing this crash on the same laptop with the 3.16.0-4-amd64 kernel and Debian Jessie installed. I'll notify here if it reaapears in Debian, too. Best wishes, Nick Dowson -- 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/1435587 Title: System slows down to almost unusable then freezes during usage (High kworker cpu usage etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1435587/+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 1435587] [NEW] System slows down to almost unusable then freezes during usage (High kworker cpu usage etc)
Public bug reported: Hi, after an update about a month and a half / two months ago my system started freezing after a period of usage. This tends to happen about once a day... so generally after the laptop's been on for a few hours (not necessarily constantly), sometimes probably up to 8 or ten hours. But the freezing doesn't seem to correlate to any particular activity or application that I am using. When the freeze occurs, the system slows down and doing anything takes excruciatingly long. It never recovers from this and I have to shutdown. Sometime REISUB can take the system down but sometimes I just have to hold the power button to switch it off the harmful way! A few times I have managed to get 'System Activity' (KDE Task Manager) or top up before it has frozen completely and this has shown multiple Kworker processes using up huge amounts of CPU. Looking this up on the forums I found a couple of suggested solutions: I tried turning off acpi interrupts for certain gpes (http://askubuntu.com/questions/176565/why-does-kworker-cpu-usage-get- so-high). I initially thought this had helped, but it hasn't (possibly slowing down the frequency of the freezes). I also tried the drm_kms helper fix: https://souriguha.wordpress.com/2011/03/08/how-to-solve- problem-with-thinkpadkslowd-kworker-on-linux-kernel-2-35-2-36/. Alas, no success. As I said, the freezing first occured almost two months ago, whilst I was using Ubuntu 14.04. I upgrade to 14.10 to see if this would help the freeze but no luck. Happy to try further diagnostics or any suggested workarounds appreciated; I got a bit lost in the different wiki pages and wasn't sure whether this was really the same sort of freeze / crash as they were talking about (I don't think it really has anything to do with xorg!) Cheers. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Mar 23 21:53:17 2015 InstallationDate: Installed on 2014-05-02 (325 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2015-02-17 (34 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts kubuntu utopic -- 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/1435587 Title: System slows down to almost unusable then freezes during usage (High kworker cpu usage etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1435587/+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 1429381] [NEW] could not connect to internet
Public bug reported: for 3 days ran this and it worked after ,no idea if this fixed it or coincidence but thanks have a grat weekend i love ubuntu just wish someone could send me in the right direction to learn it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 Date: Sat Mar 7 11:20:50 2015 DistUpgraded: 2015-03-03 14:19:06,750 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:034a] Subsystem: Acer Incorporated [ALI] Device [1025:034a] InstallationDate: Installed on 2014-03-16 (355 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic root=UUID=5cd8006c-556d-49db-858b-d7499eb21b3f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2015-03-03 (3 days ago) dmi.bios.date: 08/12/2010 dmi.bios.vendor: GATEWAY dmi.bios.version: V3.05(DDR2) dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Acer dmi.board.version: V3.05(DDR2) dmi.chassis.type: 10 dmi.chassis.vendor: GATEWAY dmi.chassis.version: V3.05(DDR2) dmi.modalias: dmi:bvnGATEWAY:bvrV3.05(DDR2):bd08/12/2010:svnGATEWAY:pn:pvrV3.05(DDR2):rvnAcer:rn:rvrV3.05(DDR2):cvnGATEWAY:ct10:cvrV3.05(DDR2): dmi.product.version: V3.05(DDR2) dmi.sys.vendor: GATEWAY 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 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Mar 7 10:50:57 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 25042 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.7 ** 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/1429381 Title: could not connect to internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1429381/+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 1341309] Re: [965gm mesa] TotalBlackCrash_or_IntermittingScreenView, GPU lockup in Chromium
Issue persists in Xubuntu 14.04; opening http://google.com/chrome/ in either Chrome or Firefox triggers the bug. The issue can be worked around by either disabling hardware acceleration in Chrome or switching the acceleration method to UXA in Xorg.conf. -- 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/1341309 Title: [965gm mesa] TotalBlackCrash_or_IntermittingScreenView, GPU lockup in Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1341309/+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 1424263] Re: Broken dependencies
Thank you Infektedpc it is work for me too. -- 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/1424263 Title: Broken dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424263/+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 1411552] Re: External monitor detected only on first plug.
*** This bug is a duplicate of bug 1300914 *** https://bugs.launchpad.net/bugs/1300914 Edgar I have the same problem only _after_ upgrading to 3.13.0-44-generic. Can you test if the problem goes away for you too when you boot with an earlier version of kernel? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1411552 Title: External monitor detected only on first plug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1411552/+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 1411552] Re: External monitor detected only on first plug.
*** This bug is a duplicate of bug 1300914 *** https://bugs.launchpad.net/bugs/1300914 oops! I've missed the duplicate bug warning - will re-post to bug #1300914 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1411552 Title: External monitor detected only on first plug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1411552/+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 1370270] Re: package fglrx-updates-core 2:14.201-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I'm also seeing this after both an upgrade, then a purge reinstall. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1370270 Title: package fglrx-updates-core 2:14.201-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1370270/+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 1369307] [NEW] package fglrx-core (not installed) failed to install/upgrade: trying to overwrite '/lib/fglrx/modprobe.conf', which is also in package fglrx 2:13.350.1-0ubuntu3
Public bug reported: Upgrading fglrx (13.350.1-0ubuntu3 = 14.201-0ubuntu1) Unpacking fglrx-core (2:14.201-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/fglrx-core_2%3a14.201-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/lib/fglrx/modprobe.conf', which is also in package fglrx 2:13.350.1-0ubuntu3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../fglrx_2%3a14.201-0ubuntu1_amd64.deb ... Removing all DKMS Modules Done. Unpacking fglrx (2:14.201-0ubuntu1) over (2:13.350.1-0ubuntu3) ... dpkg: warning: unable to delete old directory '/usr/lib/fglrx/etc/ati': Directory not empty dpkg: warning: unable to delete old directory '/usr/lib/fglrx/etc': Directory not empty dpkg: warning: unable to delete old directory '/etc/OpenCL/vendors': Directory not empty dpkg: warning: unable to delete old directory '/etc/OpenCL': Directory not empty Processing triggers for man-db (2.6.7.1-1) ... ProblemType: Package DistroRelease: Ubuntu 14.10 Package: fglrx-core (not installed) ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Sep 14 13:31:04 2014 DistUpgraded: 2013-10-23 23:59:31,596 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.4, 3.16.0-11-generic, x86_64: installed vboxhost, 4.3.4, 3.16.0-13-generic, x86_64: installed DuplicateSignature: package:fglrx-core:(not installed):trying to overwrite '/lib/fglrx/modprobe.conf', which is also in package fglrx 2:13.350.1-0ubuntu3 ErrorMessage: trying to overwrite '/lib/fglrx/modprobe.conf', which is also in package fglrx 2:13.350.1-0ubuntu3 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03ea] XGI Technology Inc. (eXtreme Graphics Innovation) Z7/Z9 (XG20 core) [18ca:0020] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:82b4] MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-13-generic root=/dev/mapper/hybrid--root-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: fglrx-installer Title: package fglrx-core (not installed) failed to install/upgrade: trying to overwrite '/lib/fglrx/modprobe.conf', which is also in package fglrx 2:13.350.1-0ubuntu3 UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 127: /usr/lib/nux/unity_support_test: error while loading shared libraries: libatiuki.so.1: cannot open shared object file: No such file or directory UpgradeStatus: Upgraded to utopic on 2013-10-24 (325 days ago) dmi.bios.date: 05/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2107 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B-X series dmi.board.vendor: ASUSTeK Computer INC. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2107:bd05/04/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnP8B-Xseries:rvr:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.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.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56+git20140801.5d835797-0ubuntu0sarvatt~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20140911.79736944-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20140904.3cd4c849-0ubuntu0sarvatt~trusty xserver.bootTime: Sun Sep 14 12:48:33 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No
[Ubuntu-x-swat] [Bug 1369307] Re: package fglrx-core (not installed) failed to install/upgrade: trying to overwrite '/lib/fglrx/modprobe.conf', which is also in package fglrx 2:13.350.1-0ubuntu3
** Attachment removed: xserver.devices.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203893/+files/xserver.devices.txt ** Attachment removed: xserver.outputs.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203894/+files/xserver.outputs.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203882/+files/ProcCpuinfo.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203883/+files/ProcInterrupts.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203884/+files/ProcModules.txt ** Attachment removed: GconfCompiz.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203875/+files/GconfCompiz.txt ** Attachment removed: LightdmLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203879/+files/LightdmLog.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203880/+files/Lspci.txt ** Attachment removed: Xrandr.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+attachment/4203890/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1369307 Title: package fglrx-core (not installed) failed to install/upgrade: trying to overwrite '/lib/fglrx/modprobe.conf', which is also in package fglrx 2:13.350.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1369307/+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 1194701] Re: fglrx-installer-13 freeze during X logout
Old, likely will not fix. ** Changed in: fglrx-installer (Ubuntu) Status: New = Invalid ** Attachment removed: BootDmesg.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714073/+files/BootDmesg.txt ** Attachment removed: xserver.outputs.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714094/+files/xserver.outputs.txt ** Attachment removed: XorgLogOld.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714093/+files/XorgLogOld.txt ** Attachment removed: XorgLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714092/+files/XorgLog.txt ** Attachment removed: XorgConf.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714091/+files/XorgConf.txt ** Attachment removed: UdevLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714090/+files/UdevLog.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714089/+files/UdevDb.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714088/+files/ProcModules.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714087/+files/ProcInterrupts.txt ** Attachment removed: BootLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714074/+files/BootLog.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714075/+files/CurrentDmesg.txt ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714076/+files/Dependencies.txt ** Attachment removed: DkmsStatus.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714077/+files/DkmsStatus.txt ** Attachment removed: DpkgLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714078/+files/DpkgLog.txt ** Attachment removed: GconfCompiz.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714079/+files/GconfCompiz.txt ** Attachment removed: LightdmDisplayLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714080/+files/LightdmDisplayLog.txt ** Attachment removed: LightdmGreeterLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714081/+files/LightdmGreeterLog.txt ** Attachment removed: LightdmGreeterLogOld.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714082/+files/LightdmGreeterLogOld.txt ** Attachment removed: LightdmLog.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714083/+files/LightdmLog.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714084/+files/Lspci.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714085/+files/Lsusb.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+attachment/3714086/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1194701 Title: fglrx-installer-13 freeze during X logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1194701/+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 1308105] Re: Xfce resets TV mode to NULL when power cycled
Thanks Straximus, that worked for me too. -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1308105] Re: Xfce resets TV mode to NULL when power cycled
^No AMD owns ATI, the other major graphics card provider. I am also experiencing this problem on integrated Intel graphics on Xubuntu 14.04 when using HDMI. It's the first distro I have used on this system but I never had the problem on Xubuntu 12.04 on my previous sytem (which was VGA/D-sub). I do not get 'NULL' in my /var/log/Xorg.0.log but the issue is basically the same problem. I do get null in dmesg however: [code][0.152426] ACPI: SSDT (null) 0004C4 (v01 PmRef Cpu0Ist 3000 INTL 20061109) [0.153472] ACPI: SSDT (null) 000433 (v01 PmRef Cpu0Cst 3001 INTL 20061109) [0.160066] ACPI: SSDT (null) 00015F (v01 PmRefApIst 3000 INTL 20061109) [0.163743] ACPI: SSDT (null) 8D (v01 PmRefApCst 3000 INTL 20061109)[/code] -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1311889] [NEW] App launcher icons don't respond
Public bug reported: Left click on an app icon in the launcher bar works fine on first use. After closing the app, it is impossible to open the app again by left click. The only way to open the same app is to right click and select the open option from the menu. Software updater would not launch after notifying me by being highlighted that updates were available. It was necessary to use apt-get in terminal to update. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 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: Wed Apr 23 22:27:47 2014 DistUpgraded: 2014-04-22 20:30:06,232 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516/M62-S [Mobility Radeon X1350] [1002:7196] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30d7] InstallationDate: Installed on 2013-08-21 (245 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) MachineType: Hewlett-Packard HP Compaq 6820s ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0f70fc5d-bedc-4a3f-b7f8-707f56830f71 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-22 (1 days ago) dmi.bios.date: 04/14/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MDD Ver. F.0A dmi.board.name: 30D7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 83.13 dmi.chassis.asset.tag: CNU8313FRT dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MDDVer.F.0A:bd04/14/2008:svnHewlett-Packard:pnHPCompaq6820s:pvrF.0A:rvnHewlett-Packard:rn30D7:rvrKBCVersion83.13:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6820s dmi.product.version: F.0A dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 23 21:02:54 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon ** 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/1311889 Title: App launcher icons don't respond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311889/+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 987401] Re: Ubuntu should poweroff video cards not in use
Good news that the code to enable this has finaly landed in Linux. Unfortunately, I don't have access to the hardware where this bug was initially reported against, so I cannot test this new functionality -- 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/987401 Title: Ubuntu should poweroff video cards not in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987401/+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 890061] Re: Nouveau thinks secondary DVI connection is HDMI - monitor blank
I no longer see the problem on Ubuntu 13.10. Both monitors show as DVI connected and both work fine. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/890061 Title: Nouveau thinks secondary DVI connection is HDMI - monitor blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/890061/+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 1226039] [NEW] frequency of gpu hangs increased dramatically over the weekend
Public bug reported: I am somewhat used to having GPU lockups hang X for me maybe once a week. I've followed a few vague bugs on the problem, but over the past weekend this has grown to every couple of hours. Easy ways to trigger it: changing workspaces too quickly while there is disk activity, or letting the screensaver go into power saving mode on the screen. The last one requires a hard reboot and I end up with the screen in a very dim state after the boot. Have a kern.log, if it helps. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,snap,gnomecompat,grid,regex,mousepoll,compiztoolbox,resize,move,wall,animation,vpswitch,place,imgpng,workarounds,expo,fade,ezoom,session,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 16 14:03:35 2013 DistUpgraded: 2013-03-19 10:32:34,118 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/python-novaclient_1%3a2.11.1-0ubuntu1_all.deb': 'subprocess new pre-removal script returned error exit status 1' DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] MachineType: LENOVO 7465CTO MarkForUpload: True ProcKernelCmdLine: root=UUID=5237fceb-23d0-412d-84d9-b8f8b3bf28af ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-03-19 (181 days ago) dmi.bios.date: 06/25/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET55WW (3.05 ) dmi.board.name: 7465CTO 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:bvr6DET55WW(3.05):bd06/25/2009:svnLENOVO:pn7465CTO:pvrThinkPadX200s:rvnLENOVO:rn7465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7465CTO dmi.product.version: ThinkPad X200s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Sep 16 13:31:40 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6.1 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring third-party-packages ubuntu ** Attachment added: kern.log https://bugs.launchpad.net/bugs/1226039/+attachment/3823690/+files/kern.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/1226039 Title: frequency of gpu hangs increased dramatically over the weekend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1226039/+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 1195705] Re: fglrx kernel module fails to build on kernel 3.10 [error: implicit declaration of function ‘create_proc_entry’]
This bug also exists in fglrx-13 from xorg-edgers @ https://launchpad.net/~xorg-edgers/+archive/ppa Not entirely sure where fglrx bugs go. I've also reported at: http://ati.cchtml.com/show_bug.cgi?id=847 ** Bug watch added: ATi Linux Platform Bugs #847 http://ati.cchtml.com/show_bug.cgi?id=847 ** Also affects: fglrx via http://ati.cchtml.com/show_bug.cgi?id=847 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1195705 Title: fglrx kernel module fails to build on kernel 3.10 [error: implicit declaration of function ‘create_proc_entry’] To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1195705/+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 1194701] [NEW] fglrx-installer-13 freeze during X logout
Public bug reported: Running a new ASUS EAH6670 on Raring, seems to have frozen w/ kernel spinning in X during logoff. htop shows an unkillable spinning thread (100% CPU, all in kernel) of: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [11139.483689] AMD IOMMUv2 driver by Joerg Roedel joerg.roe...@amd.com [11139.483705] AMD IOMMUv2 functionality not available on this system [11139.489082] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [11139.500983] 6[fglrx] Maximum main memory to use for locked dma buffers: 7724 MBytes. [11139.501148] 6[fglrx] vendor: 1002 device: 6758 count: 1 [11139.501449] 6[fglrx] ioport: bar 4, base 0xe000, size: 0x100 [11139.501631] 6[fglrx] Kernel PAT support is enabled [11139.501649] 6[fglrx] module loaded - fglrx 13.10.10 [May 23 2013] with 1 minors [11139.563367] [ cut here ] [11139.563374] WARNING: at /build/buildd/linux-3.8.0/drivers/pci/msi.c:834 pci_enable_msi_block+0x2a4/0x2b0() [11139.563375] Hardware name: To be filled by O.E.M. [11139.563376] Modules linked in: fglrx(POF) amd_iommu_v2 nls_utf8 isofs(F) iptable_nat(F) nf_nat_ipv4(F) ip_tables(F) nf_nat(F) x_tables(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) nf_conntrack_netlink(F) nf_conntrack(F) nfnetlink_log(F) nfnetlink(F) dm_crypt(F) kvm_intel kvm snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) snd_rawmidi(F) snd_seq(F) snd_seq_device(F) tpm_infineon snd_timer(F) snd(F) soundcore(F) microcode(F) tpm_tis xgifb(C) ppdev(F) psmouse(F) lpc_ich parport_pc(F) parport(F) serio_raw(F) mac_hid w83627ehf tcp_htcp(F) hwmon_vid coretemp raid456(F) async_memcpy(F) async_raid6_recov(F) async_pq(F) async_xor(F) xor(F) async_tx(F) raid6_pq(F) raid0(F) multipath(F) linear(F) raid1(F) raid10(F) hid_generic usbhid hid ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) xts(F) lrw(F) gf128mul(F) ablk_helper(F) cryptd(F) radeon video(F) i2c_algo_bit ttm drm_kms_helper e1000e(F) drm [11139.563410] Pid: 12541, comm: Xorg Tainted: PFC O 3.8.0-26-generic #38-Ubuntu [11139.563410] Call Trace: [11139.563414] [810587ef] warn_slowpath_common+0x7f/0xc0 [11139.563416] [8105884a] warn_slowpath_null+0x1a/0x20 [11139.563417] [81391bc4] pci_enable_msi_block+0x2a4/0x2b0 [11139.563452] [a085bbb3] KCL_RequestMSI+0x13/0x20 [fglrx] [11139.563480] [a087d3cf] IRQMGR_initialize+0x24f/0x380 [fglrx] [11139.563509] [a087d127] ? IRQMGR_alloc_context+0xb7/0x110 [fglrx] [11139.563537] [a087bd72] ? irqmgr_wrap_initialize+0x22/0xc0 [fglrx] [11139.563565] [a087cf23] ? firegl_irqmgr_init+0x53/0x100 [fglrx] [11139.563595] [a088de7f] ? hal_init_gpu+0x1cf/0x480 [fglrx] [11139.563619] [a08689fb] ? firegl_open+0x2db/0x310 [fglrx] [11139.563637] [a0858ab7] ? ip_firegl_open+0x17/0x20 [fglrx] [11139.563654] [a0858135] ? firegl_stub_open+0xa5/0x120 [fglrx] [11139.563657] [81198bdf] ? chrdev_open+0xaf/0x1a0 [11139.563659] [81192793] ? do_dentry_open+0x203/0x290 [11139.563660] [81198b30] ? cdev_put+0x30/0x30 [11139.563662] [81192869] ? vfs_open+0x49/0x50 [11139.563663] [811a1426] ? do_last+0x296/0xea0 [11139.563665] [8119ed78] ? inode_permission+0x18/0x50 [11139.563666] [811a088b] ? link_path_walk+0x6b/0x880 [11139.563669] [8117cc8d] ? kfree+0xdd/0x110 [11139.563670] [811a2f43] ? path_openat+0xb3/0x4b0 [11139.563695] [a0866dab] ? firegl_release_helper+0x3eb/0x6c0 [fglrx] [11139.563696] [811a3d41] ? do_filp_open+0x41/0xa0 [11139.563698] [811b14c9] ? __alloc_fd+0xd9/0x130 [11139.563700] [81193b23] ? do_sys_open+0xf3/0x230 [11139.563701] [81193c81] ? sys_open+0x21/0x30 [11139.563704] [816d495d] ? system_call_fastpath+0x1a/0x1f [11139.563705] ---[ end trace d75520ae5348e0e0 ]--- [11139.563723] radeon :01:00.0: irq 50 for MSI/MSI-X [11139.563728] radeon :01:00.0: irq 51 for MSI/MSI-X [11139.563733] [ cut here ] [11139.563736] WARNING: at /build/buildd/linux-3.8.0/fs/sysfs/dir.c:536 sysfs_add_one+0xd4/0x100() [11139.563736] Hardware name: To be filled by O.E.M. [11139.563737] sysfs: cannot create duplicate filename '/devices/pci:00/:00:01.0/:01:00.0/msi_irqs' [11139.563738] Modules linked in: fglrx(POF) amd_iommu_v2 nls_utf8 isofs(F) iptable_nat(F) nf_nat_ipv4(F) ip_tables(F) nf_nat(F) x_tables(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) nf_conntrack_netlink(F) nf_conntrack(F) nfnetlink_log(F) nfnetlink(F) dm_crypt(F) kvm_intel kvm snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F)
[Ubuntu-x-swat] [Bug 1173491] Re: Boot to Safe Graphics after upgrade to Raring
Thanks for the advice, Chris! The --newmode/--addmode arguments will be very useful. I do want to use that mode quite badly, as the display represents all other resolutions I tried (of which there were many on the older kernels) very badly. I presently cannot remember on what basis I concluded that 14x9 was the display's actual native resolution, so I can't claim I'm certain that that is correct. However, I am quite certain that the actual native resolution is not on the list of detected resolutions. I will try to back my claims up with something solid (however, it will have to wait till tomorrow, at least, as I am not presently near the system in question). I did try analysing the EDID data, using the read-edid tools from http://www.polypux.org/projects/read-edid/ . The tools did complain that there was something unexpected about the EDID data and that it was probably bad. Thus I suspect that the EDID data is indeed bad and that something changed about how faulty data is handled between kernel 3.7 and 3.8, causing the previously detected modes (of which there were many more) to no longer be detected. As for the additional logs of the working 14x9 mode: If you are still interested in them, then I will be happy to try and produce/collect them, when I get back to the affected system. I am not quite clear on what you are after, though. If you are just interested in a set of logs where the system successfully booted with light-dm switching to the 14x9 mode, then the original set of logs I uploaded seems to be what you are looking for. In particular, you can see: [+1.57s] DEBUG: Connecting to XServer :0 [+1.57s] DEBUG: Launching process 1674: xrandr --output HDMI2 --primary --mode 1440x900 [+2.59s] DEBUG: Process 1674 exited with return value 0 [+2.59s] DEBUG: Exit status of xrandr --output HDMI2 --primary --mode 1440x900: 0 [+2.59s] DEBUG: Starting greeter That just shows that it didn't mind using the mode in question on kernel 3.7 (at least on RC8). However, I suspect that you were after something more specific. If so, please let me know. Thanks for all your help, Chris! -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658592/+files/Dependencies.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Re: Boot to Safe Graphics after upgrade to Raring
apport information ** Tags added: apport-collected ** Description changed: Graphics worked in Precise. After upgrading, lightdm does not load, but the safe graphics mode dialog is displayed, instead This dialog fails to accomplish anything other than allowing me to exit to a terminal and I thus cannot use the system in graphical mode at all (even safe graphics). Booting an older pre-upgrade kernel still works (hence the odd kernel version collected by apport). The display (a TV) is connected via HDMI to the integrated intel graphics adapter. May be related to potentially dodgy EDID information from the display (even in Precise, the selected default resolution is not the native resolution of the display and I have to manually adjust it). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8 Uname: Linux 3.7.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 CurrentDmesg: Date: Sat Apr 27 14:53:20 2013 DistUpgraded: 2013-04-26 17:47:28,463 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2111] InstallationDate: Installed on 2012-07-14 (287 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: MSI MS-7758 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-5-generic root=UUID=4cb92e57-8f73-4490-8da4-2b6c1369e72d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-04-26 (0 days ago) dmi.bios.date: 02/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1:bd02/20/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 27 14:40:11 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel + --- + ApportVersion: 2.9.2-0ubuntu8 + 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] + CurrentDmesg: [ 18.317458] init: plymouth-ready (started) main process (882) terminated with status 1 + DistUpgraded: 2013-04-26 17:47:28,463 DEBUG enabling apt cron job + DistroCodename: raring + DistroRelease: Ubuntu 13.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) +Subsystem: Micro-Star International Co., Ltd. Device [1462:2111] + InstallationDate: Installed on 2012-07-14 (289 days ago) + InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) + MachineType: MSI MS-7758 + MarkForUpload: True + Package: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=4cb92e57-8f73-4490-8da4-2b6c1369e72d ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 + Tags:
[Ubuntu-x-swat] [Bug 1173491] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658605/+files/XorgLogOld.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658596/+files/Lsusb.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658598/+files/ProcEnviron.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658599/+files/ProcInterrupts.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] xserver.devices.txt
apport information ** Attachment added: xserver.devices.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658606/+files/xserver.devices.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658597/+files/ProcCpuinfo.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658595/+files/Lspci.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658601/+files/UdevDb.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658594/+files/GconfCompiz.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658591/+files/BootLog.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658604/+files/XorgLog.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658600/+files/ProcModules.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658603/+files/UdevLog.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] xserver.outputs.txt
apport information ** Attachment added: xserver.outputs.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658607/+files/xserver.outputs.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1173491/+attachment/3658593/+files/DpkgLog.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Re: Boot to Safe Graphics after upgrade to Raring
You are correct Chris, the original logs were indeed from a working session. I did not consider that they might only cover one session - my apologies, I hope I have not wasted anyone's time! As you can see by the spam :S it looks like I successfully ran apport- collect from the VT... I had to guess a bit with interactive prompts, due to screen clipping, but I don't think I could have done anything too stupid there. -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Re: Boot to Safe Graphics after upgrade to Raring
An interesting thing I noticed is that, upon login into the VT, ubuntu tells me that there is a new release available (13.04) and that I sould use do-release-upgrade to upgrade to it. Perhaps something went wrong in the upgrade process. Actually trying to run do-release-upgrade tells me that there is no new version, though, and dpkg --configure -a does not pick anything up. -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Re: Boot to Safe Graphics after upgrade to Raring
Ahhh, given what you just mentioned, I remembered that I had added a line to /etc/lightdm/lightdm.conf, in order to force light-dm to use the native resoltution of the display: display-setup-script=xrandr --output HDMI2 --primary --mode 1440x900 This was returning a failure code, causing light-dm to terminate. The reason for this, in turn, appears to be that the native resolution is no longer being detected at all! Upon lgging into my graphical session I was greeted by a bad resulution and a very long error dialog box, spanning multiple screens (text attached). I am unable to select the native resolution, which leaves me with cropped display output. I guess this means that the original issue was effectively my fault, although it stems from the underlying issue that the supported modes are no longer being detected correctly. Of course it is still possible that this is due to bad EDID info from the display, but the fact remains that the older kernel is able to drive the display at its native resolution. (The reason the log was missing from my uploads was presumably because I didn't think apport needed to run as root. As it turns out, the light-dm logs are only readable by root. Apport didn't warn me / complain about this, so I assumed everyting was fine.) ** Attachment added: ModeErrorDialog.txt https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+attachment/3658734/+files/ModeErrorDialog.txt -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] Re: Boot to Safe Graphics after upgrade to Raring
Thanks Timo, Unfortunately, the kernel you linked does not appear to work any better. -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1173491/+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 1173491] [NEW] Boot to Safe Graphics after upgrade to Raring
Public bug reported: Graphics worked in Precise. After upgrading, lightdm does not load, but the safe graphics mode dialog is displayed, instead This dialog fails to accomplish anything other than allowing me to exit to a terminal and I thus cannot use the system in graphical mode at all (even safe graphics). Booting an older pre-upgrade kernel still works (hence the odd kernel version collected by apport). The display (a TV) is connected via HDMI to the integrated intel graphics adapter. May be related to potentially dodgy EDID information from the display (even in Precise, the selected default resolution is not the native resolution of the display and I have to manually adjust it). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8 Uname: Linux 3.7.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 CurrentDmesg: Date: Sat Apr 27 14:53:20 2013 DistUpgraded: 2013-04-26 17:47:28,463 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2111] InstallationDate: Installed on 2012-07-14 (287 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: MSI MS-7758 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-5-generic root=UUID=4cb92e57-8f73-4490-8da4-2b6c1369e72d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-04-26 (0 days ago) dmi.bios.date: 02/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.1:bd02/20/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 27 14:40:11 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1173491/+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 1173491] Re: Boot to Safe Graphics after upgrade to Raring
Please let me know if I can provide further helpful information. (Or if imdoinitwrong.) -- 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/1173491 Title: Boot to Safe Graphics after upgrade to Raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1173491/+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 1068994] Re: button1 gets stuck after a while
Wait how do I go about installing the fixed stuff -- 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/1068994 Title: button1 gets stuck after a while To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+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 813809] Re: Hybrid Graphics with Intel+fglrx is not supported
For anyone wanting to work on this issue, you might want to take a look on these bugs: https://bugs.launchpad.net/ubuntu/+bug/1068404 This was about the initial X-server crash and it was an incompatibility of the fglrx driver with the intel one. The solution is to install fglrx 13.1+ which should prevent that error form happening. You can follow the full discussion on the bug, or take a summary in the attached novell bug: https://bugzilla.novell.com/show_bug.cgi?id=780672 After fixing the above bug, there is another of periodic crashes (but not segmentation faults) which is described here: https://bugs.launchpad.net/fglrx/+bug/1088220 It seems to be provoked by an invalid key in the amdpcsdb database, a workaround is included in the bug description (and the atached ati bug). Good luck! PS: I can no longer help on these bugs unfortunately as I do not access to an fglrx/intel system any more :( ** Bug watch added: Novell/SUSE Bugzilla #780672 https://bugzilla.novell.com/show_bug.cgi?id=780672 -- 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/813809 Title: Hybrid Graphics with Intel+fglrx is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/813809/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
Guys just a small remark. I have changed laptop and I don't have my intel/ati system any more. So, I won't be able to troubleshoot any more :( Nick -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1153734] Re: Corrupt graphics on Ubuntu 13.04
I would try but i've just broken my system. added trim command in bootup and disabled writing reports to make my SSD last longer however I now have no desktop, blank screen. I've undone these changes but ctrl-alt-f7 (still with random curruptions but no desktop). seen another post somewhere which'll give me the command to start the desktop.. I'll try this then try apport-collect, it does feel like graphics... -- 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/1153734 Title: Corrupt graphics on Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1153734/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
Yes, you are probably right, I'm hiding my comment on the other bug Thanks for pointing it out! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
Try to install this version 2:12.100.3-0~andrik1 (for both fglrx-updates and fglrx-amdcccle-updates) and remove the updated intel driver. Just the updated fglrx driver should work -- =Do- N.AND -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
Marco, I think the periodic crashes refer to the Bug #1088220 which still remains. At least the new (13.1+) drivers seem to solve the initial segmentation fault, is that right? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
I think the intel driver is out of this bug and should be marked as invalid. The solution relies in the fglrx driver. I have tried the 13.2beta3 driver and it solves the problem. If we don't want to go for this version, a Suse user on the corresponding attached bug, reported that also 13.1 is ok. I have already packaged the 13.2beta3 version here: https://launchpad.net/~andrikos/+archive/xserver/ Should I also prepare an official branch to propose for merging to quantal-proposed? -- =Do- N.AND -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
** Branch linked: lp:~andrikos/ubuntu/quantal/fglrx-installer-updates /fix-fglrx-intel-hybrid ** Branch unlinked: lp:~andrikos/ubuntu/quantal/fglrx-installer/fix- switch-to-igpu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
And this is the new merge request of 13.2beta3 for quantal-proposed: https://code.launchpad.net/~andrikos/ubuntu/quantal/fglrx-installer-updates/fix-fglrx-intel-hybrid/+merge/148950 ** Branch unlinked: lp:~andrikos/ubuntu/quantal/xserver-xorg-video-intel /fix-ati-hybrid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
And this is the new merge request of 13.2beta3 for quantal-proposed: https://code.launchpad.net/~andrikos/ubuntu/quantal/fglrx-installer-updates/fglrx-13.2-beta3/+merge/148950 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
** Description changed: [Impact] * Hybrid systems with ATI/intel GPUs using fglrx get a segmentation fault in X when using 12.10. In stock 12.04.1 these systems were working fine. * This bug represents a severe regression from precise to quantal, since is crashing on startup - * The proposed patch reverts the following upstream commit which has hidden some global symbols of the intel driver: - http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=05dcc5f1699ba90fc14c50882e8d4be89bc4a4f9 + * The proposed patch updates the driver to version 13.2beta3 of + upstream which seems to resolve this issue [Test Case] * Get an hybrid ATI/intel system. Install quantal: The system should boot fine Install the proprietary fglrx package and reboot: The X server crashes on startup [Regression Potential] - * Although upstream has stated that reverting this patch should be safe enough (mainly Comment 7): - https://bugs.freedesktop.org/show_bug.cgi?id=56494#c6 - it seems that it can cause X server to crash if radeon/intel system is used (without fglrx). This is a regression for the default configuration so the proposed patch is not suitable for SRU + * This solution does not need any change on the intel driver (as a previous workaround needed). + * No regressions have been reported so far using this most recent fglrx upstream, from the people affected by this bug == After installing the latest fglrx-updates package on Ubuntu 12.10 (fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was present before AMD fixed switchable graphics on PowerXpress 4.0 cards (such as my HD 6470M coupled with the intel HD Graphics 3000 of my intel Core i5-2430M). The X server has a segmentation fault and the low graphics mode is activated. WORKAROUND: Follow carefully the instructions here: https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND As per Nick Andrik, this is a version regression of xserver-xorg-video- intel from 2.20.2 (working and in below mentioned PPA) and 2.20.3. The regression commit is http://cgit.freedesktop.org/xorg/driver/xf86-video- intel/commit/?id=05dcc5f1699ba90fc14c50882e8d4be89bc4a4f9 . + + Upstream fglrx has published a new version ( 13.1 ) of the driver which + seems to solve this issue. No need to revert the commit in the Intel + driver any more. ATTENTION: 1. If you choose the integrated GPU (via Catalyst or via amdconfig --px-igpu) and your X server crashes on startup, then your are probably affected by this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220 2. If your system includes an old ATI GPU card (Radeon HD 2x00 3x00 4x00) which is not supported any more by fglrx drivers, then probably you suffer from this bug: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1058040 Subscribe and comment there please. If the X server loads (so you see no low graphics mode window) but you get no menu bars, window decorations, etc, then press Ctrl+Shift+T to open a terminal, write in there: unity --replace and post a comment with the result. The logs from the intial bug report follow: Here is the Xorg log: [20.924] X.Org X Server 1.13.0 Release Date: 2012-09-05 [20.924] X Protocol Version 11, Revision 0 [20.924] Build Operating System: Linux 3.2.0-30-generic x86_64 Ubuntu [20.924] Current Operating System: Linux marco-HP-Pavilion-g6-Notebook-PC 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 [20.924] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=5374f779-2ae8-4842-a390-e21317364c6c ro quiet splash vt.handoff=7 [20.924] Build Date: 08 October 2012 03:34:01PM [20.924] xorg-server 2:1.13.0-0ubuntu6 (For technical support please see http://www.ubuntu.com/support) [20.924] Current version of pixman: 0.26.0 [20.924] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [20.924] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [20.924] (==) Log file: /var/log/Xorg.0.log, Time: Fri Oct 19 02:42:21 2012 [20.924] (==) Using config file: /etc/X11/xorg.conf [20.924] (==) Using system config directory /usr/share/X11/xorg.conf.d [20.924] (==) ServerLayout aticonfig Layout [20.924] (**) |--Screen aticonfig-Screen[0]-0 (0) [20.924] (**) | |--Monitor aticonfig-Monitor[0]-0 [20.925] (**) | |--Device aticonfig-Device[0]-0 [20.925] (==) Automatically adding devices [20.925] (==) Automatically enabling devices [20.925] (==) Automatically adding GPU devices [20.925] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [20.925
[Ubuntu-x-swat] [Bug 1068404]
It seems that the fglrx 12.3-beta3 driver solves this issus without any patch needed for the intel driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404]
Yes, I menat the 13.2, not 12.3, sorry. I packaged and tried that version for ubuntu and it seems to resolve the problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade
I have packaged the latest beta version from upstream 13.2-beta3 in my PPA: https://launchpad.net/~andrikos/+archive/xserver/ In my system, this version resolves the problem without the need to change anything in the intel driver (just use the default 2:2.20.9-0ubuntu2 version shipping in quantal). Could anyone please test the packages in your systems in order to see if it is a proper fix and if any regressions appear? Thanks, Nick -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1068404 Title: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1068404/+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 1088220] Re: Periodic Xserver crash when using integrated GPU in flgrx/Intel systems
I have packaged the latest beta version from upstream 13.2-beta3 in my PPA: https://launchpad.net/~andrikos/+archive/xserver/ In my system, this version resolves the problem without the need to change anything in the intel driver (just use the default 2:2.20.9-0ubuntu2 version shipping in quantal). Could anyone please test these packages in your systems in order to see if this is a proper fix and if any regressions appear? Thanks, Nick -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1088220 Title: Periodic Xserver crash when using integrated GPU in flgrx/Intel systems To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1088220/+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 1088220] Re: Periodic Xserver crash when using integrated GPU in flgrx/Intel systems
workaround not working: the message is:Error: Key DDX,PX_GPUDOWN not found in PCS database Do you still get the crash if you reboot after you get this error? Nick -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1088220 Title: Periodic Xserver crash when using integrated GPU in flgrx/Intel systems To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1088220/+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
