[Desktop-packages] [Bug 2068904] Re: Screen restarts and logs out when disconnecting HDMI cable
>From our OEM bugs, remove below file may help ~/.config/monitors.xml -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2068904 Title: Screen restarts and logs out when disconnecting HDMI cable Status in gnome-shell package in Ubuntu: Incomplete Bug description: Replication steps: 1. Start up Ubuntu desktop as usual with HDMI cable connected to external monitor in extended desktop mode. 2. Log in to Ubuntu desktop. 3. Launch a few applications (e.g. browser, terminal, etc). 4. Disconnect HDMI cable. Expected behaviour: Desktop session should still be available on laptop screen after disconnecting HDMI cable. Current behaviour: Laptop screen goes black and shows the login screen. Logging in again shows a fresh desktop session (no open application windows). Other information: This is a dual-OS machine, with home directory encryption enabled for Ubuntu. Installed from Mantic originally, and upgraded to Noble via command line. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-desktop 1.539 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 21:51:29 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2024-03-14 (88 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068904/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Updated xserver-xorg-core to 21.1.4-2ubuntu1.4(kinetic) with the same test on comment #14, toggle display works ii xserver-xorg-core 2:21.1.4-2ubuntu1.4 amd64Xorg X server - core server ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- 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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
xserver-xorg-core 21.1.3-2ubuntu2.5 1. power off the machine 2. connect DP monitor on the dock 3. plug the dock type-c cable to the machine 4. waiting the machine auto bootup, and no output on the DP monitor 5. no external monitor found in display menu updated xserver-xorg-core to 21.1.3-2ubuntu2.6 1. power off the machine 2. connect DP monitor on the dock 3. plug the dock type-c cable to the machine 4. waiting the machine auto bootup, and no output on the DP monitor 5. found monitor in display menu and win + p toggle display mode work ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 -- 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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Confirmed Status in xorg-server source package in Kinetic: Confirmed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Add back the check for xf86ModeVRefresh() returns 0, the patch works on my laptop and the target 2.5k 90Hz panel. Will submit another MR soon. ** Patch added: "0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+attachment/5637169/+files/0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Confirmed Status in xorg-server source package in Kinetic: Confirmed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999852] Re: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults
*** This bug is a duplicate of bug 1999008 *** https://bugs.launchpad.net/bugs/1999008 Right, I updated the check, will verify it again, thanks. -- 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/1999852 Title: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults Status in xorg-server package in Ubuntu: New Bug description: Running xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb was fine. Since the recent update to xserver-xorg-core_21.1.3-2ubuntu2.5_amd64.deb Xorg always segfaults at startup. Going back to xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb works again. (Tried it multiple times and it is reproducable.) The errors from the last Xorg.log: [54.562] (EE) Backtrace: [54.563] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560707b09719] [54.564] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40658cd520] [54.564] (EE) 2: /usr/lib/xorg/Xorg (xf86ModeVRefresh+0x4) [0x560707a0e724] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 3: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513b9b0] [54.565] (EE) 4: /usr/lib/xorg/Xorg (xf86ProbeOutputModes+0x147) [0x560707a07e47] [54.565] (EE) 5: /usr/lib/xorg/Xorg (xf86InitialConfiguration+0x191) [0x560707a089b1] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 6: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513f07c] [54.566] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.566] (EE) 7: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f40651374bf] [54.566] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xb8b) [0x5607079d73ab] [54.566] (EE) 9: /usr/lib/xorg/Xorg (InitFonts+0x1dc) [0x56070799734c] [54.567] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40658b4d90] [54.567] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40658b4e40] [54.568] (EE) 12: /usr/lib/xorg/Xorg (_start+0x25) [0x560707980605] [54.568] (EE) [54.568] (EE) Segmentation fault at address 0xa8 [54.568] (EE) Fatal server error: [54.568] (EE) Caught signal 11 (Segmentation fault). Server aborting [54.568] (EE) [54.568] (EE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999852/+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 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialCon
Adopt the fix by Markus on bug 1999852 Verified it on my laptop, it works, and will verify more sku and the target 2.5k panel with 90Hz machines later. ** Patch added: "0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+attachment/5636938/+files/0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server source package in Jammy: Confirmed Status in xorg-server source package in Kinetic: Confirmed Status in xorg-server source package in Lunar: Confirmed Bug description: [Impact] The recent SRU'd patch had a bug in it that caused a crash if xf86ModeVRefresh returned 0. Amend the patch to fix this. [Test case] Would need an affected system to test this on, but we haven't been able to reproduce this even on an identical system as on one of the reported errors (XPS 15 9560). [Where things could go wrong] This only adds a new check. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.4-2ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/67a241f90d338c8f1b9c48466cf1f6121bece6bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+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 1999852] Re: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults
*** This bug is a duplicate of bug 1999008 *** https://bugs.launchpad.net/bugs/1999008 Hi Markus, Thanks for reporting the preferred issue, I'll submit new MR soon. -- 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/1999852 Title: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults Status in xorg-server package in Ubuntu: New Bug description: Running xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb was fine. Since the recent update to xserver-xorg-core_21.1.3-2ubuntu2.5_amd64.deb Xorg always segfaults at startup. Going back to xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb works again. (Tried it multiple times and it is reproducable.) The errors from the last Xorg.log: [54.562] (EE) Backtrace: [54.563] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560707b09719] [54.564] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40658cd520] [54.564] (EE) 2: /usr/lib/xorg/Xorg (xf86ModeVRefresh+0x4) [0x560707a0e724] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 3: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513b9b0] [54.565] (EE) 4: /usr/lib/xorg/Xorg (xf86ProbeOutputModes+0x147) [0x560707a07e47] [54.565] (EE) 5: /usr/lib/xorg/Xorg (xf86InitialConfiguration+0x191) [0x560707a089b1] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 6: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513f07c] [54.566] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.566] (EE) 7: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f40651374bf] [54.566] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xb8b) [0x5607079d73ab] [54.566] (EE) 9: /usr/lib/xorg/Xorg (InitFonts+0x1dc) [0x56070799734c] [54.567] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40658b4d90] [54.567] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40658b4e40] [54.568] (EE) 12: /usr/lib/xorg/Xorg (_start+0x25) [0x560707980605] [54.568] (EE) [54.568] (EE) Segmentation fault at address 0xa8 [54.568] (EE) Fatal server error: [54.568] (EE) Caught signal 11 (Segmentation fault). Server aborting [54.568] (EE) [54.568] (EE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999852/+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 1996490] Re: Failed to set resolutions with 2.5k@90Hz panels
Upgraded Jammy to xserver-xorg-core 2:21.1.3-2ubuntu2.4, switching to different resolutions work well. Upgrade Kinetic to xserver-xorg-core 2:21.1.4-2ubuntu1.2, switching to different resolutions also work well. ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- 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/1996490 Title: Failed to set resolutions with 2.5k@90Hz panels Status in HWE Next: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: In Progress Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Status in xorg-server source package in Lunar: In Progress Bug description: [Impact] Failed to set resolutions with new 2.5k@90Hz panels, the reported resolutions from xrandr are all invalid and got blank screen. [Fix] Below commit re-calculate clock and refresh rate fixes this issue. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 [Test] Verified on 2.5k@90Hz panel laptops and my laptop 1920x1080@60Hz Will be tested in proposed for wider range. [Where problems could occur] Not sure if the re-calculated clock and refresh rate works for all different panels, need to verify it wider in proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996490/+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 1996490] Re: Failed to set resolutions with 2.5k@90Hz panels
** Description changed: [Impact] + Failed to set resolutions with new 2.5k@90Hz panels, the reported resolutions from xrandr are all invalid and got blank screen. [Fix] + Below commit re-calculate clock and refresh rate fixes this issue. + https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 [Test] + Verified on 2.5k@90Hz panel laptops and my laptop 1920x1080@60Hz [Where problems could occur] + Not sure if the re-calculated clock and refresh rate works for all different panels, need to verify it wider in proposed. ** Patch added: "0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1996490/+attachment/5630714/+files/0001-hw-xfree86-re-calculate-the-clock-and-refresh-rate.patch ** Changed in: xorg-server (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: xorg-server (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: xorg-server (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1989829 somerville ** Description changed: [Impact] Failed to set resolutions with new 2.5k@90Hz panels, the reported resolutions from xrandr are all invalid and got blank screen. [Fix] Below commit re-calculate clock and refresh rate fixes this issue. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 [Test] Verified on 2.5k@90Hz panel laptops and my laptop 1920x1080@60Hz - + Will be tested in proposed for wider range. + [Where problems could occur] Not sure if the re-calculated clock and refresh rate works for all different panels, need to verify it wider in proposed. -- 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/1996490 Title: Failed to set resolutions with 2.5k@90Hz panels Status in HWE Next: New Status in xorg-server package in Ubuntu: In Progress Status in xorg-server source package in Jammy: In Progress Status in xorg-server source package in Kinetic: In Progress Status in xorg-server source package in Lunar: In Progress Bug description: [Impact] Failed to set resolutions with new 2.5k@90Hz panels, the reported resolutions from xrandr are all invalid and got blank screen. [Fix] Below commit re-calculate clock and refresh rate fixes this issue. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 [Test] Verified on 2.5k@90Hz panel laptops and my laptop 1920x1080@60Hz Will be tested in proposed for wider range. [Where problems could occur] Not sure if the re-calculated clock and refresh rate works for all different panels, need to verify it wider in proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996490/+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 1996490] [NEW] Failed to set resolutions with 2.5k@90Hz panels
Public bug reported: [Impact] Failed to set resolutions with new 2.5k@90Hz panels, the reported resolutions from xrandr are all invalid and got blank screen. [Fix] Below commit re-calculate clock and refresh rate fixes this issue. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 [Test] Verified on 2.5k@90Hz panel laptops and my laptop 1920x1080@60Hz [Where problems could occur] Not sure if the re-calculated clock and refresh rate works for all different panels, need to verify it wider in proposed. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: xorg-server (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: xorg-server (Ubuntu Kinetic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: xorg-server (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: oem-priority originate-from-1989829 somerville ** Also affects: xorg-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Jammy) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Kinetic) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Lunar) Status: New => In Progress -- 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/1996490 Title: Failed to set resolutions with 2.5k@90Hz panels Status in HWE Next: New Status in xorg-server package in Ubuntu: In Progress Status in xorg-server source package in Jammy: In Progress Status in xorg-server source package in Kinetic: In Progress Status in xorg-server source package in Lunar: In Progress Bug description: [Impact] Failed to set resolutions with new 2.5k@90Hz panels, the reported resolutions from xrandr are all invalid and got blank screen. [Fix] Below commit re-calculate clock and refresh rate fixes this issue. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/993 [Test] Verified on 2.5k@90Hz panel laptops and my laptop 1920x1080@60Hz [Where problems could occur] Not sure if the re-calculated clock and refresh rate works for all different panels, need to verify it wider in proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996490/+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 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)
I can reproduce this issue, too. When plug in the dock(with HDMI 4k monitor), the screen freeze and keyboard/touchpad won't work, but I still can ssh into the machine. Un-plug the dock, everything works again. BTW, I found gnome-shell runs in 100% while the issue happened, and un- plug the dock the CPU usage of gnome-shell comes back to normal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970495 Title: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed) Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: 1. Problem DOES appear on Lenovo T470s (Intel). 2. Problem DOES appear on Lenovo T14 Gen2 (AMD). 3. Problem does NOT appear on either of the above *when in the Live Installer*. I specifically checked that my dock behaved well under the Live Installer before deciding to move my workstations to Jammy. Upon logging into a fresh Jammy install, I found the following problem behavior: When the dock is plugged in, the built-in display freezes and the dock-attached displays power up but never render anything (ie, they stay black). Unplugging the USB-C cable gets mouse/keyboard response back on the built-in display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:32:35 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970495/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
SRU sent
https://lists.ubuntu.com/archives/kernel-team/2022-April/129627.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Description changed:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
- b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
- b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
- b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
- b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
+ b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
+ b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
+ b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
+
+ ==
+
+ SRU Justification
+
+ [Impact]
+ The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
+
+ [Fix]
+ Below series of commits from v5.17 fix this issue
+ 1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
+ 17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
+ e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
+
+ [Test]
+ Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
+
+ [Where problems could occcur]
+ The patches only affect ADL-P and up.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: waylan
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Also affects: linux (Ubuntu Jammy)
Importance: High
Status: In Progress
** Also affects: mutter (Ubuntu Jammy)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Committed
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Thanks Timo, this series of patches seems fix this issue
https://www.spinics.net/lists/intel-gfx/msg284609.html
Here is the test kernel, I can't reproduce the issue with this kernel.
https://people.canonical.com/~acelan/bugs/lp1967274/
I'll submit SRU soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Can't reproduce this issue with KDE.
And can't boot up the machine with mainline kernel. So, it's hard to bisect if
it's a kernel issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Confirmed with fresh installed Jammy release(5.15.0-23). After the
screen dim, the backlight power is off,
"/sys/class/backlight/intel_backlight/bl_power", and can't echo 0 to it
to light up.
Switch vt(ctrl+alt+F1) works, and then I can turn off and turn on the backlight
by
echo 4 | sudo tee /sys/class/backlight/intel_backlight/bl_power
echo 0 | sudo tee /sys/class/backlight/intel_backlight/bl_power
Close the lid and then open it, got the same behavior as meta+l, can't
turn on the backlight.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output
** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: New Bug description: For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1821863] Re: Need to add Intel CML related pci-id's
** 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Committed Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1821863] Re: Need to add Intel CML related pci-id's
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Committed Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%
** Changed in: linux (Ubuntu Vivid) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1646537 Title: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in linux source package in Vivid: Won't Fix Status in xorg source package in Vivid: Invalid Status in linux source package in Xenial: Fix Released Status in xorg source package in Xenial: Invalid Bug description: Back-light sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Issue is interment in occurrence. Will be reproducible with the command "sudo pm-suspend" & or close/reopen laptop lid for a period of time days or hours, then go a period of time, days or hours without being able to trigger it again. This is irrespective of running "apt-get update && apt-get upgrade -y" and has continued to be intermittent on last 3 versions of 3.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 1 10:06:43 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06e5] InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 1 09:14:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%
Found another machine and restored the factory image, but still can't reproduce this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1646537 Title: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in xorg source package in Vivid: Invalid Status in linux source package in Xenial: Fix Released Status in xorg source package in Xenial: Invalid Bug description: Back-light sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Issue is interment in occurrence. Will be reproducible with the command "sudo pm-suspend" & or close/reopen laptop lid for a period of time days or hours, then go a period of time, days or hours without being able to trigger it again. This is irrespective of running "apt-get update && apt-get upgrade -y" and has continued to be intermittent on last 3 versions of 3.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 1 10:06:43 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06e5] InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 1 09:14:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%
I got the same machine and restored the system to factory image. After doing some check and write some intel reg value for testing, then I can't reproduce this issue any more, even do a cold boot or restore the image again. BTW, the patched kernel on #4 seems doesn't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1646537 Title: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in xorg source package in Vivid: Invalid Status in linux source package in Xenial: Fix Released Status in xorg source package in Xenial: Invalid Bug description: Back-light sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Issue is interment in occurrence. Will be reproducible with the command "sudo pm-suspend" & or close/reopen laptop lid for a period of time days or hours, then go a period of time, days or hours without being able to trigger it again. This is irrespective of running "apt-get update && apt-get upgrade -y" and has continued to be intermittent on last 3 versions of 3.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 1 10:06:43 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06e5] InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 1 09:14:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%
The 2 i915 patches can't be backported to 3.19 kernel, so I use another way to archive the same function. The test kernel could be found here, I'll try to see if we could find a machine here to verify it. http://people.canonical.com/~acelan/bugs/lp1646537/ ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1646537 Title: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Status in xorg source package in Vivid: Invalid Status in linux source package in Xenial: Fix Released Status in xorg source package in Xenial: Invalid Bug description: Back-light sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Issue is interment in occurrence. Will be reproducible with the command "sudo pm-suspend" & or close/reopen laptop lid for a period of time days or hours, then go a period of time, days or hours without being able to trigger it again. This is irrespective of running "apt-get update && apt-get upgrade -y" and has continued to be intermittent on last 3 versions of 3.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 1 10:06:43 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06e5] InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 1 09:14:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646537/+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 1275416] Re: touchscreen do not work after suspend/resume
For Dell XPS, try remove pinctrl_sunrisepoint driver, it should work. sudo rmmod pinctrl_sunrisepoint There is a discussion and a patch for this issue here https://bugzilla.kernel.org/show_bug.cgi?id=176361 ** Bug watch added: Linux Kernel Bug Tracker #176361 http://bugzilla.kernel.org/show_bug.cgi?id=176361 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1275416 Title: touchscreen do not work after suspend/resume Status in xinput package in Ubuntu: Confirmed Bug description: My laptop (Thinkpad X200T with multi-touch screen) installed the 'Trusty' ubuntu 14.04 (64bits), touchscreen works well after cold boot! But after suspend/resume, touchsreen do not response. Execute 'xsetwacom --list' in terminal, there is nothing, both 'wacom touch' and 'wacom stylus' are gone. I must logout and relogin or reboot, the touchscreen can be normal again. By the way, the same problem happens in the 'Saucy' ubuntu 13.10 (64bits). But in 'Raring' ubuntu 13.04 (64bits), this problem does no exist, touchscreen WORKS WELL after suspend/resume. This Thinkpad X200T updated the newest BIOS, and keep ubuntu OS up to date. Please fix this bug, because 14.04 is a very important version for touchscreen devices, and i think 'suspend/resume' function is important too. Thanks! --- Feb 4, 2014 update Oh I'm sorry, I find a new change for this bug that I never noticed before. I keep Trusty ubuntu up to date(Feb 4, 2014). When the OS's first boot from cold boot, touchscreen works well. Then if suspend/resume for the first time, touchscreen will not response. At this moment, logout and relogin, touchscreen works well again even after suspend/resume. Simply put, touchscreen do not response only after the first suspend/resume since a cold boot. Once the OS logout and relogin, touchscreen will work well after any suspend/resume. The key point is that the OS must logout and relogin for at least one time. Always keep 'Trusty' ubuntu OS updated. that's a strange bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416/+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 1586641] Re: PCI/internal sound card not detected
It's pretty like a hardware issue to me, I'll try to find the hardware to verify it next week. ** Changed in: alsa-driver (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1586641 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: In Progress Bug description: My sound card is not even detected and alsamixer do nothing. I tried oem-audio-hda-daily-lts-xenial-dkms - 0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio- dev/+archive/ubuntu/alsa-daily/+packages like it was described here https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat May 28 15:20:10 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-05-27 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586641/+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 838543] Re: False battery warning +suspend
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/838543 Title: False battery warning +suspend Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Trusty: New Status in linux source package in Trusty: Fix Released Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+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 838543] Re: False battery warning +suspend
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- 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/838543 Title: False battery warning +suspend Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in gnome-settings-daemon source package in Trusty: New Status in linux source package in Trusty: Fix Committed Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+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 838543] Re: False battery warning +suspend
I re-upload the kernel today, it works well for me, so I think it should fix your issue as well. -- 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/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: In Progress Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+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 838543] Re: False battery warning +suspend
** Package changed: unity-settings-daemon (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu) Status: New => In Progress -- 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/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: In Progress Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+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 838543] Re: False battery warning +suspend
Hi all, I encountered this issue, too, and I would like to know if this patch help. You can download the kernel packages from this link, this kernel will retry to get the battery inform after wakeup from S3. Thanks. http://people.canonical.com/~acelan/bugs/lp838543 -- 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/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: New Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+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 838543] Re: False battery warning +suspend
** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: New Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+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 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Attachment added: "usd_optiplex_9030.3.log" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4125215/+files/usd_optiplex_9030.3.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: li
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
It works on Dell OptiPlex 9030 AIO ** Attachment added: "usd_optiplex_9030.2.log" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4125177/+files/usd_optiplex_9030.2.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experiment
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
The latest unity-settings-daemon fix this issue on Dell OptiPlex 9030. The touchscreen works well when connects an external monitor and it still works well after rotate the screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Attachment added: "usd_inspiron_2350.log" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4124570/+files/usd_inspiron_2350.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Attachment added: "usd_optiplex_9030.log" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4124537/+files/usd_optiplex_9030.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Attachment added: "xrandr_optiplex_9030.log" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4122776/+files/xrandr_optiplex_9030.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Here comes the Inspiron 2350 AIO log ** Attachment added: "inspiron-2350.tgz" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4122771/+files/inspiron-2350.tgz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A v
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Tested on Dell Inspiron 20 Model 3048, it works well. ** Attachment added: "inspiron_20_model_3048.tgz" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4122493/+files/inspiron_20_model_3048.tgz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental:
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Attachment added: "xrandr.log" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4121995/+files/xrandr.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Attachment added: "mylog.log" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4121993/+files/mylog.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ub
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Here comes the logs ** Attachment added: "logs_optiplex_9093.tgz" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287341/+attachment/4121989/+files/logs_optiplex_9093.tgz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Hi, I tested it on Dell OptiPlex 9030 AIO with 64-bit Ubuntu 14.04, but it doesn't work. The touchscreen remaps to the whole extended screen. I tried to re-login, reboot the system, and re-plug the hdmi cable, the symptom is the same. ii unity-settings-daemon 14.04.0+14.04.20140414-0ubuntu1.1 amd64daemon handling the Unity session settings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A versio
[Desktop-packages] [Bug 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
** Tags removed: verification-needed-saucy ** Tags added: verification-done-saucy ** Changed in: hwe-next/saucy Status: Confirmed => Fix Committed ** Changed in: hwe-next/trusty Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in HWE Next Project: Fix Released Status in HWE Next saucy series: Fix Committed Status in HWE Next trusty series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “xserver-xorg-input-evdev” package in Ubuntu: Invalid Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
** Patch added: "0001-HID-usbhid-quirk-for-Synaptics-Large-Touchccreen.patch" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+attachment/3856403/+files/0001-HID-usbhid-quirk-for-Synaptics-Large-Touchccreen.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: Fix Committed Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
Those 2 patches had submitted ** Patch added: "0002-HID-usbhid-quirk-for-SiS-Touchscreen.patch" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+attachment/3856404/+files/0002-HID-usbhid-quirk-for-SiS-Touchscreen.patch ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: Fix Committed Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
unix25, Good to know that. I'll build a patch for your device, so that linux kernel can support the SiS touchscreen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: In Progress Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
Hi unix25, thanks a lot. But, looks like your touchscreen chip is not Synaptics, I don't know if the solution apply to SiS' chip. I got a new way to test. # cat /etc/modprobe.d/usbhid.conf options usbhid quirks=0x06cb:0x0af8:0x2000 # sudo update-initramfs -u # sudo reboot Remember to correct the id, ex. options usbhid quirks=0x06cb:0x1d10:0x2000 or options usbhid quirks=0x0457:0x1013:0x2000 The quirk means do no send the init commands which may not supported by Synaptics, #define HID_QUIRK_NO_INIT_REPORTS 0x2000 I need your ack to include the usb id into the quirk, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: In Progress Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
Using wireshark to monitor the usb traffic, we'll find the touchscreen becomes abnormal after systems sends the IDLE command to it. But the touchscreen could revive after sending some other commands, such as GET_DESCRIPTOR. I'll build a test driver soon, but I need to build a list for the affected usb id. On this bug, there are 2 IDs 06cb:1d10 and mine is 06cb:0af8 Please reply if your borken touchscreen ID is not listed above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: In Progress Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Confirmed => In Progress ** Changed in: xserver-xorg-input-evdev (Ubuntu) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: In Progress Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
add the following lines in /etc/rc.local could wake up the touch screen, it
works every time after booting up.
Or, you can run it manually to check if the commands work.
sudo rmmod hid_multitouch ; sudo modprobe hid-multitouch ; find
/sys/bus/usb/devices/2-3 -name control | xargs -I '{}' sudo sh -c "echo on >
'{}'"
sudo rmmod hid_multitouch ; sudo modprobe hid-multitouch ; find
/sys/bus/usb/devices/2-3 -name control | xargs -I '{}' sudo sh -c "echo on >
'{}'"
sudo rmmod hid_multitouch ; sudo modprobe hid-multitouch ; find
/sys/bus/usb/devices/2-3 -name control | xargs -I '{}' sudo sh -c "echo on >
'{}'"
My touchscreen is linked to /sys/bus/usb/devices/2-3, check the
idProduct and idVendor in that directory to make sure which directory
your touchscreen is using.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works after suspend/resume on Lenovo ideapad P400
Touch
Status in “xserver-xorg-input-evdev” package in Ubuntu:
Confirmed
Bug description:
Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All
other devices work.
Touchscreen shows as working and 'states' are correct for any xinput
--list off of a cold boot.
However, if I (at any point) "Suspend" the system, then awaken it, the
Touchscreen immediately functions properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
The above test result is wrong, the touchscreen function is not always working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
It's confirmed that it's a Synaptics firmware bug, and the new firmware can fix it. It works for my device, the usb id is 06CB:0AF8 I'm not sure if it'll work or damage other devices, so use it at your own risk. ** Attachment added: "PR1507220.zip" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+attachment/3835672/+files/PR1507220.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
More finding, if suspend/resume doesn't work for you, try the following steps
cd /sys/devices/pci:00
find -name control | xargs -I '{}' sudo sh -c "echo on > '{}'"
sudo pm-suspend
It will turn on the power for all devices, more precisely you can just turn on
the usb host chip's power
cd /sys/devices/pci:00/:00:14.0
find -name control | xargs -I '{}' sudo sh -c "echo on > '{}'"
sudo pm-suspend
It works for me every time, so it's more like a power management issue
from Synaptics touchscreen firmware.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works after suspend/resume on Lenovo ideapad P400
Touch
Status in “xserver-xorg-input-evdev” package in Ubuntu:
Confirmed
Bug description:
Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All
other devices work.
Touchscreen shows as working and 'states' are correct for any xinput
--list off of a cold boot.
However, if I (at any point) "Suspend" the system, then awaken it, the
Touchscreen immediately functions properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
** Tags added: blocks-hwcert-enablement -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
click top-right systray to open any app's indicator, close lid to enter suspend, re-open it, then the touch screen works. I use this way to enable the touch screen, but have no clue why it behave like that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+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 1175533] Re: [HSW] intel VGA driver i915 doesn't support new haswell graphics [8086:0a2e]
After installed those package from proposed repository, it can enable the chip and run on unity 3D. linux-image-3.5.0-36-generic libgl1-mesa-glx-lts-quantal libglapi-mesa- lts-quantal libgl1-mesa-dri-lts-quantal libdrm2 xserver-xorg-video- intel-lts-quantal -- 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/1175533 Title: [HSW] intel VGA driver i915 doesn't support new haswell graphics [8086:0a2e] Status in HWE Next Project: New Status in The Linux Kernel: Fix Released Status in “libdrm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux-lts-quantal” package in Ubuntu: Fix Committed Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-quantal” package in Ubuntu: Invalid Status in “mesa-lts-raring” package in Ubuntu: New Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu: Invalid Status in “libdrm” source package in Precise: Fix Committed Status in “mesa-lts-quantal” source package in Precise: Fix Committed Status in “xserver-xorg-video-intel-lts-quantal” source package in Precise: New Status in “linux” source package in Quantal: Fix Committed Status in “mesa” source package in Quantal: Fix Committed Status in “xserver-xorg-video-intel” source package in Quantal: Fix Committed Status in “libdrm” source package in Raring: Fix Committed Status in “linux” source package in Raring: Fix Committed Status in “mesa” source package in Raring: Fix Committed Status in “xserver-xorg-video-intel” source package in Raring: Fix Committed Status in “libdrm” source package in Saucy: Fix Released Status in “linux” source package in Saucy: Fix Released Status in “mesa” source package in Saucy: Fix Released Status in “xserver-xorg-video-intel” source package in Saucy: Fix Released Bug description: The PCI ID 8086:0a2e is not in i915 driver so graphics doesn't work on this Haswell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1175533/+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 1197316] Re: GPU hang with Haswell GT3
After installed those package from proposed repository, it can enable the chip and run on unity 3D. linux-image-3.5.0-36-generic libgl1-mesa-glx-lts-quantal libglapi-mesa- lts-quantal libgl1-mesa-dri-lts-quantal libdrm2 xserver-xorg-video- intel-lts-quantal ** Tags removed: verification-needed ** Tags added: verification-done-quantal -- 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/1197316 Title: GPU hang with Haswell GT3 Status in “mesa” package in Ubuntu: Fix Released Status in “mesa-lts-quantal” package in Ubuntu: Invalid Status in “mesa-lts-raring” package in Ubuntu: Invalid Status in “mesa” source package in Precise: Invalid Status in “mesa-lts-quantal” source package in Precise: Fix Committed Status in “mesa-lts-raring” source package in Precise: New Status in “mesa” source package in Quantal: Fix Committed Status in “mesa” source package in Raring: In Progress Bug description: [Impact] renders GT3 haswells unusable [Test Case] use ubuntu with mesa < 9.1.4, notice how it hangs on login, and doesn't with the fixed package [Regression Potential] small, these are limited to GT3, and two commits to make them apply -- The GPU hangs on login if the system has a GT3 version of Intel Haswell. This is fixed in 9.1.4 and by backporting these four commits to 9.0.x: 210f2794f5c4fedc7 i965: Turn brw->urb.vs_size and gs_size into local variables. d4311138e47224ace i965: Use a variable for the push constant size in kB. acff9c2bbf6cf4d9a i965: Update URB partitioning code for Haswell's GT3 variant. ed7fa63bbd375aaf6 i965: Add chipset limits for the Haswell GT3 variant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1197316/+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 1172151] Re: ASUS F75A wi-fi disabled by hardware switch
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172151 Title: ASUS F75A wi-fi disabled by hardware switch Status in GUI Program to install ath9k_htc (Atheros Linux Driver): New Status in Additional Linux Wireless Drivers: New Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: New Status in “linux” package in Ubuntu: Fix Committed Status in “network-manager” package in Ubuntu: New Bug description: Please help me report this bug to the correct project. Today, my Uncle purchased a new Laptop. It is an ASUS F75A, having the following network card: lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) I've installed Ubuntu 13.04 onto this machine, and each time I log in and click on the network-manager indicator, it is in the following state: 1) "Enable Wi-Fi" is NOT check and it is GRAYED OUT. 2) "wi-fi is disabled by hardware switch" The work around I've discovered is not acceptable, because it only resolves the issue for one session: 1) sudo rmmod -f asus_nb_wmi 2) Toggle wi-fi, by holding down the function key and pressing f2 (fn-f2). Note: if don't do step one, the wi-fi only stays enabled for about 4 seconds and then resorts back to the previous state mentioned above. The user (my Uncle), must do this each and everytime he logs into his laptop, in order to consume wi-fi. Also, due to his condition, he's practically incapable of these seemingly simple steps. Note: Before removing Windows 7, Window 7 was able to (appearantly) automatically turn on the hardware switch and connect to the wireless network (recurringly) on each login. However, in Ubuntu, the hardware switch is always OFF after login, and I must rmmod before toggling the hardware switch with fn-f2. Ideally, I'd like this laptop to function like any other laptop I've installed Ubuntu onto. So, how can I acheive that? Also, how can I put this issue in front of the eyes that can prevent this issue for others who purchase an ASUS F75A? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Apr 24 01:48:48 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.7.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.7.0/24 dev wlan0 proto kernel scope link src 192.168.7.36 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 165281c64-6702-4ff0-bc4e-1b1c2c7b3b4a 802-3-ethernet1366784897 Wed 24 Apr 2013 01:28:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 Video Surveillance7f736f06-a4e9-4340-a9cf-b293812ca247 802-11-wireless 1366786097 Wed 24 Apr 2013 01:48:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 2073 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 4
[Desktop-packages] [Bug 1172151] Re: ASUS F75A wi-fi disabled by hardware switch
Cool, good to hear the dkms works for you. And the fix is too late to enter the 13.04 release. Anyway, I'll submit the fix to mainstream kernel, so that the next ubuntu release will have the fix. Thanks for your report and test. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172151 Title: ASUS F75A wi-fi disabled by hardware switch Status in GUI Program to install ath9k_htc (Atheros Linux Driver): New Status in Additional Linux Wireless Drivers: New Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: New Status in “linux” package in Ubuntu: In Progress Status in “network-manager” package in Ubuntu: New Bug description: Please help me report this bug to the correct project. Today, my Uncle purchased a new Laptop. It is an ASUS F75A, having the following network card: lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) I've installed Ubuntu 13.04 onto this machine, and each time I log in and click on the network-manager indicator, it is in the following state: 1) "Enable Wi-Fi" is NOT check and it is GRAYED OUT. 2) "wi-fi is disabled by hardware switch" The work around I've discovered is not acceptable, because it only resolves the issue for one session: 1) sudo rmmod -f asus_nb_wmi 2) Toggle wi-fi, by holding down the function key and pressing f2 (fn-f2). Note: if don't do step one, the wi-fi only stays enabled for about 4 seconds and then resorts back to the previous state mentioned above. The user (my Uncle), must do this each and everytime he logs into his laptop, in order to consume wi-fi. Also, due to his condition, he's practically incapable of these seemingly simple steps. Note: Before removing Windows 7, Window 7 was able to (appearantly) automatically turn on the hardware switch and connect to the wireless network (recurringly) on each login. However, in Ubuntu, the hardware switch is always OFF after login, and I must rmmod before toggling the hardware switch with fn-f2. Ideally, I'd like this laptop to function like any other laptop I've installed Ubuntu onto. So, how can I acheive that? Also, how can I put this issue in front of the eyes that can prevent this issue for others who purchase an ASUS F75A? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Apr 24 01:48:48 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.7.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.7.0/24 dev wlan0 proto kernel scope link src 192.168.7.36 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 165281c64-6702-4ff0-bc4e-1b1c2c7b3b4a 802-3-ethernet1366784897 Wed 24 Apr 2013 01:28:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 Video Surveillance7f736f06-a4e9-4340-a9cf-b293812ca247 802-11-wireless 1366786097 Wed 24 Apr 2013 01:48:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wal
[Desktop-packages] [Bug 1172151] Re: ASUS F75A wi-fi disabled by hardware switch
Correct. BTW, blacklist asus-nb-wmi will make hotkeys stop working, such as brightness adjustment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172151 Title: ASUS F75A wi-fi disabled by hardware switch Status in GUI Program to install ath9k_htc (Atheros Linux Driver): New Status in Additional Linux Wireless Drivers: New Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: New Status in “linux” package in Ubuntu: In Progress Status in “network-manager” package in Ubuntu: New Bug description: Please help me report this bug to the correct project. Today, my Uncle purchased a new Laptop. It is an ASUS F75A, having the following network card: lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) I've installed Ubuntu 13.04 onto this machine, and each time I log in and click on the network-manager indicator, it is in the following state: 1) "Enable Wi-Fi" is NOT check and it is GRAYED OUT. 2) "wi-fi is disabled by hardware switch" The work around I've discovered is not acceptable, because it only resolves the issue for one session: 1) sudo rmmod -f asus_nb_wmi 2) Toggle wi-fi, by holding down the function key and pressing f2 (fn-f2). Note: if don't do step one, the wi-fi only stays enabled for about 4 seconds and then resorts back to the previous state mentioned above. The user (my Uncle), must do this each and everytime he logs into his laptop, in order to consume wi-fi. Also, due to his condition, he's practically incapable of these seemingly simple steps. Note: Before removing Windows 7, Window 7 was able to (appearantly) automatically turn on the hardware switch and connect to the wireless network (recurringly) on each login. However, in Ubuntu, the hardware switch is always OFF after login, and I must rmmod before toggling the hardware switch with fn-f2. Ideally, I'd like this laptop to function like any other laptop I've installed Ubuntu onto. So, how can I acheive that? Also, how can I put this issue in front of the eyes that can prevent this issue for others who purchase an ASUS F75A? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Apr 24 01:48:48 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.7.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.7.0/24 dev wlan0 proto kernel scope link src 192.168.7.36 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 165281c64-6702-4ff0-bc4e-1b1c2c7b3b4a 802-3-ethernet1366784897 Wed 24 Apr 2013 01:28:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 Video Surveillance7f736f06-a4e9-4340-a9cf-b293812ca247 802-11-wireless 1366786097 Wed 24 Apr 2013 01:48:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 2073 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS
[Desktop-packages] [Bug 1172151] Re: ASUS F75A wi-fi disabled by hardware switch
For the unknown reason, the dkms package I built may not be able to install, so I attached the source code here as well. Following commands to use it 1. tar -zxvf asus-wmi-1.0.tgz 2. sudo cp -a asus-wmi-1.0 /usr/src 3. sudo apt-get install dkms 4. sudo dkms add -m asus-wmi -v 1.0 5. sudo dkms install -m asus-wmi -v 1.0 6. reboot Then, you will get a system just like installing the dkms package ** Attachment added: "asus-wmi-1.0.tgz" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1172151/+attachment/3652817/+files/asus-wmi-1.0.tgz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172151 Title: ASUS F75A wi-fi disabled by hardware switch Status in GUI Program to install ath9k_htc (Atheros Linux Driver): New Status in Additional Linux Wireless Drivers: New Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: New Status in “linux” package in Ubuntu: In Progress Status in “network-manager” package in Ubuntu: New Bug description: Please help me report this bug to the correct project. Today, my Uncle purchased a new Laptop. It is an ASUS F75A, having the following network card: lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) I've installed Ubuntu 13.04 onto this machine, and each time I log in and click on the network-manager indicator, it is in the following state: 1) "Enable Wi-Fi" is NOT check and it is GRAYED OUT. 2) "wi-fi is disabled by hardware switch" The work around I've discovered is not acceptable, because it only resolves the issue for one session: 1) sudo rmmod -f asus_nb_wmi 2) Toggle wi-fi, by holding down the function key and pressing f2 (fn-f2). Note: if don't do step one, the wi-fi only stays enabled for about 4 seconds and then resorts back to the previous state mentioned above. The user (my Uncle), must do this each and everytime he logs into his laptop, in order to consume wi-fi. Also, due to his condition, he's practically incapable of these seemingly simple steps. Note: Before removing Windows 7, Window 7 was able to (appearantly) automatically turn on the hardware switch and connect to the wireless network (recurringly) on each login. However, in Ubuntu, the hardware switch is always OFF after login, and I must rmmod before toggling the hardware switch with fn-f2. Ideally, I'd like this laptop to function like any other laptop I've installed Ubuntu onto. So, how can I acheive that? Also, how can I put this issue in front of the eyes that can prevent this issue for others who purchase an ASUS F75A? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Apr 24 01:48:48 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.7.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.7.0/24 dev wlan0 proto kernel scope link src 192.168.7.36 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 165281c64-6702-4ff0-bc4e-1b1c2c7b3b4a 802-3-ethernet1366784897 Wed 24 Apr 2013 01:28:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 Video Surveillance7f736f06-a4e9-4340-a9cf-b293812ca247 802-11-wireless 1366786097 Wed 24 Apr 2013 01:48:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE
[Desktop-packages] [Bug 1172151] Re: ASUS F75A wi-fi disabled by hardware switch
Hi, I just built a asus-wmi dkms package, I think it should work for you. Try installing it and reboot the system to see if it works. sudo dpkg -i asus-wmi-dkms_1.0_all.deb If not, I need some other logs hope you can attach them to me. 1. the result of "rfkill list" command, and then press the wifi hotkey and do "rfkill list" agagin, I need the 2 logs. 2. cat /sys/module/asus_nb_wmi/parameters/wapf if you got the value is "0", then try the following commands to see if it make the wifi hotkey works 2.1 sudo rmmod asus-nb-wmi asus-wmi 2.2 sudo modprobe asus-wmi 2.3 sudo modprobe asus-nb-wmi wapf=4 2.4 try pressing the wifi hotkey and log the result of "rfkill list" to see if the hard block and soft block synchronized. BTW, since you have the wifi issue, I'm wondering if the hotkeys to the turn off the screen and the display toggle are working. I can fix them if you have problems. ** Attachment added: "asus-wmi-dkms_1.0_all.deb" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1172151/+attachment/3652816/+files/asus-wmi-dkms_1.0_all.deb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172151 Title: ASUS F75A wi-fi disabled by hardware switch Status in GUI Program to install ath9k_htc (Atheros Linux Driver): New Status in Additional Linux Wireless Drivers: New Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: New Status in “linux” package in Ubuntu: In Progress Status in “network-manager” package in Ubuntu: New Bug description: Please help me report this bug to the correct project. Today, my Uncle purchased a new Laptop. It is an ASUS F75A, having the following network card: lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) I've installed Ubuntu 13.04 onto this machine, and each time I log in and click on the network-manager indicator, it is in the following state: 1) "Enable Wi-Fi" is NOT check and it is GRAYED OUT. 2) "wi-fi is disabled by hardware switch" The work around I've discovered is not acceptable, because it only resolves the issue for one session: 1) sudo rmmod -f asus_nb_wmi 2) Toggle wi-fi, by holding down the function key and pressing f2 (fn-f2). Note: if don't do step one, the wi-fi only stays enabled for about 4 seconds and then resorts back to the previous state mentioned above. The user (my Uncle), must do this each and everytime he logs into his laptop, in order to consume wi-fi. Also, due to his condition, he's practically incapable of these seemingly simple steps. Note: Before removing Windows 7, Window 7 was able to (appearantly) automatically turn on the hardware switch and connect to the wireless network (recurringly) on each login. However, in Ubuntu, the hardware switch is always OFF after login, and I must rmmod before toggling the hardware switch with fn-f2. Ideally, I'd like this laptop to function like any other laptop I've installed Ubuntu onto. So, how can I acheive that? Also, how can I put this issue in front of the eyes that can prevent this issue for others who purchase an ASUS F75A? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Apr 24 01:48:48 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.7.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.7.0/24 dev wlan0 proto kernel scope link src 192.168.7.36 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 165281c64-6702-4ff0-bc4e-1b1c2c7b3b4a 802-3-ethernet1366784897 Wed 24 Apr 2013 01:28:17 AM CDTyes no /org/fr
[Desktop-packages] [Bug 1172151] Re: ASUS F75A wi-fi disabled by hardware switch
** Changed in: linux (Ubuntu) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172151 Title: ASUS F75A wi-fi disabled by hardware switch Status in GUI Program to install ath9k_htc (Atheros Linux Driver): New Status in Additional Linux Wireless Drivers: New Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: New Status in “linux” package in Ubuntu: In Progress Status in “network-manager” package in Ubuntu: New Bug description: Please help me report this bug to the correct project. Today, my Uncle purchased a new Laptop. It is an ASUS F75A, having the following network card: lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01) I've installed Ubuntu 13.04 onto this machine, and each time I log in and click on the network-manager indicator, it is in the following state: 1) "Enable Wi-Fi" is NOT check and it is GRAYED OUT. 2) "wi-fi is disabled by hardware switch" The work around I've discovered is not acceptable, because it only resolves the issue for one session: 1) sudo rmmod -f asus_nb_wmi 2) Toggle wi-fi, by holding down the function key and pressing f2 (fn-f2). Note: if don't do step one, the wi-fi only stays enabled for about 4 seconds and then resorts back to the previous state mentioned above. The user (my Uncle), must do this each and everytime he logs into his laptop, in order to consume wi-fi. Also, due to his condition, he's practically incapable of these seemingly simple steps. Note: Before removing Windows 7, Window 7 was able to (appearantly) automatically turn on the hardware switch and connect to the wireless network (recurringly) on each login. However, in Ubuntu, the hardware switch is always OFF after login, and I must rmmod before toggling the hardware switch with fn-f2. Ideally, I'd like this laptop to function like any other laptop I've installed Ubuntu onto. So, how can I acheive that? Also, how can I put this issue in front of the eyes that can prevent this issue for others who purchase an ASUS F75A? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Apr 24 01:48:48 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-24 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) IpRoute: default via 192.168.7.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.7.0/24 dev wlan0 proto kernel scope link src 192.168.7.36 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 165281c64-6702-4ff0-bc4e-1b1c2c7b3b4a 802-3-ethernet1366784897 Wed 24 Apr 2013 01:28:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 Video Surveillance7f736f06-a4e9-4340-a9cf-b293812ca247 802-11-wireless 1366786097 Wed 24 Apr 2013 01:48:17 AM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter
[Desktop-packages] [Bug 1037763] Re: [Asus X101CH, Internal speaker] No sound after update (Ubuntu preinstall)
Just try to dig in the root cause and explain the difference between alsa-hda-realtek-patched-dkms v1.0 and v1.1. Looks like the new kernel changes some code in snd-hda, so that makes the kernel module produced by the dkms package becomes doesn't match with other snd-hda modules come with kernel package. So, in dkms.conf file, it copy more kernel modules to the system to overwrite those come with kernel package. % diff -Nru alsa-hda-realtek-patched-1.0/Makefile alsa-hda-realtek-patched-1.1/Makefile --- alsa-hda-realtek-patched-1.0/Makefile 2012-08-31 16:09:03.0 +0800 +++ alsa-hda-realtek-patched-1.1/Makefile 2012-09-03 09:33:16.373771214 +0800 @@ -72,3 +72,5 @@ all: make -C $(KERNELBUILD) M=$(shell pwd) modules +clean: + rm -rf *.o *.cmd *.ko *.mod.c modules.order Module.symvers % diff -Nru alsa-hda-realtek-patched-1.0/dkms.conf alsa-hda-realtek-patched-1.1/dkms.conf --- alsa-hda-realtek-patched-1.0/dkms.conf 2012-06-06 11:43:07.0 +0800 +++ alsa-hda-realtek-patched-1.1/dkms.conf 2012-09-03 09:33:15.269771484 +0800 @@ -1,4 +1,4 @@ -PACKAGE_VERSION="1.0" +PACKAGE_VERSION="1.1" PACKAGE_NAME="alsa_hda_realtek_patched" AUTOINSTALL="yes" REMAKE_INITRD="yes" @@ -6,3 +6,12 @@ BUILT_MODULE_NAME[0]="snd-hda-codec-realtek" DEST_MODULE_LOCATION[0]="/updates/kernel" +BUILT_MODULE_NAME[1]="snd-hda-codec" +DEST_MODULE_LOCATION[1]="/updates/kernel" + +BUILT_MODULE_NAME[2]="snd-hda-codec-hdmi" +DEST_MODULE_LOCATION[2]="/updates/kernel" + +BUILT_MODULE_NAME[3]="snd-hda-intel" +DEST_MODULE_LOCATION[3]="/updates/kernel" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1037763 Title: [Asus X101CH, Internal speaker] No sound after update (Ubuntu preinstall) Status in “alsa-driver” package in Ubuntu: Fix Released Bug description: This is a new Asus EeePc with Ubuntu preinstalled. The sound works out of the box, but after an initial update the internal speakers stop working. Audio via the headphone jack still works. A factory reset of the system (which reinstalls Ubuntu from a recovery partition) restores the sound but the next update (of Linux kernel) breaks it again. Current workaround: Installing the latest DKMS package according to https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS should bring the sound back. I ran "ubuntu-bug audio" according to these instructions (https://wiki.ubuntu.com/DebuggingSoundProblems) to file this bug. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tgraham1749 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdff0 irq 46' Mixer name : 'Intel CedarTrail HDMI' Components : 'HDA:10ec0269,10438516,00100100 HDA:80862880,80860101,0010' Controls : 10 Simple ctrls : 4 Date: Thu Aug 16 21:34:37 2012 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-yanshui-precise-i386-20120615-0 InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.2.0-25-generic-pae.old-dkms' LIVE Binary 20120615-03:22 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: 1749 tgraham F pulseaudio PID ACCESS COMMAND Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X101CH, Realtek ID 269, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X101CH.1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X101CH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: x.xx dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX101CH.1101:bd05/30/2012:svnASUSTeKCOMPUTERINC.:pnX101CH:pvrx.x:rvnASUSTeKCOMPUTERINC.:rnX101CH:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x: dmi.produ
[Desktop-packages] [Bug 873495] Re: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed
Great, I just cherry-picked some patches and built a new kernel Could you guys try to see if those patches fix the issue? Thanks http://people.canonical.com/~acelan/bugs/lp873495/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/873495 Title: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed Status in Light Display Manager: New Status in NVIDIA Drivers Ubuntu: New Status in “lightdm” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX 485M, GTX 560M or GTX 580M. Appears to be a race condition. LightDM attempts to start before /dev/nvidiactrl is created. As a workaround add "sleep 1 && service lightdm start" to /etc/rc.local to start the service. ### This workaround is insufficient. Some users have reported that their systems do not start after initial user setup. Deleting the contents of /var/run/dbus/* resolves the issue in these cases. ### ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell] CompositorRunning: compiz Date: Thu Oct 13 11:05:18 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5102] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: System76, Inc. Serval Professional ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 01/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+subscript
[Desktop-packages] [Bug 873495] Re: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed
Hi, I'm wondering if this issue still happened while using Precise(12.04) kernel. >From what I heard, this issue might result from that kernel didn't send out >the drm ready event. So, it's possible that this issue is fixed by the newer kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/873495 Title: LightDM fails to start when installed in OEM mode after nvidia-current or nvidia-current-updates are installed Status in Light Display Manager: New Status in NVIDIA Drivers Ubuntu: New Status in “lightdm” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX 485M, GTX 560M or GTX 580M. Appears to be a race condition. LightDM attempts to start before /dev/nvidiactrl is created. As a workaround add "sleep 1 && service lightdm start" to /etc/rc.local to start the service. ### This workaround is insufficient. Some users have reported that their systems do not start after initial user setup. Deleting the contents of /var/run/dbus/* resolves the issue in these cases. ### ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell] CompositorRunning: compiz Date: Thu Oct 13 11:05:18 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5102] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: System76, Inc. Serval Professional ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 01/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bu
[Desktop-packages] [Bug 914348] Re: Touchpad LED on Dell's laptop is not working
I submitted the 2 patches mentioned in #6 to stable kernel, so they will go into precise kernel at next merge. -- 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/914348 Title: Touchpad LED on Dell's laptop is not working Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: In some of Dell laptops, they support a touchpad LED to indicate the enablement/disablement of the touchpad. And kernel(after 3.2) supports an interface to turn on/off the LED, user space app should take the responsibility to handle this, and I think gnome-settings-daemon is the best one. The interface is in /sys To turn on the LED echo 1 > /sys/class/leds/dell-laptop::touchpad/brightness To turn it off echo 0 > /sys/class/leds/dell-laptop::touchpad/brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/914348/+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 914348] Re: Touchpad LED on Dell's laptop is not working
Hi, In Precise kernel, it already provided an interface to turn on/off the tourchpad LED /sys/class/leds/dell-laptop::touchpad/brightness Other patches are just quirks to add more machines to have this interface, so I don't think it's so urgent. The problem is that there is no userspace app to take care of this interface, and to turn on/off the LED while touchpad toggle events happened. It's not suitable to let driver handle this, for it can't access the led subsystem while receiving the key events. -- 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/914348 Title: Touchpad LED on Dell's laptop is not working Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: In some of Dell laptops, they support a touchpad LED to indicate the enablement/disablement of the touchpad. And kernel(after 3.2) supports an interface to turn on/off the LED, user space app should take the responsibility to handle this, and I think gnome-settings-daemon is the best one. The interface is in /sys To turn on the LED echo 1 > /sys/class/leds/dell-laptop::touchpad/brightness To turn it off echo 0 > /sys/class/leds/dell-laptop::touchpad/brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/914348/+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 914348] Re: Touchpad LED on Dell's laptop is not working
Yes, I'll submit SRU to the kernel team to cherry pick those patches. But, we still don't have a good way in userspace to cooperate with the kernel driver. It just comes to my mind, maybe ubuntu kernel team will accept the way turning on/off touchpad LED in the driver until we have a better way doing this in userspace app. I'll try it. -- 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/914348 Title: Touchpad LED on Dell's laptop is not working Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: In some of Dell laptops, they support a touchpad LED to indicate the enablement/disablement of the touchpad. And kernel(after 3.2) supports an interface to turn on/off the LED, user space app should take the responsibility to handle this, and I think gnome-settings-daemon is the best one. The interface is in /sys To turn on the LED echo 1 > /sys/class/leds/dell-laptop::touchpad/brightness To turn it off echo 0 > /sys/class/leds/dell-laptop::touchpad/brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/914348/+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 959106] Re: brightness changing problem in ASUS machines
I also filed a bug on upstream. https://bugzilla.gnome.org/show_bug.cgi?id=672380 -- 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/959106 Title: brightness changing problem in ASUS machines Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: For all ASUS machines, it will only notify the userspace app by udev event while the brightness value is changed, instead of keyevent. The procedure in the asus-wmi kernel module is as described below 1. receive the keyevent from WMI 2. if the brightness event is not handled by ACPI, then update the brightness value through WMI 3. call backlight_force_update(), it will 1. send a change notification on the actual_brightness file (userspace can monitor it using inotify or related), and 2. send a uevent which can be catched by udev or others (with SOURCE being an env variable containing the source of this change) The problem is that it won't report keyevent, so g-s-d won't show the brightness OSD. But it actually reports the event, uevent. It won't harm to monitor the uevent and read the brightness value from actual_brightness and shows the OSD, even if there is already a keyevent reported. Please consider to add this feature, thanks. The brightness uevent looks like this == KERNEL[16407.000334] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.000555] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.000605] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.000730] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.000997] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.001164] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.002040] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.002212] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/959106/+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 959106] [NEW] brightness changing problem in ASUS machines
Public bug reported: For all ASUS machines, it will only notify the userspace app by udev event while the brightness value is changed, instead of keyevent. The procedure in the asus-wmi kernel module is as described below 1. receive the keyevent from WMI 2. if the brightness event is not handled by ACPI, then update the brightness value through WMI 3. call backlight_force_update(), it will 1. send a change notification on the actual_brightness file (userspace can monitor it using inotify or related), and 2. send a uevent which can be catched by udev or others (with SOURCE being an env variable containing the source of this change) The problem is that it won't report keyevent, so g-s-d won't show the brightness OSD. But it actually reports the event, uevent. It won't harm to monitor the uevent and read the brightness value from actual_brightness and shows the OSD, even if there is already a keyevent reported. Please consider to add this feature, thanks. The brightness uevent looks like this == KERNEL[16407.000334] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.000555] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.000605] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.000730] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.000997] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.001164] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.002040] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.002212] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) == ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #672380 https://bugzilla.gnome.org/show_bug.cgi?id=672380 -- 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/959106 Title: brightness changing problem in ASUS machines Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: For all ASUS machines, it will only notify the userspace app by udev event while the brightness value is changed, instead of keyevent. The procedure in the asus-wmi kernel module is as described below 1. receive the keyevent from WMI 2. if the brightness event is not handled by ACPI, then update the brightness value through WMI 3. call backlight_force_update(), it will 1. send a change notification on the actual_brightness file (userspace can monitor it using inotify or related), and 2. send a uevent which can be catched by udev or others (with SOURCE being an env variable containing the source of this change) The problem is that it won't report keyevent, so g-s-d won't show the brightness OSD. But it actually reports the event, uevent. It won't harm to monitor the uevent and read the brightness value from actual_brightness and shows the OSD, even if there is already a keyevent reported. Please consider to add this feature, thanks. The brightness uevent looks like this == KERNEL[16407.000334] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.000555] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.000605] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.000730] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.000997] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.001164] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) KERNEL[16407.002040] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) UDEV [16407.002212] change /devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight) == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/959106/+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 914348] Re: Touchpad LED on Dell's laptop is not working
I fixed the problem to persist the LED status after S3 in the driver, but I still have no idea how to let user space application access the sysfs without root privilege. And I don't think it's suitable to change the file mode to 0666, for I can't find any file with that mode in sysfs. -- 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/914348 Title: Touchpad LED on Dell's laptop is not working Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: In some of Dell laptops, they support a touchpad LED to indicate the enablement/disablement of the touchpad. And kernel(after 3.2) supports an interface to turn on/off the LED, user space app should take the responsibility to handle this, and I think gnome-settings-daemon is the best one. The interface is in /sys To turn on the LED echo 1 > /sys/class/leds/dell-laptop::touchpad/brightness To turn it off echo 0 > /sys/class/leds/dell-laptop::touchpad/brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/914348/+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 914348] Re: Touchpad LED on Dell's laptop is not working
Hi, I'm trying to build a patch for this issue, but I encountered some problems. 1. The permission of the file in sysfs is 0644, so gsd(gnome-settings-daemon) should have root privilege to access the file. -rw-r--r-- 1 root root 4096 Jan 13 17:04 /sys/class/leds/dell-laptop::touchpad/brightness But the gsd run as a normal user privilege, so it don't have the permission to control the touchpad LED. I'm wondering how user space application deals with this kind of issue. 2. After system recovered from S3, the touchpad LED won't turn on again. Is there any way that gsd can know the system recovered from S3 and reset the LED status? I can discuss with the driver maintainer if there is no way to know that. -- 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/914348 Title: Touchpad LED on Dell's laptop is not working Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: In some of Dell laptops, they support a touchpad LED to indicate the enablement/disablement of the touchpad. And kernel(after 3.2) supports an interface to turn on/off the LED, user space app should take the responsibility to handle this, and I think gnome-settings-daemon is the best one. The interface is in /sys To turn on the LED echo 1 > /sys/class/leds/dell-laptop::touchpad/brightness To turn it off echo 0 > /sys/class/leds/dell-laptop::touchpad/brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/914348/+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 914348] [NEW] Touchpad LED on Dell's laptop is not working
Public bug reported: In some of Dell laptops, they support a touchpad LED to indicate the enablement/disablement of the touchpad. And kernel(after 3.2) supports an interface to turn on/off the LED, user space app should take the responsibility to handle this, and I think gnome-settings-daemon is the best one. The interface is in /sys To turn on the LED echo 1 > /sys/class/leds/dell-laptop::touchpad/brightness To turn it off echo 0 > /sys/class/leds/dell-laptop::touchpad/brightness ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/914348 Title: Touchpad LED on Dell's laptop is not working Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: In some of Dell laptops, they support a touchpad LED to indicate the enablement/disablement of the touchpad. And kernel(after 3.2) supports an interface to turn on/off the LED, user space app should take the responsibility to handle this, and I think gnome-settings-daemon is the best one. The interface is in /sys To turn on the LED echo 1 > /sys/class/leds/dell-laptop::touchpad/brightness To turn it off echo 0 > /sys/class/leds/dell-laptop::touchpad/brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/914348/+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
