[Ubuntu-x-swat] [Bug 1337749] Re: High CPU usage after resizing a window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- 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/1337749 Title: High CPU usage after resizing a window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1337749/+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 1307877] Re: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor.
i confirm this bug. I cant adjust the brightness after second monitor unplug. -- 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/1307877 Title: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1307877/+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 1271410] Re: screen brightness does not work after removal of second monitor
i confirm this bug. I cant adjust the brightness after second monitor unplug. -- 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/1271410 Title: screen brightness does not work after removal of second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1271410/+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 1337749] Re: High CPU usage after resizing a window
A further comment: I noticed this bug report here which seems to report a similar issue https://bugs.launchpad.net/compiz/+bug/1293384 I also figured out that even moving the mouse around causes high CPU usage. For example, launch Nautilus and move the mouse around inside it for 15-20 seconds or so. My CPU usage jumps to 25% for Xorg, 25% for nautilus, and 15% for compiz. Same thing happens with other programs like Firefox. So I searched around some more and found this bug report: https://bugs.launchpad.net/xorg-server/+bug/1250277 It seems that there's a chance all of these bug reports might be related. I will test on my office PC soon, which has an nvidia card, and report back. -- 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/1337749 Title: High CPU usage after resizing a window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1337749/+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 1340556] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1188123 *** https://bugs.launchpad.net/bugs/1188123 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1188123, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1340556/+attachment/4150161/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1340556/+attachment/4150164/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1340556/+attachment/4150175/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1340556/+attachment/4150177/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1340556/+attachment/4150178/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1340556/+attachment/4150179/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1340556/+attachment/4150180/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1188123 Xorg crashed with SIGABRT in OsAbort() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1340556 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1340556/+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 1337749] Re: High CPU usage after resizing a window
It also has something to do with firefox. Chrome do not use this much CPU. -- 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/1337749 Title: High CPU usage after resizing a window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1337749/+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 1340582] [NEW] Crash when switching user
Public bug reported: I already saw this bug reported but I just wanted to add my logs ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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 CurrentDesktop: Unity Date: Fri Jul 11 10:07:58 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca] NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:8094] InstallationDate: Installed on 2014-07-01 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=2006c8c3-d123-4c76-8a6e-339163a6fa92 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd09/22/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB75M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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.1 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: Fri Jul 11 09:54:01 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) [drm] KMS not enabled xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40971 vendor DEL xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340582 Title: Crash when switching user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340582/+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 1179617] [NEW] qmlscene assert failure: qmlscene: ../../src/xcb_conn.c:180: write_vec: Assertion `!c-out.queue_len' failed.
You have been subscribed to a public bug: - Spontaneous crash without any apparent reason. - Except the web browser, no application was in use at the moment of the crash. Thanks fabio ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: qmlscene 5.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 ApportVersion: 2.10-0ubuntu3 Architecture: amd64 Date: Mon May 13 20:02:17 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-12 (213 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20121011) MarkForUpload: True SourcePackage: qtdeclarative-opensource-src UpgradeStatus: Upgraded to saucy on 2013-05-01 (11 days ago) ** Affects: qt Importance: Medium Status: Fix Released ** Affects: libxcb (Ubuntu) Importance: High Status: Incomplete ** Tags: amd64 apport-bug saucy -- qmlscene assert failure: qmlscene: ../../src/xcb_conn.c:180: write_vec: Assertion `!c-out.queue_len' failed. https://bugs.launchpad.net/bugs/1179617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxcb in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1179617] Re: qmlscene assert failure: qmlscene: ../../src/xcb_conn.c:180: write_vec: Assertion `!c-out.queue_len' failed.
I'm not sure if this is still reproducable with Qt 5.3.0, but the upstream seems to point to the libxcb upstream bug which now has a fix. Another Qt bug linked to the upstream Qt bug report was also reported fixed in Qt 5.3.0. ** Package changed: qtdeclarative-opensource-src (Ubuntu) = libxcb (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1179617 Title: qmlscene assert failure: qmlscene: ../../src/xcb_conn.c:180: write_vec: Assertion `!c-out.queue_len' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1179617/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
Hi Chih-Hsyuan, you also can try to give the log file to us. -- 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/1315285 Title: [AMD Richland + Mars] Unable to switch graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1314551] Re: 1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption
I've had similar problems. Regarding comment #7, 12.04 was not affected, I first saw the problem after upgraded to 13.10 (I didn't use 12.10 or 13.04 so can't say it they were affected). The problem persisted after upgrading to 14.04. I've had the same problem affected both open source ATI and open source Nvidia drivers (on different machines). In both cases problem ceases to exist after installing proprietary drivers. As mentioned in comment #5 just installing fglrx from Ubuntu repository borks the 14.04, I've installed proprietary drivers downloaded directly from AMD.com. -- 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/1314551 Title: 1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314551/+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 1340648] [NEW] bumblebee nvidia-driver doesn`t detect discrete graphic card
Public bug reported: After update xserver-xorg-core xserver-xorg-common 1.14.5 to 1.14.6, GPU PCI ID is correct in xserver conf bumblebee co f is also correct, with xserver 1.15.1 all work fine. ** Affects: xorg-server-lts-saucy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server-lts-saucy in Ubuntu. https://bugs.launchpad.net/bugs/1340648 Title: bumblebee nvidia-driver doesn`t detect discrete graphic card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-saucy/+bug/1340648/+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 1033533] Re: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1033533 Title: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1033533/+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
tl;dr - There is a bug in xfsettingsd that not only affects external monitors, but primary monitors as well. I believe that I am encountering the same bug, but by a different scenario. This may also be the same bug as #1313539. I am running Xubuntu 14.04 on two of my four computers. I have all four computers connected to a single keyboard, monitor and mouse via a 4port KVM switch. Prior 14.04 upgrade, this setup worked like a dream. Post 14.04 upgrade, I have found that switching to either of the Xubuntu machines results in a blank monitor. On one machine, I am usually able to get to a virtual console and reset of the video by restarting lightdm. On the other machine, I am not able to even get a virtual console, and I have to ssh into the machine in order to restart lightdm. The dying video happens so frequently that I starting the process of migrating away to XFCE. I installed Gnome Shell on one machine and Fluxbox on the other. Neither of these WM's exhibited the dying video phenomena. Based upon this bug report, I decided to investigate the possibility that xfsettingsd might be the problem. Here's what I did. 1) Log in to a Xubuntu session. 2) Open a terminal window. Because I needed to do part of this from the Xubuntu session and part of this via ssh, I opened a new Byobu session (screen or tmux would work too). Then, $ killall xfsettingsd $ XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon 21 | tee output.txt 3) After the initial output from xfsettingsd had finished, $ cp output.txt before.txt 4) Here's where the fun begins: I unplugged the monitor from the KVM switch. I waited a few seconds, and then I plugged the monitor back into the switch. No video. I switched the KVM to one of the other computers and verified that the monitor was corrected plugged in and working. 5) On one of the other computers with working video, I ssh'ed into the machine running the Xubuntu session and reconnected to the Byobu session. I found that xfsettingsd had crashed. 6) Executing sleep 5; xfsettingsd on the ssh session and switching to the Xubuntu machine restored the video. 7) I diff'ed the before.txt with the output.txt. Here is the output that was generated when the monitor was unplugged and replugged. xfce4-settings(displays): RRScreenChangeNotify event received. xfce4-settings(displays): Refreshing RandR cache. xfce4-settings(displays): Detected CRTC 63. xfce4-settings(displays): Detected CRTC 64. xfce4-settings(displays): Detected CRTC 65. xfce4-settings(displays): Noutput: before = 1, after = 0. xfce4-settings(displays): Output disconnected: VGA1 xfce4-settings(displays): Disabling CRTC 63. xfce4-settings(displays): No active output anymore! Attempting to re-enable the internal output. xfce4-settings(displays): RRScreenChangeNotify event received. xfce4-settings(displays): Refreshing RandR cache. xfce4-settings(displays): Detected CRTC 63. xfce4-settings(displays): Detected CRTC 64. xfce4-settings(displays): Detected CRTC 65. xfce4-settings(displays): Noutput: before = 0, after = 0. xfce4-settings(displays): RRScreenChangeNotify event received. xfce4-settings(displays): Refreshing RandR cache. xfce4-settings(displays): Detected CRTC 63. xfce4-settings(displays): Detected CRTC 64. xfce4-settings(displays): Detected CRTC 65. xfce4-settings(displays): Detected output 66 VGA1. xfce4-settings(displays): Noutput: before = 0, after = 1. xfce4-settings(displays): New output connected: VGA1 xfce4-settings(displays): RRScreenChangeNotify event received. xfce4-settings(displays): Refreshing RandR cache. xfce4-settings(displays): Detected CRTC 63. xfce4-settings(displays): Detected CRTC 64. xfce4-settings(displays): Detected CRTC 65. xfce4-settings(displays): Noutput: before = 1, after = 0. xfce4-settings(displays): Output disconnected: VGA1 xfce4-settings(displays): Disabling CRTC 89. The program 'xfsettingsd' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRRCrtc (invalid Crtc parameter)'. (Details: serial 505 error_code 148 request_code 140 minor_code 21) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- 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 :
[Ubuntu-x-swat] [Bug 1340719] [NEW] Mouse droppings on radeon-controlled screen
Public bug reported: I have a two-monitor setup, one driven by the onboard Intel graphics, and the other by an ATI HD 5450-powered card, using the radeon driver. When I move the mouse pointer over the second, radeon-driven screen, I get mouse droppings. I tried to take a screenshot showing this, but the process of taking the screenshot (by pressing PrtSc) clears up the droppings. So does clicking on a window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:21:46 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption trusty -- 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/1340719 Title: Mouse droppings on radeon-controlled screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340719/+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 1340722] [NEW] Screen order cannot be configured correctly
Public bug reported: I have two screens driven by different graphics cards. I configure them in Screen Display settings to have the radeon-driven secondary screen on the left, and the intel-driven primary screen on the right. Every time I start up my computer and log in, they are the other way around (primary on the left, secondary on the right). This problem does not occur when I drive both monitors from the same graphics adaptor (but unfortunately I then get other problems!). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:29:34 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1340722 Title: Screen order cannot be configured correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340722/+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 1340716] [NEW] segfault at 8 ip 08051738 sp bf97f4e0 error 4 in xrandr[8048000+c000]
Public bug reported: Laptop's lid was closed during script to initialize external monitor and disable LVDS1. segfault at 8 ip 08051738 sp bf97f4e0 error 4 in xrandr[8048000+c000] Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 8192 x 8192 LVDS1 connected (normal left inverted right x axis y axis) 1366x768 60.0 + 1360x768 59.8 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 connected 1920x1200+2560+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 60.0*+ 1920x1080 60.0 1600x1200 60.0 1680x1050 60.0 1280x1024 60.0 1280x960 60.0 1024x768 60.0 800x60060.3 640x48060.0 720x40070.1 HDMI1 disconnected (normal left inverted right x axis y axis) DP1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 60.0*+ 1920x1200 59.9 1920x1080 60.0 60.0 50.0 59.9 24.0 24.0 1920x1080i 60.1 50.0 60.0 1600x1200 60.0 1680x1050 60.0 1280x1024 75.0 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 60.0 800x60075.0 60.3 720x57650.0 720x48060.0 59.9 640x48075.0 60.0 59.9 720x40070.1 HDMI2 disconnected (normal left inverted right x axis y axis) HDMI3 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) Intel (sandy bridge)'s graphics. dmesg during crash: [34112.801828] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34114.339578] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34114.351444] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34115.904452] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34115.910932] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34115.919048] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34117.555736] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34118.061252] xrandr[14813]: segfault at 8 ip 08051738 sp bf97f4e0 error 4 in xrandr[8048000+c000] [34118.488651] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34120.353155] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34120.365152] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34121.921496] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34121.933163] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34123.486506] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34123.493197] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34123.501321] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34125.054863] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34125.061363] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34125.069532] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34126.620808] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34126.627544] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34126.637193] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34128.194951] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34128.212203] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34131.392352] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34131.398781] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34131.409436] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34132.964217] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34134.515388] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34136.068077] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34137.618574] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34139.354699] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up [34139.368775] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34140.922575] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [34142.475539] [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: x11-xserver-utils 7.7+2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-31.55-generic
[Ubuntu-x-swat] [Bug 1340716] Re: segfault at 8 ip 08051738 sp bf97f4e0 error 4 in xrandr[8048000+c000]
Script: xrandr --output DP1 --auto xrandr --output LVDS1 --off xrandr --output VGA1 --auto xrandr --output DP1 --left-of VGA1 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1340716 Title: segfault at 8 ip 08051738 sp bf97f4e0 error 4 in xrandr[8048000+c000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1340716/+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 1340727] [NEW] Ubuntu starting problem
Public bug reported: I have three operating system installed like Windows XP, Windows 7 and Ubuntu. The default OS is Ubuntu. When I starting my computer, selection automatically highlighted to Windows 7 and then still. Again when I selected ubuntu and press enter, screen is repeatedly print the character and number like [4 . After some time screen continuously flickering and waiting for enter to stable the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-24.42-generic 3.11.10.11 Uname: Linux 3.11.0-24-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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 CurrentDmesg: [ 154.334931] alx :03:00.0 eth0: NIC Up: 100 Mbps Full [ 154.335592] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Fri Jul 11 17:57:19 2014 DistUpgraded: 2014-04-18 19:37:11,953 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-19-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-20-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-22-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-23-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-24-generic, i686: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-03-17 (115 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: LENOVO 20157 MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-24-generic root=UUID=5e48a462-c3a0-4975-88f1-55e1c0709172 ro splash plymouth:debug=1=1=1=1 quiet plymouth:debug=1=1 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2014-04-18 (83 days ago) dmi.bios.date: 07/27/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN40WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake 2 dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr62CN40WW:bd07/27/2012:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 20157 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1~saucy1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.6-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Jul 11 17:51:32 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16978 vendor SEC xserver.version: 2:1.14.6-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 saucy 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/1340727 Title: Ubuntu starting problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340727/+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 1315777] Re: TV displays no signal have turning off then back on.
*** This bug is a duplicate of bug 1308105 *** https://bugs.launchpad.net/bugs/1308105 ** This bug is no longer a duplicate of bug 1313443 Cannot restore HDMI display after regular TV session ** This bug has been marked a duplicate of bug 1308105 Xfce resets TV mode to NULL when power cycled -- 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/1315777 Title: TV displays no signal have turning off then back on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1315777/+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 1313443] Re: Cannot restore HDMI display after regular TV session
*** This bug is a duplicate of bug 1308105 *** https://bugs.launchpad.net/bugs/1308105 The workaround from the following bug fixed the issue for me: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1308105 Recommend making this a duplicate. ** This bug has been marked a duplicate of bug 1308105 Xfce resets TV mode to NULL when power cycled -- 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/1313443 Title: Cannot restore HDMI display after regular TV session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313443/+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 1331224] Re: Split Screen with latest ubuntu kernel update
*** This bug is a duplicate of bug 1339768 *** https://bugs.launchpad.net/bugs/1339768 ** This bug has been marked a duplicate of bug 1339768 VMWare graphics driver regression -- 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/1331224 Title: Split Screen with latest ubuntu kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1331224/+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 1340888] Re: gnome
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1340888 Title: gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340888/+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 1340905] [NEW] Acer Aspire E1-570-6889 brightness control not working
Public bug reported: Cannot adjust the brightness in a Acer Aspire E1-570-6889. The brightness key works and the brightness configuracion in the system configuration allows to adjust the brightness but the display does nothing, it is always at full brightness. I may try some things esporadically since it is not my laptop, but I may take a long time to try them :-(. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Fri Jul 11 15:48:22 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0835] InstallationDate: Installed on 2014-07-07 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Acer Aspire E1-570 ProcEnviron: LANGUAGE=es_UY:es TERM=xterm PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=951be93c-e59d-461a-b0e6-d7e48153b4ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_CX dmi.board.vendor: Acer dmi.board.version: V2.06 dmi.chassis.asset.tag: Acer Asset Tag String dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnAcer:pnAspireE1-570:pvrV2.06:rvnAcer:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06: dmi.product.name: Aspire E1-570 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 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.1 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: Fri Jul 11 15:25:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18668 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340905 Title: Acer Aspire E1-570-6889 brightness control not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340905/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1041790]
I am seeing [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle followed by a graphics freeze and the need to reboot (if I can) in Fedora 20 with the latest updates including the 3.15.4 kernel. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1337749] Re: High CPU usage after resizing a window
Abhijit, you're right scrolling in Chrome only uses around 40% or so. I noticed it doesn't have smooth scrolling enabled. After disabling smooth scrolling in Firefox (general.smoothScroll in about:config), CPU usage dropped to about the same level as Chrome. Still extremely high for just scrolling down a page, though. I tested on the office computer today, which is a Core i7-920 w/ 6GB of RAM and an Nvidia GT 9400 with the proprietary driver installed. I can confirm that it suffers from the same problem (also running Ubuntu 14.04). -- 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/1337749 Title: High CPU usage after resizing a window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1337749/+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 1341037] Re: Xorg crashed with SIGABRT in OsAbort()
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1338492, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1341037/+attachment/4150930/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1341037/+attachment/4150932/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1341037/+attachment/4150933/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1341037/+attachment/4150934/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1341037/+attachment/4150935/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1341037/+attachment/4150936/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1341037/+attachment/4150937/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1338492 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1341037 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1341037/+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 1341037] Re: Xorg crashed with SIGABRT in OsAbort()
Great, now i can't switch to nvidia card anymore... And there is no error mensage displayed in this pop-up window. ** This bug is no longer a duplicate of private bug 1338492 ** Attachment added: Nvidia-prime does not switch to nvidia card anymore https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1341037/+attachment/4150938/+files/nvidia-prime%20does%20not%20switch%20to%20nvidia%20card.png -- 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/1341037 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1341037/+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 1341037] Re: Xorg crashed with SIGABRT in OsAbort()
And there is no messages in terminal too, just it: ERROR: -- 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/1341037 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1341037/+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 1213338] Re: Displaylink slow graphic performance on Ubuntu 13
I have similar problems using xrandr on a laptop with a dual display LCD 32 TV under Ubuntu 14.04 with Kernel's 3.13.24, 3.13.29, 3.15.1, 3.15.2, 3.15.3, 3.15.4 and 3.15.5. A new Kernel seems to come out each week addressing various problems so I have held off reporting the glitches. -- 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/1213338 Title: Displaylink slow graphic performance on Ubuntu 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1213338/+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 1341037] Re: Xorg crashed with SIGABRT in OsAbort()
sudo prime-select nvidia Error: alternatives are not set up properly Error: nvidia mode can't be enabled So i tried: sudo prime-switch sudo prime-select nvidia sudo prime-offload sudo prime-select nvidia sudo prime-offload in this sequence, logout, get a black screen, restart and got this new report bug. It happens in kernel 3.13 and 3.14 ** Attachment added: _usr_bin_Xorg.0.crash https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1341037/+attachment/4150950/+files/_usr_bin_Xorg.0.crash -- 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/1341037 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1341037/+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 1314551] Re: 1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption
Bartlomiej Ogryczak, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- 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/1314551 Title: 1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314551/+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
