[Ubuntu-x-swat] [Bug 1498799] Re: screen resolution 640x480
*** This bug is a duplicate of bug 1498705 *** https://bugs.launchpad.net/bugs/1498705 ibnu, thank you for reporting this and helping make Ubuntu better. If you upgrade to the Vivid enablement stack as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack does this change anything for you? ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** This bug has been marked a duplicate of bug 1498705 screen resolution -- 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/1498799 Title: screen resolution 640x480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1498799/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1452318] Re: Faulty behavior when resuming from suspend
I tried to bisect it, but that went nowhere.. too many changes between 3.19..4.0 to identify backportable fixes just by looking at it. ** This bug has been marked a duplicate of bug 1483320 [BDW] VGA output regression on 4.2 (was: Migrate Broadwell to use i915_bpo) -- 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/1452318 Title: Faulty behavior when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1452318/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1468373] Re: GPU driver issues when waking up from suspend mode
*** This bug is a duplicate of bug 1483320 *** https://bugs.launchpad.net/bugs/1483320 ** This bug is no longer a duplicate of bug 1452318 Faulty behavior when resuming from suspend ** This bug has been marked a duplicate of bug 1483320 [BDW] VGA output regression on 4.2 (was: Migrate Broadwell to use i915_bpo) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1468373 Title: GPU driver issues when waking up from suspend mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1468373/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1497707] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1497707/+attachment/4469410/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1497707/+attachment/4469412/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1497707/+attachment/4469415/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1497707/+attachment/4469416/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1497707/+attachment/4469417/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1497707/+attachment/4469418/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1497707/+attachment/4469419/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 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/1497707 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1497707/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1497698] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1338492 *** https://bugs.launchpad.net/bugs/1338492 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/1497698/+attachment/4469351/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1497698/+attachment/4469354/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1497698/+attachment/4469365/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1497698/+attachment/4469367/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1497698/+attachment/4469368/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1497698/+attachment/4469369/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1497698/+attachment/4469370/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1338492 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/1497698 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1497698/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1497468] Re: Xorg crashed with SIGSEGV
*** This bug is a duplicate of bug 1498707 *** https://bugs.launchpad.net/bugs/1498707 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 #1498707, 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/1497468/+attachment/4468149/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1497468/+attachment/4468152/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1497468/+attachment/4468165/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1497468/+attachment/4468167/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1497468/+attachment/4468168/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1497468/+attachment/4468169/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1497468/+attachment/4468170/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1498707 ** 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/1497468 Title: Xorg crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1497468/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1497464] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1497464/+attachment/4468127/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1497464/+attachment/4468130/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1497464/+attachment/4468137/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1497464/+attachment/4468139/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1497464/+attachment/4468140/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1497464/+attachment/4468141/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1497464/+attachment/4468142/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 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/1497464 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1497464/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1492037] Re: Segmentation fault in brw_meta_fast_clear
This bug was fixed in the package mesa - 11.0.0-1ubuntu1 --- mesa (11.0.0-1ubuntu1) wily; urgency=medium * Merge from Debian. (LP: #1484279) * egl-platform-mir.patch: Updated. * i965-remove-early-release-of-dri2-miptree.patch: Add a workaround to fix crashes in brw_meta_fast_clear. (LP: #1492037) * control, rules: Default to llvm-3.6 again, because 3.7 won't be in main for wily. mesa (11.0.0-1) experimental; urgency=medium * New upstream release. mesa (11.0.0~rc3-1) experimental; urgency=medium [ Andreas Boll ] * Use https for Vcs-* fields. [ Timo Aaltonen ] * New upstream release candidate. mesa (11.0.0~rc2-1) experimental; urgency=medium * New upstream release candidate. mesa (11.0.0~rc1-1) experimental; urgency=medium [ Andreas Boll ] * New upstream release candidate. * control: Drop unneeded libomxil-bellagio-dev build-dep. * rules: Explicitly disable vaapi (Closes: #789100). * control: Update upstream url. * control: Update Vcs-* fields. * Drop libgl1-mesa-swx11* packages. * control: Update package description. [ Timo Aaltonen ] * control: Delete commented out libgl1-mesa-glx-i686 from the file. * control: Bump llvm/libclang build-deps to match versions where amdgpu is enabled. mesa (11.0.0~git20150817-1) experimental; urgency=medium * New upstream snapshot * control: Bump libdrm build-dep to 2.4.63. * control: Add libomxil-bellagio-dev to build-deps. * rules: Disable gles1 & 2 for swx11 builds. * libegl1-mesa.symbols, libgles2-mesa.symbols: Updated * control, rules: Migrate to llvm 3.7. * rules: Enable llvmpipe on armhf again. mesa (10.6.7-1) unstable; urgency=medium * New upstream release. mesa (10.6.5-1) unstable; urgency=medium [ Andreas Boll ] * New upstream release. [ Julien Cristau ] * Break libopengl-perl (<< 0.6704+dfsg-2), thanks to Niko Tyni (closes: #796918) mesa (10.6.4-1) unstable; urgency=medium * New upstream release. -- Timo AaltonenTue, 22 Sep 2015 19:20:17 +0300 ** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released -- 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/1492037 Title: Segmentation fault in brw_meta_fast_clear To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1492037/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1484279] Re: [FFe] Mesa 11.0.0
This bug was fixed in the package mesa - 11.0.0-1ubuntu1 --- mesa (11.0.0-1ubuntu1) wily; urgency=medium * Merge from Debian. (LP: #1484279) * egl-platform-mir.patch: Updated. * i965-remove-early-release-of-dri2-miptree.patch: Add a workaround to fix crashes in brw_meta_fast_clear. (LP: #1492037) * control, rules: Default to llvm-3.6 again, because 3.7 won't be in main for wily. mesa (11.0.0-1) experimental; urgency=medium * New upstream release. mesa (11.0.0~rc3-1) experimental; urgency=medium [ Andreas Boll ] * Use https for Vcs-* fields. [ Timo Aaltonen ] * New upstream release candidate. mesa (11.0.0~rc2-1) experimental; urgency=medium * New upstream release candidate. mesa (11.0.0~rc1-1) experimental; urgency=medium [ Andreas Boll ] * New upstream release candidate. * control: Drop unneeded libomxil-bellagio-dev build-dep. * rules: Explicitly disable vaapi (Closes: #789100). * control: Update upstream url. * control: Update Vcs-* fields. * Drop libgl1-mesa-swx11* packages. * control: Update package description. [ Timo Aaltonen ] * control: Delete commented out libgl1-mesa-glx-i686 from the file. * control: Bump llvm/libclang build-deps to match versions where amdgpu is enabled. mesa (11.0.0~git20150817-1) experimental; urgency=medium * New upstream snapshot * control: Bump libdrm build-dep to 2.4.63. * control: Add libomxil-bellagio-dev to build-deps. * rules: Disable gles1 & 2 for swx11 builds. * libegl1-mesa.symbols, libgles2-mesa.symbols: Updated * control, rules: Migrate to llvm 3.7. * rules: Enable llvmpipe on armhf again. mesa (10.6.7-1) unstable; urgency=medium * New upstream release. mesa (10.6.5-1) unstable; urgency=medium [ Andreas Boll ] * New upstream release. [ Julien Cristau ] * Break libopengl-perl (<< 0.6704+dfsg-2), thanks to Niko Tyni (closes: #796918) mesa (10.6.4-1) unstable; urgency=medium * New upstream release. -- Timo AaltonenTue, 22 Sep 2015 19:20:17 +0300 ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- 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/1484279 Title: [FFe] Mesa 11.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1452318] Re: Faulty behavior when resuming from suspend
hm, making this the master bug of this issue, duping others here ** This bug is no longer a duplicate of bug 1483320 [BDW] VGA output regression on 4.2 (was: Migrate Broadwell to use i915_bpo) ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- 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/1452318 Title: Faulty behavior when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452318/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1468373] Re: GPU driver issues when waking up from suspend mode
*** This bug is a duplicate of bug 1452318 *** https://bugs.launchpad.net/bugs/1452318 ** This bug is no longer a duplicate of bug 1483320 [BDW] VGA output regression on 4.2 (was: Migrate Broadwell to use i915_bpo) ** This bug has been marked a duplicate of bug 1452318 Faulty behavior when resuming from suspend -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1468373 Title: GPU driver issues when waking up from suspend mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1468373/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498705] Re: screen resolution
ibnu, thank you for reporting this and helping make Ubuntu better. If you upgrade to the Vivid enablement stack as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack does this change anything for you? ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (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/1498705 Title: screen resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1498705/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498808] Re: stuck resolution 640x480
*** This bug is a duplicate of bug 1498705 *** https://bugs.launchpad.net/bugs/1498705 ** This bug has been marked a duplicate of bug 1498799 screen resolution 640x480 ** This bug is no longer a duplicate of bug 1498799 screen resolution 640x480 ** This bug has been marked a duplicate of bug 1498705 screen resolution -- 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/1498808 Title: stuck resolution 640x480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1498808/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1452318] Re: Faulty behavior when resuming from suspend
Wahoo!! The vivid-proposed kernel seems to fix the issues for me too. Thanks to all who worked on this: Much appreciated. Just out of interest, is it any clearer yet what the problem was? Thanks again. -- 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/1452318 Title: Faulty behavior when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1452318/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498593] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1498593/+attachment/4471491/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1498593/+attachment/4471494/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1498593/+attachment/4471503/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1498593/+attachment/4471505/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1498593/+attachment/4471506/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1498593/+attachment/4471507/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1498593/+attachment/4471508/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 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/1498593 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1498593/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1342675] Re: Random characters in screen text suddenly disappear
My previous comment was wrong. All windows are affected, but not necessarily at the same time. -- 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/1342675 Title: Random characters in screen text suddenly disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1342675/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498893] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1498893/+attachment/4472209/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1498893/+attachment/4472212/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1498893/+attachment/4472219/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1498893/+attachment/4472221/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1498893/+attachment/447/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1498893/+attachment/4472223/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1498893/+attachment/4472224/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 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/1498893 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1498893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1489696] Re: black screen when enabling rotation on a gpu screen
This bug was fixed in the package xorg-server - 2:1.17.1-0ubuntu3.1 --- xorg-server (2:1.17.1-0ubuntu3.1) vivid; urgency=medium * disable-rotation-transform-gpuscreens.patch: Revert back to disabling rotations on GPU screens. (LP: #1489696) -- Timo AaltonenWed, 02 Sep 2015 16:21:04 +0300 ** Changed in: xorg-server (Ubuntu Vivid) Status: Fix Committed => Fix Released -- 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/1489696 Title: black screen when enabling rotation on a gpu screen To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1489696/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1489696] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1489696 Title: black screen when enabling rotation on a gpu screen To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1489696/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1490684] Re: Mouse cursor duplicated in dual screen setup
Thanks for the response, and very clear instructions on how to upgrade the BIOS under Linux. It's much appreciated. I upgraded the BIOS: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 1402 08/09/2012 The problem of a duplicate cursor getting stuck on the previous screen is much less common now, but does still occur. Especially when moving the cursor from one screen to the other relatively quickly. I should probably clarify that, like the original bug, this didn't happen in Ubuntu 12.04. I upgraded that to Ubuntu 14.04 and the problem still wasn't there. Then I wiped the machine and installed Kubuntu 14.04 directly, and the problem manifested itself. Thanks for your continued help. ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1490684 Title: Mouse cursor duplicated in dual screen setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1490684/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1489696] Re: black screen when enabling rotation on a gpu screen
This bug was fixed in the package xorg-server-lts-vivid - 2:1.17.1-0ubuntu3.1~trusty1 --- xorg-server-lts-vivid (2:1.17.1-0ubuntu3.1~trusty1) trusty; urgency=medium * Backport vivid package for lts-vivid stack. xorg-server (2:1.17.1-0ubuntu3.1) vivid; urgency=medium * disable-rotation-transform-gpuscreens.patch: Revert back to disabling rotations on GPU screens. (LP: #1489696) -- Timo AaltonenWed, 02 Sep 2015 16:28:30 +0300 ** Changed in: xorg-server-lts-vivid (Ubuntu Trusty) Status: Fix Committed => Fix Released -- 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/1489696 Title: black screen when enabling rotation on a gpu screen To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1489696/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1472272] Re: problems in X
Yes, I changed and nothing. I needed reinstall Ubuntu other day e this problem that's ok. This HP was my first and it was be last. The incompatible were much. -- 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/1472272 Title: problems in X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1472272/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498935] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1498935/+attachment/4472285/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1498935/+attachment/4472288/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1498935/+attachment/4472295/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1498935/+attachment/4472297/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1498935/+attachment/4472298/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1498935/+attachment/4472299/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1498935/+attachment/4472300/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 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/1498935 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1498935/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1490684] Re: Mouse cursor duplicated in dual screen setup
Nevermind, it's not really any more or less frequent after the BIOS upgrade. One further thing I've observed is that the cursor duplication IS more frequent if I have open windows near the edges of the screens where the transfer is taking place. If it's just the desktop, then the cursor gets stuck on occasion, but not as often. -- 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/1490684 Title: Mouse cursor duplicated in dual screen setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1490684/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498547] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1498547/+attachment/4471444/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1498547/+attachment/4471447/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1498547/+attachment/4471456/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1498547/+attachment/4471458/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1498547/+attachment/4471459/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1498547/+attachment/4471460/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1498547/+attachment/4471461/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 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/1498547 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1498547/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498698] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1496172 *** https://bugs.launchpad.net/bugs/1496172 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 #1496172, 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/1498698/+attachment/4471685/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1498698/+attachment/4471688/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1498698/+attachment/4471700/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1498698/+attachment/4471702/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1498698/+attachment/4471703/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1498698/+attachment/4471704/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1498698/+attachment/4471705/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1496172 ** 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/1498698 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1498698/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1298846] Re: AMD Radeon HD [1002:9834][1002:9830] Unable to boot to desktop without the nomodeset parameter
This bug still exists in a supported release, namely 12.04.5, with the trusty backported xorg stack. # lspci -nn -k | grep -A 2 VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400] [1002:9830] Subsystem: ASUSTeK Computer Inc. Device [1043:8623] Kernel driver in use: radeon I'll attach the Xorg.log as well, which shows the segfault. ** Package changed: xorg-lts-saucy (Ubuntu) => xorg-lts-trusty (Ubuntu) ** Changed in: xorg-lts-trusty (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-lts-saucy in Ubuntu. https://bugs.launchpad.net/bugs/1298846 Title: AMD Radeon HD [1002:9834][1002:9830] Unable to boot to desktop without the nomodeset parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-trusty/+bug/1298846/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498526] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1237904 *** https://bugs.launchpad.net/bugs/1237904 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 #1237904, 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/1498526/+attachment/4471376/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1498526/+attachment/4471379/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1498526/+attachment/4471388/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1498526/+attachment/4471390/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1498526/+attachment/4471391/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1498526/+attachment/4471392/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1498526/+attachment/4471393/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1237904 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/1498526 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1498526/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1492753] Re: Screen rotation broken in Wily
This issue happens on intel gpu also. I tried several BDW and SKL integrate GPU machines, all of them have this issue. -- 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/1492753 Title: Screen rotation broken in Wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1492753/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498808] [NEW] stuck resolution 640x480
Public bug reported: gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits) i can not change my desktop resolution and stuck at 640x480 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 23 15:32:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.10, 3.16.0-30-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] (rev 10) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:0801] InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) Lsusb: Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: clevo M7x0S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=e2d9e4a4-8627-4223-ab53-4466b48fd5ba ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/0892 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: 1234567890 dmi.board.name: M7x0S dmi.board.vendor: clevo dmi.board.version: Bottom dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: SiS dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/08/0892:svnclevo:pnM7x0S:pvrRev.A1:rvnclevo:rnM7x0S:rvrBottom:cvnSiS:ct1:cvrN/A: dmi.product.name: M7x0S dmi.product.version: Rev. A1 dmi.sys.vendor: clevo version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.libdrm2: libdrm2 2.4.65+git20150922.f3c6740f-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Sep 23 15:27:14 2015 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1498808 Title: stuck resolution 640x480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1498808/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1452318] Re: Faulty behavior when resuming from suspend
try latest kernel from vivid-proposed ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1452318 Title: Faulty behavior when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1452318/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1463926] Re: Removing HDMI cable will not always resize the desktop
known kernel bug upstream ** Bug watch added: freedesktop.org Bugzilla #76464 https://bugs.freedesktop.org/show_bug.cgi?id=76464 ** Changed in: xorg-server Importance: Undecided => Unknown ** Changed in: xorg-server Status: New => Unknown ** Changed in: xorg-server Remote watch: None => freedesktop.org Bugzilla #76464 ** Changed in: xserver-xorg-video-intel (Ubuntu) Importance: Undecided => Low ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Triaged -- 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/1463926 Title: Removing HDMI cable will not always resize the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1463926/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4
Re-opened for libhybris. I just realized we could fix this in hybris by pre-pending the OpenGL version string it returns. Instead of returning: OpenGL ES 3.0 V@53.0 AU@ (CL@) we could make it: Hybris OpenGL ES 2.0 on OpenGL ES 3.0 V@53.0 AU@ (CL@) So then epoxy would not try to use the 3.0 functions missing in hybris. And no crash. ** Changed in: libhybris (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494240 Title: Xmir crashes immediately on startup using glamor on Nexus4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1494240/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1406725] Re: Severe graphical corruption running software clients on android
This bug is now hurting Xmir on phones. ** Summary changed: - Severe graphical corruption running mir_demo_client_flicker on mako + Severe graphical corruption running software clients on android ** Tags removed: mako nexus4 ** Tags added: android xmir ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Triaged ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Changed in: mir Importance: Medium => High ** Summary changed: - Severe graphical corruption running software clients on android + Severe graphical corruption running software clients (including Xmir) on android -- 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/1406725 Title: Severe graphical corruption running software clients (including Xmir) on android To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1498799] [NEW] screen resolution 640x480
Public bug reported: I am honestly completely confused as to why this is happening. This morning I boot up my computer and it was stuck at 640x480, for no apparent reason. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 23 15:11:45 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.10, 3.16.0-30-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] (rev 10) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:0801] InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) Lsusb: Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: clevo M7x0S ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=e2d9e4a4-8627-4223-ab53-4466b48fd5ba ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/0892 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: 1234567890 dmi.board.name: M7x0S dmi.board.vendor: clevo dmi.board.version: Bottom dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: SiS dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/08/0892:svnclevo:pnM7x0S:pvrRev.A1:rvnclevo:rnM7x0S:rvrBottom:cvnSiS:ct1:cvrN/A: dmi.product.name: M7x0S dmi.product.version: Rev. A1 dmi.sys.vendor: clevo version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.libdrm2: libdrm2 2.4.65+git20150922.f3c6740f-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Sep 23 15:09:28 2015 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1498799 Title: screen resolution 640x480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1498799/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1453298]
My apologies for my use of incorrect terminology ... yes, 'full system freezes' was the term I should have used! -- 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/1453298 Title: Xubuntu freeze once a day To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1453298/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1453298]
I can confirm that "legacy turbo" patch doesn't work for me either. Using that patch with ck-kernel, my system still freezes under high CPU- load frequently. The last kernel works for me is the 3.18.x branch. -- 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/1453298 Title: Xubuntu freeze once a day To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1453298/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1453298]
Have been subjected to this segment fault after performing a kernel update last week to 3.13.0-64-generic. The seg fault would particularly be prevalent under Kodi 15.x when viewing video material. My dmseg: http://pastebin.com/Gc7R4X5u Installed 'Fritsch' custom kernel (incorporating his 'legacy turbo fix' 3.19.2-legacy+edid+) from his post at http://forum.kodi.tv/showthread.php?tid=238447, and that fixed the issue for me. -- 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/1453298 Title: Xubuntu freeze once a day To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1453298/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1453298]
Wait: A segmentation fault is something completely different than what is discussed in this bugreport. From your forum post I figured you get full freeze of your system. Does it full freeze or do you get a segfault? If segfault -> post that log, then your bug is something else. -- 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/1453298 Title: Xubuntu freeze once a day To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1453298/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1453298]
My comment wont be very helpful... I tried kernel 4.1.6 from kernel.org and it doesnt freeze, but kernel 4.2 does (both selfcompiled). I then tried the legacy turbo patch on 4.2 and although it seems to last longer it does end with a full system freeze during video playback. Both used on the same system with baytrail i915 with nightly mesa/drivers. -- 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/1453298 Title: Xubuntu freeze once a day To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1453298/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1453298]
@Maxime Bergeron: It is helpful, I was recently wondering if I should switch back to the latest kernel on my Archlinux. Now I know I should better stick with the 3.14 LTS. Thanks. -- 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/1453298 Title: Xubuntu freeze once a day To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1453298/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1488599] Re: left click randomly stops working
Have updated to BIOS 2.A; will report back if problem reoccurs. -- 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/1488599 Title: left click randomly stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1488599/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1499055] [NEW] Wily: Mesa 11.0 causes hang in Intel Xorg driver, reverting to 10.6.3 fixes
Public bug reported: I am testing Wily on Kubuntu package set with SDDM display manager. After upgrading Mesa packages from 10.6.3 to 11.0.0 I found that graphical logon screen does not appear, and the system freezes with black screen, non-blinking cursor and non-responding keyboard I disabled SDDM service in systemctl and could log in to text console. Then I found that 'startx' command freezes the system as well. In dpkg.log I found that Mesa packages were updated last, from v. 10.6.3 to 11.0.0. I downloaded older versions from Ubuntu pool mirror and installed them by dpkg -i. After that, GUI operation was fixed, and I re-enabled SDDM and continue using my system without more significant problems. My system is Acer 1830T, made in 2010, CPU is Core i3-380UM with integrated GPU (Westmere/Ironlake/Arrandale, reported as gen5 in Xorg.0.log). Please investigate and fix this issue. Please ask me if you need more testing or more details. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1499055 Title: Wily: Mesa 11.0 causes hang in Intel Xorg driver, reverting to 10.6.3 fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1499055/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1406725] Re: Severe graphical corruption running software clients (including Xmir) on android
Alberto's previous fix is here: int mga::AndroidAllocAdaptor::convert_to_android_usage(BufferUsage usage) { switch (usage) { case mga::BufferUsage::use_hardware: return (GRALLOC_USAGE_HW_TEXTURE | GRALLOC_USAGE_HW_RENDER); case mga::BufferUsage::use_framebuffer_gles: return (GRALLOC_USAGE_HW_RENDER | GRALLOC_USAGE_HW_COMPOSER | GRALLOC_USAGE_HW_FB); case mga::BufferUsage::use_software: return (GRALLOC_USAGE_SW_WRITE_OFTEN | GRALLOC_USAGE_SW_READ_OFTEN | GRALLOC_USAGE_HW_COMPOSER | GRALLOC_USAGE_HW_TEXTURE); default: return -1; } } -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption running software clients (including Xmir) on android To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1406725] Re: Severe graphical corruption running software clients (including Xmir) on android
Is it safe to mix HW and SW flags? -- 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/1406725 Title: Severe graphical corruption running software clients (including Xmir) on android To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1496172] Re: It seems like something kicked me out from seance ((
** Information type changed from Private to Public ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- 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/1496172 Title: It seems like something kicked me out from seance (( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1496172/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1468373] Re: GPU driver issues when waking up from suspend mode
*** This bug is a duplicate of bug 1452318 *** https://bugs.launchpad.net/bugs/1452318 ** This bug has been marked a duplicate of bug 1452318 Faulty behavior when resuming from suspend -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1468373 Title: GPU driver issues when waking up from suspend mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1468373/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1432194] Re: Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics 5500
vivid issues after resume from suspend is a different bug, should be fixed by https://bugs.launchpad.net/ubuntu/vivid/+source/linux/+bug/1483320 (the "migrate bdw to i915_bpo" part) tracked also on bug 1452318 -- 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/1432194 Title: Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics 5500 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1432194/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1452318] Re: Faulty behavior when resuming from suspend
Awesome, latest kernel from vivid-proposed (3.19.0-30-generic) fixes the issue for me. Many thanks! -- 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/1452318 Title: Faulty behavior when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1452318/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1463926] Re: Removing HDMI cable will not always resize the desktop
Launchpad has imported 9 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=76464. 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 2014-03-21T18:09:25+00:00 Wayne-boyer wrote: 1. Connect a secondary monitor via HDMI 2. *Slowly* unplug the HDMI cable 3. Observe that there is no output retraining. The mouse can still be moved to the now unplugged external monitor. Looking at the output of "cat /sys/class/drm/*/status" shows that the kernel has the correct view of the current connection states. In the output below the states represent the three connections on the video card. card0-DVI-I-1 card0-DVI-I-2 card0-HDMI-A-1 ## Before plugging in monitor $ cat /sys/class/drm/*/status disconnected connected disconnected ## After plugging in monitor $ cat /sys/class/drm/*/status disconnected connected connected ## After slowly unplugging in monitor $ cat /sys/class/drm/*/status disconnected connected disconnected The output from xrandr shows the correct states when the secondary monitor is connected. $ xrandr Screen 0: minimum 320 x 200, current 4480 x 1600, maximum 8192 x 8192 DVI-I-1 disconnected (normal left inverted right x axis y axis) DVI-I-2 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 646mm x 406mm 2560x1600 59.9* 1280x800 59.9 HDMI-1 connected 1920x1080+2560+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 50.0 59.9 60.0 1920x1080i 60.1 50.0 60.0 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 59.9 1280x960 60.0 1366x768 59.8 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 720x57650.0 720x48060.0 59.9 640x48075.0 72.8 66.7 60.0 59.9 720x40070.1 After the cable is slowly unplugged, xrandr shows the monitor as disconnected, but still shows and idea of the last resolution. ** Also, running xrandr at this point kicks the system to retrain the output ** $ xrandr Screen 0: minimum 320 x 200, current 4480 x 1600, maximum 8192 x 8192 DVI-I-1 disconnected (normal left inverted right x axis y axis) DVI-I-2 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 646mm x 406mm 2560x1600 59.9* 1280x800 59.9 HDMI-1 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x481) 148.5MHz h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.5KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.0Hz Running xrandr once more shows the expected state of the system. $ xrandr Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 8192 x 8192 DVI-I-1 disconnected (normal left inverted right x axis y axis) DVI-I-2 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 646mm x 406mm 2560x1600 59.9* 1280x800 59.9 HDMI-1 disconnected (normal left inverted right x axis y axis) This problem reproduces on several platforms using various kernels and video cards. Here are two examples: - Arch linux, intel graphics (i915), 3.13 kernel - Linux Mint 13.10, nVidia (nouveau) graphics, 3.11 kernel This problem does not happen when the cable is disconnected quickly. Reply at: https://bugs.launchpad.net/xorg-server/+bug/1463926/comments/0 On 2014-03-21T18:14:16+00:00 Chris Wilson wrote: Hotplug interrupt is raised by hardware whilst the monitor is still connected. Only the manual probe sees the monitor as disconnected, triggering a round of userspace notifications and retraining. Use xrandr --current to avoid the manual probe. Reply at: https://bugs.launchpad.net/xorg-server/+bug/1463926/comments/1 On 2014-03-22T11:41:03+00:00 Daniel-ffwll wrote: Some guys at vpg are signed up to finally implement what I want here ... don't hold your breadth though :( Reply at: https://bugs.launchpad.net/xorg-server/+bug/1463926/comments/2 On 2014-03-26T21:26:52+00:00 Daniel-ffwll wrote: Downgrading to feature request since meh ... Hopefully someone gets around to actually write the code. Reply at: https://bugs.launchpad.net/xorg-server/+bug/1463926/comments/3 On 2014-03-27T07:34:22+00:00 Jani-nikula wrote: Sorry about
[Ubuntu-x-swat] [Bug 1496172] Re: [SNB] driver crash
** Summary changed: - It seems like something kicked me out from seance (( + [SNB] driver crash -- 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/1496172 Title: [SNB] driver crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1496172/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1490684] Re: Mouse cursor duplicated in dual screen setup
Eric Layton, if you upgrade to the Vivid enablement stack as outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack is this reproducible? ** Tags removed: bios-outdated-1402 ** Tags added: latest-bios-1402 ** Tags added: regression-release ** Changed in: xorg (Ubuntu) Importance: Low => Medium ** Changed in: xorg (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/1490684 Title: Mouse cursor duplicated in dual screen setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1490684/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1472272] Re: problems in X
Yes, I maked this and not resolved. I changed and nothing, it means I did what you said and nothing happened. -- 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/1472272 Title: problems in X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1472272/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1472272] Re: problems in X
Cassio, could you please clarify your comment: >"Yes, I changed and nothing." Are you saying that you uninstall fglrx and the problem was reproducible? -- 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/1472272 Title: problems in X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1472272/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1406725] Re: Severe graphical corruption running software clients (including Xmir) on android
I recall Alberto fixed a corruption bug just like this using magic HWC flags on the affected buffer. Not sure where that change went or if we still have it. -- 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/1406725 Title: Severe graphical corruption running software clients (including Xmir) on android To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1406725/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1472272] Re: problems in X
Cassio, to see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? -- 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/1472272 Title: problems in X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1472272/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1447313] Re: Synaptics two finger horizontal scrolling not enabled on Thinkpad Yoga 12
** Package changed: libevdev (Ubuntu) => xserver-xorg-input-synaptics (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1447313 Title: Synaptics two finger horizontal scrolling not enabled on Thinkpad Yoga 12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1447313/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp