[Desktop-packages] [Bug 1942993] Re: Fail to close the window by clicking "Done" button after adding "apps" to the skip list
Will install snap-store snap instead of hiding the "apps" page. ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1942993 Title: Fail to close the window by clicking "Done" button after adding "apps" to the skip list Status in gnome-initial-setup package in Ubuntu: Invalid Bug description: For the images which only pre-load ubuntu-desktop-minimal, snap-store snap package isn't installed by default. The page "apps" should be skipped. I add "apps" into the skip list. But, I cannot close the window by clicking "Done" button" after adding "apps" into the skip list. Here are my reproduction steps: 1. Add "apps" into the skip list. /usr/lib/gnome-initial-setup/vendor.conf [pages] -skip=language; +skip=language;apps; 2. Run gnome-initial-setup with --exisiting-user $ /usr/libexec/gnome-initial-setup --exisiting-user Test result: 40.4-1ubuntu1 (impish): Failed 3.36.2-0ubuntu2 (focal): Failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1942993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942993] [NEW] Fail to close the window by clicking "Done" button after adding "apps" to the skip list
Public bug reported: For the images which only pre-load ubuntu-desktop-minimal, snap-store snap package isn't installed by default. The page "apps" should be skipped. I add "apps" into the skip list. But, I cannot close the window by clicking "Done" button" after adding "apps" into the skip list. Here are my reproduction steps: 1. Add "apps" into the skip list. /usr/lib/gnome-initial-setup/vendor.conf [pages] -skip=language; +skip=language;apps; 2. Run gnome-initial-setup with --exisiting-user $ /usr/libexec/gnome-initial-setup --exisiting-user Test result: 40.4-1ubuntu1 (impish): Failed 3.36.2-0ubuntu2 (focal): Failed ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1941009 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1942993 Title: Fail to close the window by clicking "Done" button after adding "apps" to the skip list Status in gnome-initial-setup package in Ubuntu: New Bug description: For the images which only pre-load ubuntu-desktop-minimal, snap-store snap package isn't installed by default. The page "apps" should be skipped. I add "apps" into the skip list. But, I cannot close the window by clicking "Done" button" after adding "apps" into the skip list. Here are my reproduction steps: 1. Add "apps" into the skip list. /usr/lib/gnome-initial-setup/vendor.conf [pages] -skip=language; +skip=language;apps; 2. Run gnome-initial-setup with --exisiting-user $ /usr/libexec/gnome-initial-setup --exisiting-user Test result: 40.4-1ubuntu1 (impish): Failed 3.36.2-0ubuntu2 (focal): Failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1942993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Tags added: originate-from-1911479 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: Fix Released Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
I built the package in my local machine without problems. The issue in [1] is caused by the duplicate content in the attached patch (comment#9). In file included from ../../../../mi/misprite.c:48: ../../../../mi/mipointer.h:132:23: warning: redundant redeclaration of ‘miDCSaveUnderCursor2’ [-Wredundant-decls] 132 | extern _X_EXPORT void miDCSaveUnderCursor2(ScreenPtr pScreen); | ^~~~ ../../../../mi/mipointer.h:130:23: note: previous declaration of ‘miDCSaveUnderCursor2’ was here 130 | extern _X_EXPORT void miDCSaveUnderCursor2(ScreenPtr pScreen); | ^~~~ ../../../../mi/misprite.c:977:1: error: redefinition of ‘miDCSaveUnderCursor2’ 977 | miDCSaveUnderCursor2(ScreenPtr pScreen) | ^~~~ ../../../../mi/misprite.c:960:1: note: previous definition of ‘miDCSaveUnderCursor2’ was here 960 | miDCSaveUnderCursor2(ScreenPtr pScreen) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
@Timo I got the attached patch from [1] and found it has duplicate content. --- [1] https://launchpad.net/ubuntu/+source/xorg-server/2:1.20.10-3ubuntu6 ** Patch added: "300-mi-sprite-SaveUnderCursor2.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1920096/+attachment/5485754/+files/300-mi-sprite-SaveUnderCursor2.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for hirsute ** Patch added: "xorg-server_1.20.10-3ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1920096/+attachment/5478240/+files/xorg-server_1.20.10-3ubuntu4.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for focal ** Patch added: "xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1920096/+attachment/5478242/+files/xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Description changed: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- - Xilinx has upstreamed the patch. + Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html - But, it's still under review. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority/focal Importance: Undecided => High ** Changed in: oem-priority Importance: High => Critical ** Changed in: oem-priority/focal Importance: High => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for hirsute ** Patch added: "xorg-server_1.20.10-3ubuntu4.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1920096/+attachment/5478041/+files/xorg-server_1.20.10-3ubuntu4.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
The issue is fixed by the attached patch in comment#1 and #2. Please help to review and integrate it to hirsute and focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for focal ** Patch added: "xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1920096/+attachment/5478042/+files/xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff ** Description changed: [Impact] - The cursor bleeds because of the bug in xorg which does not refresh the sprite background. + The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] [NEW] Cursor bleeds on the platform with Mali armsoc driver
Public bug reported: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. ** Affects: oem-priority Importance: Critical Status: New ** Affects: oem-priority/focal Importance: Critical Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/focal Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: New Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
The issue is gone after upgrading gnome-control-center. --- Bionic: ubuntu-18.04.2-desktop-amd64.iso Xenial: ubuntu-gnome-16.04.5-desktop-amd64.iso ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in OEM Priority Project xenial series: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Xenial: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-control-center source package in Disco: Fix Released Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
The issue is gone after upgrading gnome-control-center to 1:3.32.2-0ubuntu1. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: Fix Committed Status in OEM Priority Project bionic series: Fix Committed Status in OEM Priority Project xenial series: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Disco: Fix Committed Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
@Sebastien Please check the diff for xenial as attached. ** Patch added: "xenial.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261724/+files/xenial.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Patch added: "disco.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261105/+files/disco.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Patch added: "xenial.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261103/+files/xenial.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Patch added: "bionic.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261104/+files/bionic.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
@Sebastien The description has been updated. ** Description changed: [Impact] - Power: Fail to set delay time when the value is 90 minutes + Fail to set delay time when the value is 90 minutes. + + In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 + (90*60). When setting the delay time to 90 minutes, the UI will show "80 + minutes" after reopening "All Settings". (Please refer to the photo in + #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] - 5) The value of delay time is 80 minutes + 5) Check if the value is 90 minutes. + + [Regression Potential] + + Low. The value of 90 minutes is wrong. Just correct the value to 5400. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: Confirmed Bug description: [Impact] Fail to set delay time when the value is 90 minutes. In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 (90*60). When setting the delay time to 90 minutes, the UI will show "80 minutes" after reopening "All Settings". (Please refer to the photo in #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) Check if the value is 90 minutes. [Regression Potential] Low. The value of 90 minutes is wrong. Just correct the value to 5400. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
The attached patch has been accepted by upstream. Please help to backport it to bionic and xenial. ** Patch added: "0001-power-correct-the-value-of-90-minutes-to-5400.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260824/+files/0001-power-correct-the-value-of-90-minutes-to-5400.patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority/bionic Importance: Undecided => High ** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] Power: Fail to set delay time when the value is 90 minutes [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) The value of delay time is 80 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] [NEW] Power: Fail to set delay time when the value is 90 minutes
Public bug reported: [Impact] Power: Fail to set delay time when the value is 90 minutes [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) The value of delay time is 80 minutes ** Affects: oem-priority Importance: High Status: New ** Affects: oem-priority/bionic Importance: High Status: New ** Affects: oem-priority/xenial Importance: High Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Changed in: oem-priority/bionic Importance: Undecided => High ** Changed in: oem-priority/xenial Importance: Undecided => High ** No longer affects: oem-priority ** No longer affects: oem-priority/bionic ** No longer affects: oem-priority/xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] Power: Fail to set delay time when the value is 90 minutes [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) The value of delay time is 80 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Attachment added: "1_set-delay-to-90-mins.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260822/+files/1_set-delay-to-90-mins.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] Power: Fail to set delay time when the value is 90 minutes [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) The value of delay time is 80 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Attachment added: "2_value-is-80-after-reopen-power-settings.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260823/+files/2_value-is-80-after-reopen-power-settings.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in OEM Priority Project xenial series: New Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] Power: Fail to set delay time when the value is 90 minutes [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) The value of delay time is 80 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827030] Re: Keyboard brightness control not working
@Sebastien Yes. I have one project using GNOME. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827030 Title: Keyboard brightness control not working Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: [Impact] Keyboard brightness control not working [Test Case] 1) Go to [All Settings][Power][Keyboard brightness] 2) Adjust keyboard brightness by sidebar --- $ cat /sys/class/leds/dell::/kbd_backlight/max_brightness 2 The valid value for my machine is 0, 1, and 2. The Power.Keyboard.Brightness property should be in percent. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827030] [NEW] Keyboard brightness control not working
Public bug reported: [Impact] Keyboard brightness control not working [Test Case] 1) Go to [All Settings][Power][Keyboard brightness] 2) Adjust keyboard brightness by sidebar --- $ cat /sys/class/leds/dell::/kbd_backlight/max_brightness 2 The valid value for my machine is 0, 1, and 2. The Power.Keyboard.Brightness property should be in percent. ** Affects: oem-priority Importance: High Status: New ** Affects: oem-priority/xenial Importance: High Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-New-upstream-bug-fix-release.patch" https://bugs.launchpad.net/bugs/1827030/+attachment/5260251/+files/0001-New-upstream-bug-fix-release.patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827030 Title: Keyboard brightness control not working Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: [Impact] Keyboard brightness control not working [Test Case] 1) Go to [All Settings][Power][Keyboard brightness] 2) Adjust keyboard brightness by sidebar --- $ cat /sys/class/leds/dell::/kbd_backlight/max_brightness 2 The valid value for my machine is 0, 1, and 2. The Power.Keyboard.Brightness property should be in percent. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827030] Re: Keyboard brightness control not working
The issue can be fixed by the commit below. Please help to backport it to xenial. commit 2b28b00a7e9ef21d3b94277e517692896e46e58c Author: Hans de Goede Date: Fri Oct 14 18:25:35 2016 +0200 power: The Power.Keyboard.Brightness property is in percent -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827030 Title: Keyboard brightness control not working Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: [Impact] Keyboard brightness control not working [Test Case] 1) Go to [All Settings][Power][Keyboard brightness] 2) Adjust keyboard brightness by sidebar --- $ cat /sys/class/leds/dell::/kbd_backlight/max_brightness 2 The valid value for my machine is 0, 1, and 2. The Power.Keyboard.Brightness property should be in percent. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824073] Re: USB stick isn't mounted automatically
@Mathew I didn't find the patch in latest udisk2 (xenial) from the link below. https://launchpad.net/ubuntu/+source/udisks2 May I know when it will be landed to udisks2 (xenial)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Xenial: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824073] Re: USB stick isn't mounted automatically
@Sebastien Please check the attached file. ** Patch added: "0001-New-upstream-bug-fix-release.patch" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1824073/+attachment/5256492/+files/0001-New-upstream-bug-fix-release.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in udisks2 package in Ubuntu: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824073] Re: USB stick isn't mounted automatically
** Patch added: "Do-not-add-new-drive-object-on-change-uevent.patch" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1824073/+attachment/5256478/+files/Do-not-add-new-drive-object-on-change-uevent.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in udisks2 package in Ubuntu: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824073] Re: USB stick isn't mounted automatically
** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in udisks2 package in Ubuntu: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824073] Re: USB stick isn't mounted automatically
This issue fixed by the commit below. Please help to backport the patch to xenial. commit 3574f9876634c29091655733a8f07ab5c242 Author: Tomas Smetana Date: Wed Oct 12 09:47:03 2016 +0200 Don't add new drive object on "change" uevent -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in udisks2 package in Ubuntu: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824073] [NEW] USB stick isn't mounted automatically
Public bug reported: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: oem-priority/xenial Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1824073/+attachment/5254607/+files/syslog.txt ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** No longer affects: oem-priority/xenial ** No longer affects: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in udisks2 package in Ubuntu: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kern
[Desktop-packages] [Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
@Brian The issue is gone after upgrading gnome-settings-daemon to 3.28.1-0ubuntu1.1. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Committed Bug description: [Impact] The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx is larger than 127. Settings will always shows Bluetooth is off after resume. The solution is to set the encoding of GIOChannel as NULL (binary data). [Test Case] 1) Enable the -proposed repository, and install new "gnome-settings- daemon-schemas" and "gnome-settings-daemon" 2) Reboot system 3) Run suspend/resume test more than 127 times and then check if BT settings still works well. [Regression Potential] Low. The default encoding for GIOChannel is wrong. Just set correct encoding to receive rfkill event. --- The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
@Sebastien The patch has been merged. Could you help to land it to bionic? Thanks~ commit a5514ae097e5881df3ef26c63f4f4652b3f77811 Author: Ethan Hsieh Date: Tue Oct 9 10:28:31 2018 +0800 rfkill: set encoding as NULL The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: [Impact] The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx is larger than 127. Settings will always shows Bluetooth is off after resume. The solution is to set the encoding of GIOChannel as NULL (binary data). [Test Case] 1) Enable the -proposed repository, and install new "gnome-settings- daemon-schemas" and "gnome-settings-daemon" 2) Reboot system 3) Run suspend/resume test more than 127 times and then check if BT settings still works well. [Regression Potential] Low. The default encoding for GIOChannel is wrong. Just set correct encoding to receive rfkill event. --- The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
Thanks for your reminder. Bug description has been updated. ** Description changed: + [Impact] + + The default encoding for GIOChannel is UTF-8, but rfkill event is binary + data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx + is larger than 127. + + The solution is to set the encoding of GIOChannel as NULL (binary data). + + [Test Case] + + 1) Enable the -proposed repository, and install new "gnome-settings- + daemon-schemas" and "gnome-settings-daemon" + + 2) Reboot system + + 3) Run suspend/resume test more than 127 times and then check if BT + settings still works well. + + [Regression Potential] + + Low. The default encoding for GIOChannel is wrong. Just set correct + encoding to receive rfkill event. + + --- + The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 ** Description changed: [Impact] The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx is larger than 127. + + Settings will always shows Bluetooth is off after resume. The solution is to set the encoding of GIOChannel as NULL (binary data). [Test Case] 1) Enable the -proposed repository, and install new "gnome-settings- daemon-schemas" and "gnome-settings-daemon" 2) Reboot system 3) Run suspend/resume test more than 127 times and then check if BT settings still works well. [Regression Potential] Low. The default encoding for GIOChannel is wrong. Just set correct encoding to receive rfkill event. --- The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: [Impact] The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx is larger than 127. Settings will always shows Bluetooth is off a
[Desktop-packages] [Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
Have sent a merge request to GitLab and wait for approval. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/57 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event Status in gnome-settings-daemon package in Ubuntu: New Bug description: The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797322] [NEW] gsd-rfkill-manager fails to receive rfkill event
Public bug reported: The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic ** Patch added: "0001-rfkill-set-encoding-as-NULL.patch" https://bugs.launchpad.net/bugs/1797322/+attachment/5199851/+files/0001-rfkill-set-encoding-as-NULL.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event Status in gnome-settings-daemon package in Ubuntu: New Bug description: The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789201] Re: prime-select doesn't work in phase 2
The issue is gone after installing packages at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.5.2.1. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1789201 Title: prime-select doesn't work in phase 2 Status in HWE Next: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] We need to be able to disable the discrete GPU in phase 2 of the oem installer*, and this requires running gpu-manager.service before oem-config.service. [Test Case] Add the new ubuntu-drivers-common in -proposed repository, and see if gpu-manager.service is called in phase 2. [Regression Potential] Low, as no action will be taken unless custom settings for hybrid graphics are available. *What is "phase 2" (Booting from the recovery partition, and installing Ubuntu): https://docs.google.com/presentation/d/18q2VtQt3OJzh12--2Llzwz36DlF3Lca6iLPCnhIbQds/edit?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1789201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789201] Re: prime-select doesn't work in phase 2
** Description changed: SRU Request: [Impact] We need to be able to disable the discrete GPU in phase 2 of the oem installer, and this requires running gpu-manager.service before oem-config.service. [Test Case] Add the new ubuntu-drivers-common in -proposed repository, and see if gpu-manager.service is called in phase 2. [Regression Potential] Low, as no action will be taken unless custom settings for hybrid graphics are available. + + What is "phase 2": + https://docs.google.com/presentation/d/18q2VtQt3OJzh12--2Llzwz36DlF3Lca6iLPCnhIbQds/edit?usp=sharing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1789201 Title: prime-select doesn't work in phase 2 Status in HWE Next: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Bug description: SRU Request: [Impact] We need to be able to disable the discrete GPU in phase 2 of the oem installer*, and this requires running gpu-manager.service before oem-config.service. [Test Case] Add the new ubuntu-drivers-common in -proposed repository, and see if gpu-manager.service is called in phase 2. [Regression Potential] Low, as no action will be taken unless custom settings for hybrid graphics are available. *What is "phase 2" (Booting from the recovery partition, and installing Ubuntu): https://docs.google.com/presentation/d/18q2VtQt3OJzh12--2Llzwz36DlF3Lca6iLPCnhIbQds/edit?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1789201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Triaged Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
@Timo Here is the test result of mesa (xenial-proposed) A. Test Result: 1. DRI_PRIME=1 glxgear: Pass 2. DRI_PRIME=1 glxgear -fulscreen: Pass 3. glxgear: Pass 4. glxgear -fulscreen: Pass 5. Unigine_Heaven-4.0.run (5mins): Pass 6. Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass 7. DRI_PRIME=1 Unigine_Heaven-4.0.run (5mins): Pass 8. DRI_PRIME=1 Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass B. Test Environment: 1. Ubuntu: Xenial 16.04 2. Graphic Card: b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) 3.Installed package: a. Online Update b. Enable xenial-proposed and then upgrade mesa libglapi-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-dri_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libxatracker2_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libwayland-egl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-glx_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgbm1_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libegl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb ** Tags removed: verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Triaged Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
@Timo Here is the test result for mesa (17.2.4-0ubuntu1~16.04.3~1) A. Test Result: 1. DRI_PRIME=1 glxgear: Pass 2. DRI_PRIME=1 glxgear -fulscreen: Pass 3. glxgear: Pass 4. glxgear -fulscreen: Pass 5. Change Resolution: Pass 6. Scale for menu and title bars: Pass 7. Unigine_Heaven-4.0.run (5mins): Pass 8. Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass B. Test Environment: 1. Ubuntu: Xenial 16.04 2. Graphic Card: b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) 3.Installed package: a. Online Update b. mesa (17.2.4-0ubuntu1~16.04.3~1) libglapi-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-dri_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libxatracker2_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libwayland-egl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-glx_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgbm1_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libegl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb 4. src: https://launchpad.net/~tjaalton/+archive/ubuntu/ppa/+files/mesa_17.2.4-0ubuntu1~16.04.3~1.dsc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: In Progress Status in mesa source package in Xenial: Triaged Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
Cannot reproudce the issue on xenial. A. Test Result: 1. DRI_PRIME=1 glxgear -info: Pass 2. Change Resolution: Pass 3. Scale for menu and title bars: Pass 4. Unigine_Heaven-4.0.run (5mins): Pass B. Test Environment: 1. Ubuntu: Xenial 16.04 2. Graphic Card: a. AMD [1002:9874] (rev e2) b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) 3.Installed package: (Online Update: xenial-proposed: mesa) libdrm-common all 2.4.83-1~16.04.1 libdrm2 amd64 2.4.83-1~16.04.1 libcapnp-0.5.3 amd64 0.5.3-2ubuntu1 libdrm-amdgpu1 amd64 2.4.83-1~16.04.1 libwayland-egl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libwayland-client0 amd64 1.12.0-1~ubuntu16.04.2 libwayland-server0 amd64 1.12.0-1~ubuntu16.04.2 libegl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libgbm1 amd64 17.2.4-0ubuntu1~16.04.2 libmircore1 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmircommon7 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirprotobuf3 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirclient9 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libllvm5.0 amd64 1:5.0-3~16.04.1 libgl1-mesa-dri amd64 17.2.4-0ubuntu1~16.04.2 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727390] Re: New bugfix release 17.2.4
mesa 17.2.4 works well on my two devices. Here is the test result: 1) AMD [1002:9874] (rev e2) glxgear -info: Pass Unigine_Heaven-4.0 (5mins): Pass 2) Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) glxgear -info: Pass DRI_PRIME=1 glxgear -info: Pass Unigine_Heaven-4.0 (5mins): Pass DRI_PRIME=1 Unigine_Heaven-4.0.run (5mins): Pass --- Installed package: (Online Update: xenial-proposed: mesa) libdrm-common all 2.4.83-1~16.04.1 libdrm2 amd64 2.4.83-1~16.04.1 libcapnp-0.5.3 amd64 0.5.3-2ubuntu1 libdrm-amdgpu1 amd64 2.4.83-1~16.04.1 libwayland-egl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libwayland-client0 amd64 1.12.0-1~ubuntu16.04.2 libwayland-server0 amd64 1.12.0-1~ubuntu16.04.2 libegl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libgbm1 amd64 17.2.4-0ubuntu1~16.04.2 libmircore1 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmircommon7 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirprotobuf3 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirclient9 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libllvm5.0 amd64 1:5.0-3~16.04.1 libgl1-mesa-dri amd64 17.2.4-0ubuntu1~16.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)
Filed one freedesktop bug for this issue. https://bugs.freedesktop.org/show_bug.cgi?id=102508 ** Bug watch added: freedesktop.org Bugzilla #102508 https://bugs.freedesktop.org/show_bug.cgi?id=102508 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)
After applying the following patch, there is no pop-up window (#24). But, all three screens turn into black screens after I click "apply" button. hw/xfree86/drivers/modesetting/drmmode_display.c: -xf86CrtcSetSizeRange(pScrn, 320, 200, mode_res->max_width, mode_res->max_height); +xf86CrtcSetSizeRange(pScrn, 320, 200, INT16_MAX, INT16_MAX); xorg-server: 1.19.3-1ubuntu1.1 ubuntu: 17.04 ** Attachment added: "Xorg.0.log (17.04)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+attachment/4941803/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941765/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)
** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+attachment/4941782/+files/Screenshot%20from%202017-08-31%2015-26-31.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941775/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941766/+files/LightdmLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941770/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941772/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941768/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941771/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941769/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941773/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941774/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941779/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941767/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941781/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] make.log.txt
apport information ** Attachment added: "make.log.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941780/+files/make.log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941778/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941777/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941776/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941760/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941764/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941763/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] DkmsStatus.txt
apport information ** Attachment added: "DkmsStatus.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941761/+files/DkmsStatus.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941762/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)
apport information ** Tags added: apport-collected compiz-0.9 ubuntu xenial ** Description changed: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi + --- + .tmp.unity_support_test.0: + + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: compiz + CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' + CompositorUnredirectFSW: true + CurrentDesktop: Unity + DistUpgraded: Fresh install + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) +Subsystem: Dell Device [1028:07bf] +Subsystem: Dell Device [1028:07bf] + InstallationDate: Installed on 2017-08-29 (2 days ago) + InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 + MachineType: Dell Inc. Precision 5520 + Package: xorg-server (not installed) + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 + Tags: xenial ubuntu compiz-0.9 + Uname: Linux 4.11.0-14-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/08/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.3.3 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: + dmi.product.name: Precision 5520 + dmi.sys.vendor: Dell Inc. + version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 + version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941759/+files/BootLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Status in xorg-server package in Ubuntu: New Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/gene
[Desktop-packages] [Bug 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
@Alberto fglrx 2:14.101-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer source package in Trusty: Fix Committed Status in fglrx-installer-updates source package in Trusty: Fix Committed Bug description: SRU Request: [Impact] Upgrading from the upstream fglrx driver packages to the packages in the Ubuntu repository fails because the /etc/ati directory is a real directory instead of being a link (which was common in the Ubuntu packages). [Test Case] 1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages from the AMD installer 2. Upgrade the package to the current ubuntu release. 3. Check the apt-get output Expected results: the fglrx module should be updated correctly. Actual results: The update fails as described below. [Regression Potential] Low. The change only affects a migration from a specific release. __ Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 X-HWE-Bug: Bug #1664810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639896] Re: Backport support for AMD Polaris
I have verified xserver-xorg-video-amdgpu (1.1.2) and mesa (12.0.6) Test result: 1. glxgears: Pass 2. glmark2: Pass 3. S3 Test: Pass (sudo fwts s3 --s3-multiple=30 --s3-min-delay=30 --s3-max-delay=30) Test Environment 1. Kernel: 4.4.0-49-generic 2. VGA compatible controller [AMD/ATI] Device [1002:67df], Kernel driver in use: amdgpu 3. Installed packages: amdgpu-pro-dkms (16.60-377537) xserver-xorg-video-amdgpu (1.1.2-0ubuntu0.16.04.1) libegl1-mesa-drivers:amd64 (12.0.6-0ubuntu0.16.04.1) libgbm1:amd64 (12.0.6-0ubuntu0.16.04.1) libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1) libglapi-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libgles1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libgles2-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libosmesa6:amd64 (12.0.6-0ubuntu0.16.04.1) libxatracker2:amd64 (12.0.6-0ubuntu0.16.04.1) libegl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libgl1-mesa-glx:amd64 (12.0.6-0ubuntu0.16.04.1) libwayland-egl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport support for AMD Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: Fix Committed Bug description: [Impact] Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6 backported instead [Test case] Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration [Regression potential] This is a stable upstream release, and 16.10 ships the same versions so regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638495] Re: Blank screen after wakeup from suspend
Log: (unity-settings-daemon:1845): power-plugin-DEBUG: ==> system wakes up after pressing the key Received session is active change: now inactive Received session is active change: now active Doing a state transition: normal TESTSUITE: Unblanked screen Adding suspend delay inhibitor Received screensaver ActiveChanged signal: 1 (old: 0) setting up blank callback for 15s setting up sleep callback 300s setting up sleep warning callback 240s Doing a state transition: blank TESTSUITE: Blanked screen keyboard toggle on Received screensaver ActiveChanged signal: 1 (old: 1) Received screensaver ActiveChanged signal: 0 (old: 1) setting up sleep callback 300s setting up sleep warning callback 240s Received screensaver ActiveChanged signal: 0 (old: 0) ==> screen is blank although system wakes up ==> have to press the key again to turn on the screen power-plugin-DEBUG: idletime reset power-plugin-DEBUG: Doing a state transition: normal power-plugin-DEBUG: TESTSUITE: Unblanked screen power-plugin-DEBUG: keyboard toggle off -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1638495 Title: Blank screen after wakeup from suspend Status in gnome-screensaver package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using lsb_release: Ubuntu 16.04 LTS release 16.04 kernel: 4.4.0-36-generic 2) The version of the package you are using gnome-screensaver: 3.6.1-7ubuntu4 unity-settings-daemon: 15.04.1+16.04.20160701-0ubuntu1 Graphic: nvidia (driver 370.23) 3) What you expected to happen screen is on after wakeup from suspend 4) What happened instead screen is blank although system wakes up 5) Failure rate: 1/5 6) How to reproduce this issue: a. [System Menu] => [Suspend] b. press the key to wake up system c. screen is blank although system wakes up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1638495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638495] [NEW] Blank screen after wakeup from suspend
Public bug reported: 1) The release of Ubuntu you are using lsb_release: Ubuntu 16.04 LTS release 16.04 kernel: 4.4.0-36-generic 2) The version of the package you are using gnome-screensaver: 3.6.1-7ubuntu4 unity-settings-daemon: 15.04.1+16.04.20160701-0ubuntu1 Graphic: nvidia (driver 370.23) 3) What you expected to happen screen is on after wakeup from suspend 4) What happened instead screen is blank although system wakes up 5) Failure rate: 1/5 6) How to reproduce this issue: a. [System Menu] => [Suspend] b. press the key to wake up system c. screen is blank although system wakes up ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1638495 Title: Blank screen after wakeup from suspend Status in gnome-screensaver package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using lsb_release: Ubuntu 16.04 LTS release 16.04 kernel: 4.4.0-36-generic 2) The version of the package you are using gnome-screensaver: 3.6.1-7ubuntu4 unity-settings-daemon: 15.04.1+16.04.20160701-0ubuntu1 Graphic: nvidia (driver 370.23) 3) What you expected to happen screen is on after wakeup from suspend 4) What happened instead screen is blank although system wakes up 5) Failure rate: 1/5 6) How to reproduce this issue: a. [System Menu] => [Suspend] b. press the key to wake up system c. screen is blank although system wakes up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1638495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
