[Ubuntu-x-swat] [Bug 1220645] Re: Webcam capture plays green screen through xv on Haswell platform
raring version uploaded, dropped ubuntu-sponsors from subscribers -- 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/1220645 Title: Webcam capture plays green screen through xv on Haswell platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1220645/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232365] Re: Xorg crashed with SIGABRT in xf86ScrnToScreen()
*** This bug is a duplicate of bug 1213299 *** https://bugs.launchpad.net/bugs/1213299 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 #1213299, 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/1232365/+attachment/3846541/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1232365/+attachment/3846544/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1232365/+attachment/3846555/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1232365/+attachment/3846557/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1232365/+attachment/3846558/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1232365/+attachment/3846559/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1232365/+attachment/3846560/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1213299 Xorg crashed with SIGABRT in xf86ScrnToScreen() ** 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/1232365 Title: Xorg crashed with SIGABRT in xf86ScrnToScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1232365/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1213299] Re: Xorg crashed with SIGABRT in xf86ScrnToScreen()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New = Confirmed -- 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/1213299 Title: Xorg crashed with SIGABRT in xf86ScrnToScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1213299/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1218815] Re: [radeon] Graphic glitches and screen corruption (vertical lines) on XMir surfaces only
In my system vertical bar disappeared, but the screen now presents the type of glitches you casn see in the attached file. I have a radeon 6450 and the latest mir, xmir and kernel (as of 28/09/2013). ** Attachment added: Desktop glitches https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1218815/+attachment/3846628/+files/Schermata%20del%202013-09-28%2009%3A16%3A43.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/1218815 Title: [radeon] Graphic glitches and screen corruption (vertical lines) on XMir surfaces only To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1218815/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 958279] Re: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep.
I have this issue as well. Ubuntu 12.04, 3.2.0-53-generic-pae kernel Catalyst Driver Packaging Version 8.96 AMD Radeon HD 7660D (A10 5700 APU) I put this APU in two new builds, totally identical except that one has ASRock FM2A85 and the other ASRock FM2A75. Only the build with the ...A85 mobo is affected. Using 'xset dpms force off' to activate energy star power saving funtions, or 'xset s activate' to blank screen will sooner or later (often sooner) leave me with a running computer where i can not return from the blank screen (and it is not just that I can not see the screen, the keyboard is not responding, i have tried to safely shutdown using keybindings, but it does not work). Does not fix the issue: 'aticonfig --acpi-services=off' Setting this option in xorg.conf does not fix the issue: Option DPMS false All these things in combination does prevent the issue: Put in my login script: 'xset -dpms ' 'xset s off ' Put in xorg.conf: Option DPMS false But it does not fix the issue, because I only avoid screen freeze because I never enable the screen blanking/saving functions. Right now I am using 'feh -FNY ~/.black.png' as a simple screen-blanking function instead. Regards Mikael -- 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/958279 Title: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/958279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1218815] Re: [radeon] Graphic glitches and screen corruption (vertical lines) on XMir surfaces only
After my saucy update today it seems to work! Good work! -- 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/1218815 Title: [radeon] Graphic glitches and screen corruption (vertical lines) on XMir surfaces only To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1218815/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 958279] Re: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep.
Refering my last post above; Using xscreensaver (without using 'Display Power Management') works fine for me, so if you encounter issues with the xorg screensaver freezing, disabling the 'xset' screensaving features and installing/using xscreensaver instead might be a workaround for you as well: Install package 'xscreensaver'. Add these two lines to ~/.xinitrc (or whatever gnome/unity/xfce/kde startup script you have): xset -dpms xset s off Set this option in /etc/X11/xorg.conf: Option DPMS false Configure xscreensaver with cmd 'xscreensaver-demo' and set it to use Mode: Blank Screen Only and do NOT enable any Display Power Management. If you sometimes want to manually start the screen saver, use cmd xscreensaver-command -activate'. /Mikael -- 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/958279 Title: FGLRX DPMS support totally broken, fails to wake up the monitor after putting it to sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/958279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1218224] Re: [gm45] VGA Output not activated
I can confirm that this applies also to a Samsung monitor as well as the Dell monitor, with two different, high-quality VGA cables, suggesting that it's a driver issue. A reboot of the machine with the monitor attached is a workaround for the issue with the Samsung as well. -- 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/1218224 Title: [gm45] VGA Output not activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1218224/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
Someone needs to test the version in precise-proposed and then tag this bug 'verification-done' or 'verification-failed' as appropriate. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
Is this really still an issue? We have 304 and 319 in precise now, so we don't need obsolete experimental drivers (and settings panels) any more. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232426] [NEW] Saicy beta Lubuntu does not save monitor configuration
Public bug reported: Monitor configuration in saucy beta Lubuntu is set to turn off built in monitor and set external monitor to 1360 instead of default 1920 (squint, hard to read read 1920x1080 on a 15.5 monitor). Save configuration. Reboot, saved configuration is ignored and boots up with both monitors on, 1920x1080 instead of the configuration I saved, built in monitor off, 1360x768. I haven't had this problem with ubuntu saucy beta 1 can't test it with the latest saucy beta because ubiquity won't run (separate launchpad bug). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sat Sep 28 07:24:36 2013 InstallationDate: Installed on 2013-09-26 (1 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Beta amd64 (20130925) MarkForUpload: True SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1232426 Title: Saicy beta Lubuntu does not save monitor configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1232426/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-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 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
It is all set. On Sep 28, 2013, at 7:01 AM, Alberto Milone alberto.mil...@canonical.com wrote: Is this really still an issue? We have 304 and 319 in precise now, so we don't need obsolete experimental drivers (and settings panels) any more. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings Status in “nvidia-settings” package in Ubuntu: Invalid Status in “nvidia-settings-experimental-304” package in Ubuntu: Fix Committed Status in “nvidia-settings-experimental-310” package in Ubuntu: Fix Committed Status in “nvidia-settings-updates” package in Ubuntu: Invalid Status in “nvidia-settings” source package in Precise: New Status in “nvidia-settings-experimental-304” source package in Precise: New Status in “nvidia-settings-experimental-310” source package in Precise: New Status in “nvidia-settings-updates” source package in Precise: New Bug description: package nvidia-settings was installed. Seemed to conflict somehow. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 (not installed) ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 AptOrdering: nvidia-settings-experimental-310: Install nvidia-settings-experimental-310: Configure Architecture: amd64 Date: Thu Nov 8 17:00:14 2012 DpkgTerminalLog: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 DuplicateSignature: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 ErrorMessage: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: nvidia-settings-experimental-310 Title: package nvidia-settings-experimental-310 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 UpgradeStatus: Upgraded to precise on 2012-05-16 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+subscriptions -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1222602] Re: [gen3] Bad performance on GMA950 and GMA3150
I have tried the solution from comment #6 and it works. It would be helpful to understand why this works. Digging through the comments it looks like mesa uses not the GPU acceleration when the variable is not set. This looks like a design error in mesa. Maybe mesa developers should be asked about this. However, I have tried gnome-shell (before adding the environment setting) and it worked like a charm indicating that gnome-shell sets this variable on its own or initializes mesa differently. Considering gnome-shell was freaking slow compared to unity in 13.04. there must have been a not so wise change in unity. -- 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/1222602 Title: [gen3] Bad performance on GMA950 and GMA3150 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1222602] Re: [gen3] Bad performance on GMA950 and GMA3150
@manny that is a different bug. -- 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/1222602 Title: [gen3] Bad performance on GMA950 and GMA3150 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
** Changed in: nvidia-settings (Ubuntu Precise) Status: New = Invalid ** Changed in: nvidia-settings-experimental-304 (Ubuntu) Status: Fix Committed = Invalid ** Changed in: nvidia-settings-experimental-310 (Ubuntu) Status: Fix Committed = Invalid ** Changed in: nvidia-settings-experimental-310 (Ubuntu Precise) Status: New = Invalid ** Changed in: nvidia-settings-updates (Ubuntu Precise) Status: New = Invalid ** Changed in: nvidia-settings-experimental-304 (Ubuntu Precise) Status: New = Invalid ** Changed in: nvidia-settings-experimental-304 (Ubuntu) Assignee: Alberto Milone (albertomilone) = (unassigned) ** Changed in: nvidia-settings-experimental-310 (Ubuntu) Assignee: Alberto Milone (albertomilone) = (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1222602] Re: [gen3] Bad performance on GMA950 and GMA3150
@Colin Law Ok, thanks. I was able to confirm the lockups happening also on an AMD/ATI laptop. However, I get much more lockups on the Intel. So anyone else experienced this or reported it? Else I'll go my way and report this soon. -- 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/1222602 Title: [gen3] Bad performance on GMA950 and GMA3150 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1167301] Re: 8086:0166 [ThinkPad Twist S230u 3347] REGRESSION: Mirroring display works only with 1024x768 (4:3) whereas my laptop has 1366x768 (16:9) external monitor 1920x1080
Till Kamppeter, I noticed you omitted following the kernel.org format, on the grounds of you having identified the regression commit, and others noted they are experiencing a similar issue. The kernel.org format as outlined by Linus was created to be in addition to regression commit identification and duplicate notices, not in substitution. This omission would more than likely be a reason why your e-mail was promptly ignored. ;) If you wouldn't mind, after testing the lastest mainline kernel via http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.12-rc2-saucy/ , and assuming it's still reproducible, having another go at the mailing list following the format verbatim would probably yield you an upstream response in a timely manner. ** Tags added: needs-upstream-testing -- 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/1167301 Title: 8086:0166 [ThinkPad Twist S230u 3347] REGRESSION: Mirroring display works only with 1024x768 (4:3) whereas my laptop has 1366x768 (16:9) external monitor 1920x1080 (16:9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167301/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232478] [NEW] Ubuntu 13.10 Final Beta fails to boot/install MMIO write of 0x. FAULT
Public bug reported: I'm unable to provide complete apport data of the bug because of it's nature. I'm unable to reach a desktop or a console I can see the Ubuntu splash screen for a few seconds then the kernel panics with error logs related to nouveau while booting a Live CD of Ubuntu 13.10 Final Beta 64bit The error logs in full can be viewed here: http://ubuntuone.com/1hqSBKMr6qvKT2JwgHIkCx Hardware: Acer v3-772g (Nvidia Optimus: Intel HD 4600 + Nvidia GTX 760m) ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1232478 Title: Ubuntu 13.10 Final Beta fails to boot/install MMIO write of 0x. FAULT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1232478/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1066464] Re: Please remove xserver-xorg-video-sis from saucy (was: SiS driver crashes Xserver with EXA acceleration)
** Changed in: xserver-xorg-video-sis (Baltix) Status: New = Triaged ** Changed in: xserver-xorg-video-sis (Baltix) Importance: Undecided = High ** Changed in: xserver-xorg-video-sis (Baltix) Assignee: (unassigned) = Mantas Kriaučiūnas (mantas) -- 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/1066464 Title: Please remove xserver-xorg-video-sis from saucy (was: SiS driver crashes Xserver with EXA acceleration) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-sis/+bug/1066464/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 651468] Re: No image after suspend
Thomas B Homburg, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux replace-with-bug-number Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.12-rc1 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** This bug is no longer a duplicate of bug 574573 Can't resume after hibernate or suspend (nouveau and nvidia-current) ** Package changed: xorg (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New = Incomplete -- 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/651468 Title: No image after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651468/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232510] Re: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()
*** This bug is a duplicate of bug 1210025 *** https://bugs.launchpad.net/bugs/1210025 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 #1210025, 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/1232510/+attachment/3847541/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1232510/+attachment/3847543/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1232510/+attachment/3847544/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1232510/+attachment/3847545/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1232510/+attachment/3847546/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1232510/+attachment/3847547/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1232510/+attachment/3847548/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1210025 Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() ** 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/1232510 Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1232510/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1002788] Re: Using the touchscreen breaks normal device left clicking
I have the same problem with ASUS Vivobook S400. Touchscreen is Atmel Atmel maXTouch Digitizer. I tried the xorg-edgers ppa, but it did not help. It worked after reboot, but stopped recognizing clicks after ~5mins of use. -- 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/1002788 Title: Using the touchscreen breaks normal device left clicking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1002788/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1207487] Re: Brightness Controls work but brightness doesnt change
I am facing this bug on 13.10 with an intel graphics card and nVidia Optimus chip. Brightness controls were fine before upgrading from 13.04 -- 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/1207487 Title: Brightness Controls work but brightness doesnt change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1207487/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1207487] Re: Brightness Controls work but brightness doesnt change
Update - # ls /sys/class/backlight has three listings acpi_video0 acpi_video1 intel_backlight # cat /sys/class/backlight/intel_backlight/max_brightness 976 # echo 100 /sys/class/backlight/intel_backlight/brightness bash: /sys/class/backlight/intel_backlight/brightness: Permission denied # sudo -s root# echo 100 /sys/class/backlight/intel_backlight/brightness This last command worked and my brightness was changed successfully. I tried other values too, and they all seem to work. I didn't try going beyond the max_brightness value, of course. Is there something else I could try that would help in narrowing down and / or fixing this bug? -- 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/1207487 Title: Brightness Controls work but brightness doesnt change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1207487/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1231857] Re: [DPMS] Display backlight turns back on almost immediately after being turned off
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New = Confirmed -- 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/1231857 Title: [DPMS] Display backlight turns back on almost immediately after being turned off To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1231857/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232540] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1231348 *** https://bugs.launchpad.net/bugs/1231348 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 #1231348, 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/1232540/+attachment/3847720/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1232540/+attachment/3847723/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1232540/+attachment/3847734/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1232540/+attachment/3847736/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1232540/+attachment/3847737/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1232540/+attachment/3847738/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1232540/+attachment/3847739/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1231348 [xmir] 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/1232540 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1232540/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232546] [NEW] [i915g] False GPU lockup IPEHR: 0x7d8e0001
Public bug reported: The X-Server did not actually freeze up, only when windows are deactivated ( aka a window that is minimised ) the system doesn't redraw the background of the X-server. See the added example screen shots. ps. I am voluntarily running Gnome-fallback, newer gnome versions all stifle my productivity. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-8-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Chipset: i915g CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Sep 27 16:46:48 2013 DistUpgraded: 2013-09-18 12:45:51,582 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [i915g] GPU lockup IPEHR: 0x7d8e0001 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3007] InstallationDate: Installed on 2013-09-13 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: Hewlett-Packard HP Compaq dc7100 USDT(PN286ET) MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=4057cba2-bf3f-402c-8734-0030c0c32620 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [i915g] False GPU lockup IPEHR: 0x7d8e0001 UpgradeStatus: Upgraded to saucy on 2013-09-18 (10 days ago) UserGroups: dmi.bios.date: 08/07/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786C1 v02.15 dmi.board.name: 0980h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: HUB522032G dmi.chassis.type: 15 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786C1v02.15:bd08/07/2008:svnHewlett-Packard:pnHPCompaqdc7100USDT(PN286ET):pvr:rvnHewlett-Packard:rn0980h:rvr:cvnHewlett-Packard:ct15:cvr: dmi.product.name: HP Compaq dc7100 USDT(PN286ET) dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6 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-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Sep 28 22:05:31 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputApple, Inc Apple Keyboard KEYBOARD, id 8 inputApple, Inc Apple Keyboard KEYBOARD, id 9 inputBelkin Washable Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19186 vendor GSM xserver.version: 2:1.14.2.901-2ubuntu6 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash false-gpu-hang freeze i386 saucy ubuntu ** Attachment added: screenshot 4 https://bugs.launchpad.net/bugs/1232546/+attachment/3847789/+files/Screenshot%20from%202013-09-28%2022%3A31%3A10.png -- 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/1232546 Title: [i915g] False GPU lockup IPEHR: 0x7d8e0001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1232546/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232546] Re: [i915g] False GPU lockup IPEHR: 0x7d8e0001
The before closing windows shot. ** Attachment added: Screenshot 1 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1232546/+attachment/3847811/+files/Screenshot%20from%202013-09-28%2022%3A30%3A01.png -- 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/1232546 Title: [i915g] False GPU lockup IPEHR: 0x7d8e0001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1232546/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232546] Re: [i915g] False GPU lockup IPEHR: 0x7d8e0001
Screenshot 4 is the after closing several windows shot. This is the third one in sequence ** Attachment added: Screenshot 3 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1232546/+attachment/3847809/+files/Screenshot%20from%202013-09-28%2022%3A30%3A54.png -- 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/1232546 Title: [i915g] False GPU lockup IPEHR: 0x7d8e0001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1232546/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232557] [NEW] X.Org Server terminates when I close video player or run glxgears
Public bug reported: How to reproduce: run one of these: glxgears mplayer -vo gl2 /path/to/video.extension or vlc /path/to/video.extension then close it by pressing alt+f4 or clicking in the X in the corner of the window What you expected to happen: The program closes succesfully What happened instead: X server crashes This has been fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=60182#c29 . Also note that there is another patch that seems to solve a related bug: https://bugs.freedesktop.org/show_bug.cgi?id=60182#c6 I'm not a dev, so I cannot add many details, though. My hardware is: AMD A6-3400M, Radeon HD 6520g + HD 6750M. I made sure this has not been fixed in xserver-xorg-video-ati version 1:7.2.0-0ubuntu9 by checking the source files manually. (I'm using several PPAs, one of which is a repo for updates graphics drivers for raring... but I checked this exact version) $ lsb_release -rd Description:Ubuntu Saucy Salamander (development branch) Release:13.10 $ apt-cache policy xserver-xorg-video-ati xserver-xorg-video-ati: Installed: 1:7.2.0-0ubuntu6 Candidate: 1:7.2.0+git1309171150.b955dd~gd~r Version table: 1:7.2.0+git1309171150.b955dd~gd~r 0 500 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu/ raring/main amd64 Packages 1:7.2.0-0ubuntu9 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages *** 1:7.2.0-0ubuntu6 0 100 /var/lib/dpkg/status Thanks. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-video-ati (Ubuntu Saucy) Importance: Undecided Status: New -- 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/1232557 Title: X.Org Server terminates when I close video player or run glxgears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1232557/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232557] Re: X.Org Server terminates when I close video player or run glxgears
** Also affects: xserver-xorg-video-ati (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati (Ubuntu Saucy) Importance: Undecided = High ** Tags added: saucy ** Changed in: xserver-xorg-video-ati (Ubuntu Saucy) Assignee: (unassigned) = Canonical X.org (canonical-x) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1232557 Title: X.Org Server terminates when I close video player or run glxgears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1232557/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 583494] Re: 8086:2a42 [gm45] Screen blacks out for a second occasionally
*** This bug is a duplicate of bug 538648 *** https://bugs.launchpad.net/bugs/538648 ** Summary changed: - [gm45] Screen blacks out for a second occasionally + 8086:2a42 [gm45] Screen blacks out for a second occasionally -- 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/583494 Title: 8086:2a42 [gm45] Screen blacks out for a second occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/583494/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 578899] Re: 8086:2a42 [gm45] Screen flickers (Needs i915.powersave=0)
*** This bug is a duplicate of bug 538648 *** https://bugs.launchpad.net/bugs/538648 ** Summary changed: - [gm45] Screen flickers (Needs i915.powersave=0) + 8086:2a42 [gm45] Screen flickers (Needs i915.powersave=0) -- 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/578899 Title: 8086:2a42 [gm45] Screen flickers (Needs i915.powersave=0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/578899/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 534894] Re: 8086:2a42 screen flickers in the bottom half of the screen at random
*** This bug is a duplicate of bug 538648 *** https://bugs.launchpad.net/bugs/538648 ** Summary changed: - screen flickers in the bottom half of the screen at random + 8086:2a42 screen flickers in the bottom half of the screen at random -- 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/534894 Title: 8086:2a42 screen flickers in the bottom half of the screen at random To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/534894/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 538648] Re: 8086:2a42 [Intel GM45] Irregular sync flashes (Needs i915.powersave quirk)
** Summary changed: - [Intel GM45] Irregular sync flashes on 8086:2a42 (Needs i915.powersave quirk) + 8086:2a42 [Intel GM45] Irregular sync flashes (Needs i915.powersave quirk) -- 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/538648 Title: 8086:2a42 [Intel GM45] Irregular sync flashes (Needs i915.powersave quirk) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/538648/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232587] Re: Xorg crashed with SIGABRT in __libc_start_main()
*** This bug is a duplicate of bug 1232000 *** https://bugs.launchpad.net/bugs/1232000 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 #1232000, 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/1232587/+attachment/3848087/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1232587/+attachment/3848090/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1232587/+attachment/3848101/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1232587/+attachment/3848103/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1232587/+attachment/3848104/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1232587/+attachment/3848105/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1232587/+attachment/3848106/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1232000 ** 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/1232587 Title: Xorg crashed with SIGABRT in __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1232587/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1232557] Re: X.Org Server terminates when I close video player or run glxgears
Launchpad has imported 37 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=60182. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2013-02-02T06:52:02+00:00 RussianNeuroMancer wrote: X.Org Server terminate when I close VLC (OpenGL GLX video output). This issue not reproducible when VLC doesn't playback anything. So only closing player that still playback video trigger issue. Issue reproducible not every time (around 1 of 10 closing VLC get X.Org Server termination). Issue tested only on integrated GPU (Radeon HD 6620G). Kubuntu 13.04 x86_64 Linux 3.8rc6 (with Linux 3.7 is also reproducible). Mesa: 9.0.2 (with 9.1 is also reproducible) libdrm-radeon1: 2.4.41 xserver-xorg-video-radeon: 7.1.0 xserver-xorg-core: 1.13.2 KDE 4.9.98 (4.10rc3) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/0 On 2013-02-02T06:53:52+00:00 RussianNeuroMancer wrote: Created attachment 74078 Log of terminated X.Org Server Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/1 On 2013-02-02T06:54:57+00:00 RussianNeuroMancer wrote: Created attachment 74079 dmesg Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/2 On 2013-02-02T06:57:00+00:00 RussianNeuroMancer wrote: Also a little bit info, just in case: Exact GPU model: 1002:6741 Advanced Micro Devices [AMD] nee ATI BeaverCreek [Mobility Radeon HD 6620G] VLC version: 2.0.5. If I need to provide any additional information, please let me know. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/3 On 2013-02-04T10:51:39+00:00 Michel-daenzer wrote: The attached log ends abruptly. Is there more information in the kdm log file? Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/4 On 2013-02-04T16:15:23+00:00 RussianNeuroMancer wrote: Is there more information in the kdm log file? I use LightDM-KDE. I'll look into LightDM log next time. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/5 On 2013-02-04T16:54:39+00:00 Ihadzic wrote: Created attachment 74183 Possible Band-Aid to get you going. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/6 On 2013-02-04T16:56:30+00:00 Ihadzic wrote: I have just posted a patch that may help at least prevent the crash. I have seen this bug on my end too, but I though that I locally introduced it with my own hacks. The patch does not solve the root cause (i.e. buffer double-free), but if it prevents the crash, maybe we can apply it to get people going until we find the real solution. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/7 On 2013-02-04T17:37:47+00:00 RussianNeuroMancer wrote: So since you find root case, LightDM log is not necessary now, I am correct? Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/8 On 2013-02-04T17:43:09+00:00 Ihadzic wrote: (In reply to comment #8) So since you find root case, LightDM log is not necessary now, I am correct? No, I didn't find the root cause. I am only assuming (based on the last message in your Xorg.0.log file) that you are seeing the same kind of a crash that I have been seeing recently. So I would like you to test if the patch that I posted fixes the problem for you. If it does, then there are two open issues that remain: a) should we push my patch upstream (i.e. to at least prevent the crash of affected users like you) and b) what really causes the double-free. The latter is what we have no idea about yet. Any additional logs that you can produce in the meantime would be useful. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1232557/comments/9 On 2013-02-04T17:47:23+00:00 RussianNeuroMancer wrote: So I would like you to
[Ubuntu-x-swat] [Bug 1198962] Re: Xorg crashed with SIGABRT in raise()
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Expired -- 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/1198962 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1198962/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
