[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
It's worth mentioning that even with the downgraded bios the mouse cursor frequently gets stuck requiring a screen flex to fix. In addition the downgraded bios exposes similar sticking on Windows. So I can only imagine that resolving this was the purpose of the bios update in the first place. Once updated to the latest bios cursor behaviour is good on Windows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826844] Re: nvidia-drivers-* are not on the ISO
Have confirmed with Nvidia via sverdy. We are clear to distribute the drivers on the ISO. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826844] Re: nvidia-drivers-* are not on the ISO
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Will Cooke (willcooke) ** Tags removed: rls-ee-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1826844 Title: nvidia-drivers-* are not on the ISO Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: On Ubuntu desktop, without a network connection, the user can select to install 3rd party drivers (which states that it'll install graphics driver) but even if he selects this option, nVidia proprietary drivers won't be installed because they are not on the pool of the ISO. also tracked in the desktop trello board as card: https://trello.com/c/rPiwDpPe/130-bug1826844-nvidia-drivers-are-not-on-the-iso ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:22:44 2019 InstallationDate: Installed on 2014-07-15 (1749 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to eoan on 2018-03-24 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1826844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations
** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Tags removed: rls-ee-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801383 Title: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations Status in apport package in Ubuntu: New Status in firefox package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: New Bug description: When I apport-bug certain packages such as firefox for example, it uploads the WifiSyslog.txt file. The WifiSyslog may contain a list of all system connections enumerated in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has ever connected to that are found in the system-connections. This is a serious privacy risk and completely unnecessary information for most bug reports. Should either remove WifiSyslog as a requirement for packages that don't need it (should I report this to https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact information that may contain usernames and SSIDs from the log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 -0400:2018-11-01 19:17:30.982295751 -0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 11:24:20 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (50 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824103] Re: aplay record file failed always.
Is there a step missing in the reproducer steps? On a new 19.04 install on a random Dell Inspiron arecord fails with: ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave arecord: main:828: audio open error: No such file or directory -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824103 Title: aplay record file failed always. Status in linux package in Ubuntu: Incomplete Bug description: Test machine: ThinkPad X1 Carbon Image: Ubuntu Disco 19.04 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N23ET55W (1.30 ) Steps: 1. Install image 19.04 2. Login as default user 3. Open a terminal and type "$ arecord abc.wav" 4. Say something and let laptop recorded your words 5. Cancel the record, please press 'Ctrl + C' 6. Please type "$ aplay abc.wav" in terminal Expected result: The voice played smoothly. Actual result: Step 3, u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ^CAborted by signal Interrupt... arecord: pcm_read:2145: read error: Interrupted system call Step 6, u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824211] Re: Ubiquity in 18.04.2 does not install nvidia driver when requested to do so
This is probably a packaging problem on the nvidia drivers rather than a bug in Ubiquiuty. Moving there for more ideas. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubiquity (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1824211 Title: Ubiquity in 18.04.2 does not install nvidia driver when requested to do so Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Installed 18.04.2 on a laptop with nvidia GTX 960. I enabled wireless network and ticked the box to install 3rd party proprietary stuff. Rebooted to the installed system and found no nvidia driver installed. Found this in the installer/syslog (full syslog attached) Apr 10 16:44:54 ubuntu ubiquity: The following packages have unmet dependencies: Apr 10 16:44:54 ubuntu ubiquity: nvidia-driver-390 : Depends: xserver-xorg-video-nvidia-390 (= 390.77-0ubuntu0.18.04.1) but it is not going to be installed Apr 10 16:44:54 ubuntu ubiquity: Recommends: libnvidia-compute-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable Apr 10 16:44:54 ubuntu ubiquity: Recommends: libnvidia-decode-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable Apr 10 16:44:54 ubuntu ubiquity: Recommends: libnvidia-encode-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable Apr 10 16:44:54 ubuntu ubiquity: Recommends: libnvidia-ifr1-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable Apr 10 16:44:54 ubuntu ubiquity: Recommends: libnvidia-fbc1-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable Apr 10 16:44:54 ubuntu ubiquity: Recommends: libnvidia-gl-390:i386 (= 390.77-0ubuntu0.18.04.1) but it is not installable Apr 10 16:44:54 ubuntu ubiquity: E Apr 10 16:44:54 ubuntu ubiquity: : Unable to correct problems, you have held broken packages. Apr 10 16:44:54 ubuntu ubiquity: ubuntu-drivers autoinstall failed with code: 100 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 18:01:03 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- keyboard-configuration/layoutcode=gb InstallationDate: Installed on 2019-04-10 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1824211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Added to Trello: https://trello.com/c/4fDA1uYR/291-bug1773897 -regression-logitech-m337-mice-are-automatically-disconnected-after- connected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: Confirmed Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam
Updated tags for Liam. Thanks for testing. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: ===SRU Justification=== [Impact] New steam-hid driver breaks Unity games. [Fix] Quote from the commit message: "With this commit, when a HID client starts, the input device is removed; when the HID client ends the input device is recreated." [Test] A guy from Valve comfirms the backport works. [Regression Potential] Low. This fix is specific to hid-steam, which is a new driver introduced in v4.18. ===Original Bug Report=== The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam
As I understand it, while this currently works on Bionic with 4.15 it will _stop_ working on Bionic when the new 4.18 HWE kernel gets released, without this patch applied. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ===SRU Justification=== [Impact] New steam-hid driver breaks Unity games. [Fix] Quote from the commit message: "With this commit, when a HID client starts, the input device is removed; when the HID client ends the input device is recreated." [Test] A guy from Valve comfirms the backport works. [Regression Potential] Low. This fix is specific to hid-steam, which is a new driver introduced in v4.18. ===Original Bug Report=== The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam
I would like to see this prepared for Bionic too. While a lot of gamers go for the latest release, the LTS has a massive user base. I'd like to see Steam controllers working in Bionic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: ===SRU Justification=== [Impact] New steam-hid driver breaks Unity games. [Fix] Quote from the commit message: "With this commit, when a HID client starts, the input device is removed; when the HID client ends the input device is recreated." [Test] A guy from Valve comfirms the backport works. [Regression Potential] Low. This fix is specific to hid-steam, which is a new driver introduced in v4.18. ===Original Bug Report=== The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806247] Re: hid-steam in linux 4.18 causes trouble with steam games
*** This bug is a duplicate of bug 1798583 *** https://bugs.launchpad.net/bugs/1798583 Kernel available here for testing: https://people.canonical.com/~khfeng/lp1806247/ I'm going to mark this as a duplicate of LP: #1798583 and suggest that we continue discussion over there. ** This bug has been marked a duplicate of bug 1798583 the new Steam Controller driver breaks it on Steam -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806247 Title: hid-steam in linux 4.18 causes trouble with steam games Status in linux package in Ubuntu: Confirmed Bug description: Good day, Reported on Valve's issue tracker [1] and upstream [2]. There is a functional regression with the introduction of the hid-steam kernel module and using the Steam Controller with some Steam games. In the bug reports there is a proposed fix which has been accepted upstream [3] and backported to 4.19 [4]. Unfortunately, 4.18 was EOL'd before this patch could land, and is expected to affect both Ubuntu 18.10's kernel and the upcoming 18.04.2 hwe kernel. Please consider applying this patch [3] to your 4.18 builds. Best regards, kisak [1] https://github.com/ValveSoftware/steam-for-linux/issues/5645 [2] https://bugzilla.kernel.org/show_bug.cgi?id=201571 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=385a4886778f6d6e61eff1d4d295af332d7130e1 [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=fb87a92b43961c89bf4a115d8a700885d8959cb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806247] Re: hid-steam in linux 4.18 causes trouble with steam games
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806247 Title: hid-steam in linux 4.18 causes trouble with steam games Status in linux package in Ubuntu: Confirmed Bug description: Good day, Reported on Valve's issue tracker [1] and upstream [2]. There is a functional regression with the introduction of the hid-steam kernel module and using the Steam Controller with some Steam games. In the bug reports there is a proposed fix which has been accepted upstream [3] and backported to 4.19 [4]. Unfortunately, 4.18 was EOL'd before this patch could land, and is expected to affect both Ubuntu 18.10's kernel and the upcoming 18.04.2 hwe kernel. Please consider applying this patch [3] to your 4.18 builds. Best regards, kisak [1] https://github.com/ValveSoftware/steam-for-linux/issues/5645 [2] https://bugzilla.kernel.org/show_bug.cgi?id=201571 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=385a4886778f6d6e61eff1d4d295af332d7130e1 [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=fb87a92b43961c89bf4a115d8a700885d8959cb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam
Kernel team are addressing this in bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806247 This might be able to be marked as a dupe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
Not a release blocker. Seb will look to SRU. ** Tags removed: rls-cc-incoming ** Tags added: rls-cc-notfixing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Triaged Bug description: https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) 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/1796550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
Could be related to this: https://gitlab.gnome.org/GNOME/gdm/merge_requests/37 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Won't Fix Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Fix Released Status in gdm3 source package in Cosmic: Won't Fix Status in kmod source package in Cosmic: Invalid Status in linux source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Confirmed Status in xserver-xorg-video-fbdev source package in Cosmic: Fix Released Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty When this issue happens there is a plymouth crash reported in bug 1794292 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705466] Re: Kernel oopsed when booting
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705466 Title: Kernel oopsed when booting Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Invalid Bug description: Spoke to Leann and she suggested that I log this. Artful running proposed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1870 F pulseaudio CurrentDesktop: GNOME Date: Thu Jul 20 13:14:48 2017 InstallationDate: Installed on 2017-07-10 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709) MachineType: Dell Inc. Inspiron 11-3168 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0XKKP9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 11-3168 dmi.product.version: 1.0.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system Status in laptop-mode-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Confirmed Status in laptop-mode-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in systemd package in Debian: Fix Released Bug description: This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery. We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue. This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only. The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log. From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times. $ grep 'EXT4-fs.*sda6' systemd-debug.log Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Those last five appear to be carrying options generated by laptop- mode-tools. User has disabled laptop-mode.service and laptop-mode.timer, and lmt- poll.service, but the issue remains. We see several reports of "read-only file-system": $ grep 'Read-only' systemd-debug.log Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system. Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system) Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system ... Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system We also see several problems with systemd's connection to Dbus: $ grep 'Transport endpoint' systemd-debug.log Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit change signal for cups-browsed.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change
[Kernel-packages] [Bug 1757445] Re: Suspend does not always resume
I'm seeing messages in syslog that show USB device(s) not reconnecting. I spoke to Jamie and his monitor is connected over a USB-C dock. That might be involved here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757445 Title: Suspend does not always resume Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 13 9350 on AC power left running overnight, suspends after a given timeout. When coming back the next morning sometimes the laptop resumes to an aubergine desktop (just the screen, no GDM) and cursor and sits there forever. Sometimes it resumes to a black screen and cursor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 21 14:15:04 2018 InstallationDate: Installed on 2018-02-13 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
AFAIK, Bolt (https://christian.kellner.me/2017/12/14/introducing-bolt- thunderbolt-3-security-levels-for-gnulinux/) will allow us to provide UI for managing security levels for Thunderbolt connected devices. It uses the Intel provided sysfs devices for configuration. If thunderbolt- tools also uses those devices, then the two should be able to co-exist, but I can see that there might end up being a fight over who owns the settings. From a desktop perspective we want the UI provided by the GNOME Shell extension and Bolt so that users don't have to drop to a command line to configure their devices. I don't have any suitable hardware to test coexistence of both thunderbolt-tools and Bolt. If the two can coexist, then I would like to use Bolt on the desktop for the ease of use. If not, and if Mario is happy, then just providing thunderbolt-tools will be more appropriate for generic Ubuntu since it will be usable on servers etc. It seems that thunderbolt-tools is more mature. I think we need Mario to make a call on which one we should be using. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No
[Kernel-packages] [Bug 1308674] Re: [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked
This issue went away for me sometime in the last year. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308674 Title: [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked -> undocked Status in Linux: New Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Fix Released Bug description: This happens on my X220, running trusty, linux 3.13.0-24-generic. It's the exact same problem discussed on https://bugzilla.redhat.com/show_bug.cgi?id=1067071. Discussed also on kernel mailing list: https://lkml.org/lkml/2014/2/19/720. It worked on 3.12, and upstream acknowledges the regression. To reproduce, remove the X220 from the dock. The brightness is set to minimum (the screen is nearly unreadable) and the brightness control is broken, you can't adjust it by hardware keys. My hardware: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21da Kernel driver in use: i915 Docked on a ThinkPad mini dock series 3. I have nothing much relevant in /var/log/syslog. Below there are excerpts of it when brightness is working: Apr 16 14:55:37 galactica kernel: [79261.217384] [drm:asle_set_backlight], bclp = 0x80ff Apr 16 14:55:37 galactica kernel: [79261.217390] [drm:asle_set_backlight], updating opregion backlight 255/255 Apr 16 14:55:37 galactica kernel: [79261.217394] [drm:intel_panel_get_max_backlight], max backlight PWM = 4648 Apr 16 14:55:37 galactica kernel: [79261.217396] [drm:intel_panel_actually_set_backlight], set backlight PWM = 4590 Apr 16 14:55:37 galactica kernel: [79261.217537] [drm:asle_set_pwm_freq], PWM freq is not supported And brightness not working: Apr 16 15:23:46 galactica kernel: [80948.263160] [drm:asle_set_backlight], bclp = 0x8058 Apr 16 15:23:46 galactica kernel: [80948.263168] [drm:asle_set_pwm_freq], PWM freq is not supported Apr 16 15:23:46 galactica kernel: [80948.280637] [drm:asle_set_backlight], bclp = 0x8041 Apr 16 15:23:46 galactica kernel: [80948.280642] [drm:asle_set_pwm_freq], PWM freq is not supported A workaround is to echo values directly to /sys/class/backlight/intel_backlight/brightness. Maximum brightness is 4648 (/sys/class/backlight/intel_backlight/max_brightness). e.g.: # echo 500 > /sys/class/backlight/intel_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ursula 3881 F pulseaudio /dev/snd/controlC0: ursula 3881 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 16 15:09:23 2014 HibernationDevice: RESUME=UUID=68890e28-0eee-4184-9456-cc267c4a5f31 InstallationDate: Installed on 2013-05-27 (323 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: LENOVO 4286CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=4db5451d-c250-47bc-9c4e-235fb1967ee5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-11-04 (162 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1308674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705466] Re: Kernel oopsed when booting
So far it was a one off, if I can make it happen again I'll report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705466 Title: Kernel oopsed when booting Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Spoke to Leann and she suggested that I log this. Artful running proposed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1870 F pulseaudio CurrentDesktop: GNOME Date: Thu Jul 20 13:14:48 2017 InstallationDate: Installed on 2017-07-10 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709) MachineType: Dell Inc. Inspiron 11-3168 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0XKKP9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 11-3168 dmi.product.version: 1.0.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705466] Re: Kernel oopsed when booting
Full kernel log ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705466/+attachment/4918118/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705466 Title: Kernel oopsed when booting Status in linux package in Ubuntu: Confirmed Bug description: Spoke to Leann and she suggested that I log this. Artful running proposed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1870 F pulseaudio CurrentDesktop: GNOME Date: Thu Jul 20 13:14:48 2017 InstallationDate: Installed on 2017-07-10 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709) MachineType: Dell Inc. Inspiron 11-3168 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0XKKP9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 11-3168 dmi.product.version: 1.0.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705466] [NEW] Kernel oopsed when booting
Public bug reported: Spoke to Leann and she suggested that I log this. Artful running proposed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1870 F pulseaudio CurrentDesktop: GNOME Date: Thu Jul 20 13:14:48 2017 InstallationDate: Installed on 2017-07-10 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709) MachineType: Dell Inc. Inspiron 11-3168 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0XKKP9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 11-3168 dmi.product.version: 1.0.1 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful package-from-proposed wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705466 Title: Kernel oopsed when booting Status in linux package in Ubuntu: Confirmed Bug description: Spoke to Leann and she suggested that I log this. Artful running proposed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1870 F pulseaudio CurrentDesktop: GNOME Date: Thu Jul 20 13:14:48 2017 InstallationDate: Installed on 2017-07-10 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709) MachineType: Dell Inc. Inspiron 11-3168 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0XKKP9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 11-3168 dmi.product.version: 1.0.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683277] Re: Mute key LED does not work on HP notebooks
** Tags removed: wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683277 Title: Mute key LED does not work on HP notebooks Status in linux package in Ubuntu: Confirmed Bug description: Description of problem: The F6/mute key on the keyboard of HP notebooks often has a built in LED indicator to show if the sound is muted. The LED state is never toggled. It will just retain its state, even though the audio is succesfully muted/unmuted. Tested with HP Envy 15 from 2015. HP Stream 11 from 2015 and HP Stream 11 from 2016. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Press mute key on HP laptop Actual results: Mute state in software toggles, LED in mute key does not. Expected results: Mute state in software and LED in mute key toggle. Additional info: This happens on kernel 4.8, 4.9 and 4.10. I have not tested any other versions. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stevenh1659 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 17 11:02:20 2017 HibernationDevice: RESUME=UUID=2d246125-abf7-4945-9542-45b25fb8fcb2 InstallationDate: Installed on 2016-09-13 (215 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81CC dmi.board.vendor: HP dmi.board.version: KBC Version 60.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/13/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687267] Re: kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
This is affecting both of my systems with Zesty (17.04). It appears to freeze most frequently in Thunderbird, when it does, it takes down the network (or, perhaps the network takes down Thunderbird). Once it happens, other programs will gradually lock up until the whole system hard freezes and requires a power reset to reboot. The final error is a general protection fault. May 9 14:58:44 devonavar-UX32VD kernel: [349888.675865] [ cut here ] May 9 14:58:44 devonavar-UX32VD kernel: [349888.675893] kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129! May 9 14:58:44 devonavar-UX32VD kernel: [349888.675920] invalid opcode: [#1] SMP May 9 14:58:44 devonavar-UX32VD kernel: [349888.675934] Modules linked in: ccm rfcomm cmac bnep bbswitch(OE) nvidia_uvm(POE) binfmt_misc nls_iso8859_1 asus_nb_wmi asus_wmi sparse_keymap mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic crct10dif_pclmul crc32_pclmul snd_hda_intel uvcvideo ghash_clmulni_intel snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hda_core videobuf2_v4l2 snd_hwdep videobuf2_core pcbc snd_pcm btusb videodev btrtl btbcm btintel media snd_seq_midi snd_seq_midi_event rtsx_usb_ms snd_rawmidi memstick aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate bluetooth intel_rapl_perf arc4 input_leds joydev snd_seq iwldvm serio_raw mac80211 snd_seq_device snd_timer iwlwifi snd nvidia(POE) soundcore mei_me cfg80211 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676158] lpc_ich mei int3403_thermal mac_hid int3402_thermal wmi int340x_thermal_zone acpi_als kfifo_buf shpchp int3400_thermal industrialio asus_wireless acpi_thermal_rel vhba(OE) parport_pc ppdev lp parport ip_tables x_tables autofs4 rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes May 9 14:58:44 devonavar-UX32VD kernel: [349888.676273] CPU: 1 PID: 2183 Comm: thunderbird Tainted: P OE 4.10.0-20-generic #22-Ubuntu May 9 14:58:44 devonavar-UX32VD kernel: [349888.676302] Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676328] task: 99cc91169680 task.stack: b4c502bbc000 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676351] RIP: 0010:__migration_entry_wait+0x16a/0x180 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676368] RSP: :b4c502bbfd68 EFLAGS: 00010246 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676386] RAX: 000fc0048078 RBX: d743052ee770 RCX: d743052ee770 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676409] RDX: 0001 RSI: 99cc8bb9d800 RDI: d74300c44000 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676432] RBP: b4c502bbfd80 R08: 99cce1680f80 R09: 99cce1680f80 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676455] R10: 7f51b02000c8 R11: 0206 R12: d74300c44000 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676478] R13: 3e031100 R14: b4c502bbfe30 R15: 99cca8a22708 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676501] FS: 7f51b1642740() GS:99cceee8() knlGS: May 9 14:58:44 devonavar-UX32VD kernel: [349888.676527] CS: 0010 DS: ES: CR0: 80050033 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676545] CR2: 7f5186b00018 CR3: 0001491d7000 CR4: 001406e0 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676568] Call Trace: May 9 14:58:44 devonavar-UX32VD kernel: [349888.676580] migration_entry_wait+0x74/0x80 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676596] do_swap_page+0x5b3/0x770 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676611] handle_mm_fault+0x873/0x1360 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676628] __do_page_fault+0x23e/0x4e0 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676642] do_page_fault+0x22/0x30 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676657] page_fault+0x28/0x30 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676669] RIP: 0033:0x559b0639706c May 9 14:58:44 devonavar-UX32VD kernel: [349888.676682] RSP: 002b:7ffcd11d75e0 EFLAGS: 00010207 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676700] RAX: RBX: 7f51b0200040 RCX: 7f51b04c0137 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676723] RDX: 0008 RSI: 1000 RDI: 7f5186b07000 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676747] RBP: 7f5186b0 R08: 7f51b02000c8 R09: May 9 14:58:44 devonavar-UX32VD kernel: [349888.676770] R10: 7f51b02000c8 R11: 0206 R12: 0200 May 9 14:58:44 devonavar-UX32VD kernel: [349888.676792] R13: 7f51b02000c8 R14: 0006 R15: 0001 May 9
[Kernel-packages] [Bug 1608820] Re: Cannot use BT speaker - sink is suspended
Added to Trello: https://trello.com/c/N0adjFrK/12-bug-1608820-cannot- use-bt-speaker-sink-is-suspended ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Luke Yelavich (themuso) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1608820 Title: Cannot use BT speaker - sink is suspended Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After a fresh boot or resuming from suspend it is possible to connect to a BT speaker but not possible to play anything. Furthermore, if I play a video from youtube, the stream plays fine if the output is the internal speaker, but as soon as I select the BT speaker the stream hangs. It resumes immediately if I switch back to the internal speaker. When I play something over the BT speaker the following lines are logged in the journal: pulseaudio[5340]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile bluetoothd[3230]: /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1: fd(24) ready rtkit-daemon[3950]: Supervising 5 threads of 1 processes of 1 users. rtkit-daemon[3950]: Successfully made thread 28532 of process 5340 (n/a) owned by '1000' RT at priority 5. rtkit-daemon[3950]: Supervising 6 threads of 1 processes of 1 users. pulseaudio[5340]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_B8_69_C2_3D_56_CE/fd1 (Operation Not Authorized) kernel: input: B8:69:C2:3D:56:CE as /devices/virtual/input/input26 pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. gnome-session[5383]: ** (zeitgeist-datahub:5874): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required wpa_supplicant[3556]: wlan0: WPA: Group rekeying completed with 14:0c:76:71:a1:f4 [GTK=CCMP] pulseaudio[5340]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 2 09:09:18 2016 InstallationDate: Installed on 2013-09-03 (1063 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C4:85:08:A7:45:76 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING RX bytes:3492 acl:70 sco:0 events:137 errors:0 TX bytes:4838 acl:64 sco:0 commands:57 errors:0 upstart.bluetooth.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Automatically added comment
Added to Trello: https://trello.com/c/4XMcUQcb/14-bug-1510344-keyboard- backlight-turns-on-at-boot ** Tags removed: desktop-trello-import -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in gnome-settings-daemon: Fix Released Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot
Added to Trello: https://trello.com/c/WMkMUwl1/3-bug-1510344-keyboard- backlight-turns-on-at-boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510344 Title: Keyboard Backlight Turns on at boot Status in Dell Sputnik: Confirmed Status in One Hundred Papercuts: Confirmed Status in Linux: Invalid Status in linux package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: System: Dell XPS 13 9343 Action: Boot computer Expected Behavior: Keyboard backlight would be off when computer is booted Actual Behavior: Keyboard backlight is on at boot This did not happen with Ubuntu 15.04 There are new files in Ubuntu 15.10 - /sys/class/leds/dell::kbd_backlight$ cat stop_timeout 60s cat start_triggers +keyboard +touchpad cat trigger [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 rfkill0 cat brightness 2 --- Unsure if these files are important, but included in the report ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-2-generic 4.1.0-2.2 ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3 Uname: Linux 4.1.0-2-generic x86_64 ApportVersion: 2.18-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2488 F pulseaudio /dev/snd/controlC0: ubuntu 2488 F pulseaudio CasperVersion: 1.362 CurrentDesktop: Unity Date: Tue Oct 27 01:29:47 2015 IwConfig: enx00249b0981e3 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt RelatedPackageVersions: linux-restricted-modules-4.1.0-2-generic N/A linux-backports-modules-4.1.0-2-generic N/A linux-firmware 1.145 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546092] Re: computer freezes frequently
Rick's kernel log available here: http://pastebin.ubuntu.com/15077887/ Line 10556 shows nulls being written to the log and then presumably the machine being rebooted because it has hung. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1546092 Title: computer freezes frequently Status in linux package in Ubuntu: Confirmed Bug description: Running Xenial. Freezes seem to happen every 5 to 45 minutes. I have not been able to create any repro steps, it feels quite random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-4-generic 4.4.0-4.19 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1780 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 16 08:26:12 2016 HibernationDevice: RESUME=UUID=36268acb-4215-452f-9778-754c015d00d8 InstallationDate: Installed on 2016-02-02 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: TOSHIBA Satellite L15W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed root=UUID=ed019e52-c90e-48b7-bbe4-ae5d39fea067 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-4-generic N/A linux-backports-modules-4.4.0-4-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.00 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 0670 dmi.board.vendor: FF40 dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.00:bd07/16/2015:svnTOSHIBA:pnSatelliteL15W-B:pvrPSKVUU-00S01U:rvnFF40:rn0670:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite L15W-B dmi.product.version: PSKVUU-00S01U dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1348550] Re: When undocking the laptop panel brightness goes to minimum and cannot be increased
*** This bug is a duplicate of bug 1308674 *** https://bugs.launchpad.net/bugs/1308674 ** This bug has been marked a duplicate of bug 1308674 [Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken when going from docked - undocked -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348550 Title: When undocking the laptop panel brightness goes to minimum and cannot be increased Status in “linux” package in Ubuntu: Incomplete Bug description: My X220 sits on a docking station connected to (among other things) an external DisplayPort monitor. I have it set up so that I use both monitors. When I undock the laptop, and so remove the external display, the laptop panel brightness goes to minimum and cannot be made brighter either via the function keys or the system settings slider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2179 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 10:15:40 2014 HibernationDevice: RESUME=UUID=48c1ab97-c081-4af0-a42d-2ffe656eed00 InstallationDate: Installed on 2013-12-24 (212 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4287CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=3238572a-b1a6-4e68-aade-1c58b750f578 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-19 (96 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1348550] Re: When undocking the laptop panel brightness goes to minimum and cannot be increased
I downloaded the latest BIOS ISO from the Lenovo website, but it seems to be broken. The ISO is empty. I'm trying to find an older version to see if that works. From the README with the BIOS update there is nothing which suggests anything do to with this bug has been fixed. I'll keep trying though. This didn't used to happen though, so my feeling is that its something introduced in 14.04. I can't prove it though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348550 Title: When undocking the laptop panel brightness goes to minimum and cannot be increased Status in “linux” package in Ubuntu: Incomplete Bug description: My X220 sits on a docking station connected to (among other things) an external DisplayPort monitor. I have it set up so that I use both monitors. When I undock the laptop, and so remove the external display, the laptop panel brightness goes to minimum and cannot be made brighter either via the function keys or the system settings slider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2179 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 10:15:40 2014 HibernationDevice: RESUME=UUID=48c1ab97-c081-4af0-a42d-2ffe656eed00 InstallationDate: Installed on 2013-12-24 (212 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4287CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=3238572a-b1a6-4e68-aade-1c58b750f578 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-19 (96 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1348550] [NEW] When undocking the laptop panel brightness goes to minimum and cannot be increased
Public bug reported: My X220 sits on a docking station connected to (among other things) an external DisplayPort monitor. I have it set up so that I use both monitors. When I undock the laptop, and so remove the external display, the laptop panel brightness goes to minimum and cannot be made brighter either via the function keys or the system settings slider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2179 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 10:15:40 2014 HibernationDevice: RESUME=UUID=48c1ab97-c081-4af0-a42d-2ffe656eed00 InstallationDate: Installed on 2013-12-24 (212 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4287CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=3238572a-b1a6-4e68-aade-1c58b750f578 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-19 (96 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348550 Title: When undocking the laptop panel brightness goes to minimum and cannot be increased Status in “linux” package in Ubuntu: New Bug description: My X220 sits on a docking station connected to (among other things) an external DisplayPort monitor. I have it set up so that I use both monitors. When I undock the laptop, and so remove the external display, the laptop panel brightness goes to minimum and cannot be made brighter either via the function keys or the system settings slider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2179 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 10:15:40 2014 HibernationDevice: RESUME=UUID=48c1ab97-c081-4af0-a42d-2ffe656eed00 InstallationDate: Installed on 2013-12-24 (212 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4287CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=3238572a-b1a6-4e68-aade-1c58b750f578 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-19 (96 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1348550] Re: When undocking the laptop panel brightness goes to minimum and cannot be increased
It seems that this only happens the first time I undock. If I re-dock the brightness goes back to as it was (e.g. full) and then subsequent un-docking keeps the brightness at the correct level. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1348550 Title: When undocking the laptop panel brightness goes to minimum and cannot be increased Status in “linux” package in Ubuntu: Confirmed Bug description: My X220 sits on a docking station connected to (among other things) an external DisplayPort monitor. I have it set up so that I use both monitors. When I undock the laptop, and so remove the external display, the laptop panel brightness goes to minimum and cannot be made brighter either via the function keys or the system settings slider. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: will 2179 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 25 10:15:40 2014 HibernationDevice: RESUME=UUID=48c1ab97-c081-4af0-a42d-2ffe656eed00 InstallationDate: Installed on 2013-12-24 (212 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 4287CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=3238572a-b1a6-4e68-aade-1c58b750f578 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-19 (96 days ago) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1195483] Re: [Asus ZenBook Prime UX31A] Installation, Live and Check disc do not start
Ok, now that I've figured out how to upgrade the kernel properly, I can confirm that the issue is resolved on my Asus Zenbook UX32VD for 3.11.0-15-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1195483 Title: [Asus ZenBook Prime UX31A] Installation, Live and Check disc do not start Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Raring: In Progress Status in “linux” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Fix Released Bug description: When I try to install Ubuntu 13.04 on a new Asus ZenBook Prime UX31A from june 2013, grub will come up bit every option such as Installation, Live and Check disc result in a blank screen. This is possibly due to preinstalled Windows 8 and UEFI. I did not approve/accept the Windows 8 installation and that should not matter. I want to install only Ubuntu and *no* dual boot with the preinstalled Windows 8. I want to erase the entire disc in firsts steps of installation procedure. Screenshot illustrating the problem are: http://i.imgur.com/94zPRh5.jpg (ASUS splash screen) http://i.imgur.com/CKJZf6s.jpg (language selection for Windows 8) http://i.imgur.com/2OIGnra.jpg (accept license, which I did not and rebooted with F1/F2) http://i.imgur.com/0l3ZIme.jpg (general BIOS info, I upgrade to latest BIOS) http://i.imgur.com/RtjRraF.jpg (used settings to boot from USB) http://i.imgur.com/Vgb3Xju.jpg (grub which goes to black screen and systems is locked in that state) For more information, see: device information https://help.ubuntu.com/community/AsusZenbookPrime similar problem http://ubuntuforums.org/showthread.php?t=2149954 UEFI and preinstalled Windwos 8 http://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-uefi-supported-windows-8-system More about EUFI https://help.ubuntu.com/community/UEFI More on installing without WUBI http://www.omgubuntu.co.uk/2013/04/wubi-advice Debugging attempts from https://wiki.archlinux.org/index.php/Boot_Debugging failed. Perhaps I did something wrong. What are ways to write debug to the screen in my case? And, more importantly, how do I get it working because have the right to install whatever I want? Is the only way to get it installed to accept the Windows 8 license and install Ubuntu from Windows (and in effect making it dual boot which I don't want). Ubuntu should fix this as it is the flagship of a major laptop manufacturer (ASUS) for which Ubuntu is no longer installable. --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 2424 F pulseaudio DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=24994e67-9b18-4cad-b387-788beff8b388 InstallationDate: Installed on 2013-07-06 (80 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. UX31A MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 StagingDrivers: rts5139 Tags: raring staging raring staging raring staging Uname: Linux 3.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31A.218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31A.218:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX31A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1195483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1195483] Re: [Asus ZenBook Prime UX31A] Installation, Live and Check disc do not start
I'm afraid I don't understand the versioning system for linux properly... I got myself on -proposed, updated via apt-get, and pulled down 3.11.0.15.16. Does this version contain 3.11.0-15.22? What is the difference between the 0.15 versions that I can get from apt, and the 0-15 version that is referenced here? If the version from -proposed does not contain the proposed fix, should I be trying to apply the .debs directly? I'd rather not mess with my kernel outside of apt, since I'm not 100% sure how it integrates back in... If 3.11.0.15.16 DOES contain the proposed fix, it does NOT fix this problem on the ASUS UX32VD, which I had assumed it would. I have not seen a parallel bug report for my specific model — should I be creating one? Most problem fixes I've seen have directed me to this bug report or one of the duplicates. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1195483 Title: [Asus ZenBook Prime UX31A] Installation, Live and Check disc do not start Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Raring: In Progress Status in “linux” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Fix Released Bug description: When I try to install Ubuntu 13.04 on a new Asus ZenBook Prime UX31A from june 2013, grub will come up bit every option such as Installation, Live and Check disc result in a blank screen. This is possibly due to preinstalled Windows 8 and UEFI. I did not approve/accept the Windows 8 installation and that should not matter. I want to install only Ubuntu and *no* dual boot with the preinstalled Windows 8. I want to erase the entire disc in firsts steps of installation procedure. Screenshot illustrating the problem are: http://i.imgur.com/94zPRh5.jpg (ASUS splash screen) http://i.imgur.com/CKJZf6s.jpg (language selection for Windows 8) http://i.imgur.com/2OIGnra.jpg (accept license, which I did not and rebooted with F1/F2) http://i.imgur.com/0l3ZIme.jpg (general BIOS info, I upgrade to latest BIOS) http://i.imgur.com/RtjRraF.jpg (used settings to boot from USB) http://i.imgur.com/Vgb3Xju.jpg (grub which goes to black screen and systems is locked in that state) For more information, see: device information https://help.ubuntu.com/community/AsusZenbookPrime similar problem http://ubuntuforums.org/showthread.php?t=2149954 UEFI and preinstalled Windwos 8 http://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-uefi-supported-windows-8-system More about EUFI https://help.ubuntu.com/community/UEFI More on installing without WUBI http://www.omgubuntu.co.uk/2013/04/wubi-advice Debugging attempts from https://wiki.archlinux.org/index.php/Boot_Debugging failed. Perhaps I did something wrong. What are ways to write debug to the screen in my case? And, more importantly, how do I get it working because have the right to install whatever I want? Is the only way to get it installed to accept the Windows 8 license and install Ubuntu from Windows (and in effect making it dual boot which I don't want). Ubuntu should fix this as it is the flagship of a major laptop manufacturer (ASUS) for which Ubuntu is no longer installable. --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 2424 F pulseaudio DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=24994e67-9b18-4cad-b387-788beff8b388 InstallationDate: Installed on 2013-07-06 (80 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. UX31A MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 StagingDrivers: rts5139 Tags: raring staging raring staging raring staging Uname: Linux 3.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31A.218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1229686] Re: No video output at all when booting 13.10 on Asus Zenbook UX31A
I have what I believe is the same bug affecting an ASUS UX32VD. I have also been unable to figure out what logs to post, but the system appears to boot normally with no video output. I believe it is the same Kernel bug as is reported for ArchLinux here: https://bbs.archlinux.org/viewtopic.php?id=167463, as the symptoms sound the same and the suggested workaround is effective. I am able to successfully boot the most recent 3.8 kernel with Ubuntu 13.10 installed, but the default 3.11 kernel does not appear to work. Workaround: Switch to CSM mode in BIOS, thus avoiding UEFI boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1229686 Title: No video output at all when booting 13.10 on Asus Zenbook UX31A Status in “linux” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 from 13.04 my computer booted into a black screen. I could hear the login sound but couldn't see anything. Switching to some virtual console isn't working either, nor was anything visible during the boot process. I also tried to boot 13.10 from USB with a very similar result. The IGP of the Zenbook UX31A is the Intel HD4000. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
