[Bug 1920632] Re: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works
Tested kernel 5.8.0-49 on Ubuntu 20.04. I acknowledge it works perfectly now. The bug is fixed. Thank you for all your great effort. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920632 Title: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1920632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920632] Re: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works
Thanks for handling the issue. I see I missed the update. I'll wait then, till the new kernel is available. Should I report results here? BTW - how do I ensure that kernel is in 5.8.0-48 (or any other?). All I can get from 'uname -r' is i.e. 5.8.0-44-generic without the bugfix version. Regards, P. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920632 Title: use of Wacom stylus causes immediate system hang with kernel 5.8.0-45, but 5.8.0-44 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1920632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920632] Re: use of Wacom stylus causes immediate system hang
I saw kernel 5.8.0-48 has been released. I've updated 5.8.0-44 to 5.8.0-48 and it didn't help, unfortunately. Any use of Wacom stylus causes immediately OS hung and unresponsive. Rolling back to 5.8.0-44. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920632 Title: use of Wacom stylus causes immediate system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920632] Re: use of Wacom stylus causes immediate system hang
Sure, I can test with the new kernel, once available. Just enabled pre- released updates according to the manual [5], but so far, apt update && apt upgrade do not bring any new kernel. Is this already published via proposed channel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920632 Title: use of Wacom stylus causes immediate system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920632] [NEW] use of Wacom stylus causes immediate system hang
Public bug reported: Once updated kernel from 5.8.0-44 to 5.8.0.45, any use of Wacom stylus causes immediate system hang, frozen both GUI and OS. Removing the Wacom kernel module solves the problem (no more hangs, but the stylus is unusable then). Rolling back to kernel 5.8.0-44 or any earlier solves the problem. The OS is: Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 20 18:53:56 2021 InstallationDate: Installed on 2020-04-24 (329 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920632 Title: use of Wacom stylus causes immediate system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920632] Re: use of Wacom stylus causes immediate system hang
The exact machine is a Lenovo Yoga X390. Module causing hang is: lsmod | grep wacom wacom 118784 0 usbhid 57344 1 wacom hid 135168 5 wacom,usbhid,hid_sensor_hub,intel_ishtp_hid,hid_generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920632 Title: use of Wacom stylus causes immediate system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1920632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Same here with Lenovo Yoga S1 laptop :(. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
Same here (Ubuntu 17.10): CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733887] [NEW] Instalator crashes on first daemon run after install. Config files seem not to be copied during install.
Public bug reported: Hi, I cannot make installer work for me through the repository. The OS is Ubuntu 17.10: Linux n317-pc01 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux For some unknown reasons, installer does not copy template config files. Any help is appreciated. installer output pczekalski@n317-pc01:~$ sudo apt-get install open-iscsi [sudo] password for pczekalski: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libisns0 The following NEW packages will be installed: libisns0 open-iscsi 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/392 kB of archives. After this operation, 2419 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Preconfiguring packages ... Selecting previously unselected package libisns0:amd64. (Reading database ... 240358 files and directories currently installed.) Preparing to unpack .../libisns0_0.97-2_amd64.deb ... Unpacking libisns0:amd64 (0.97-2) ... Selecting previously unselected package open-iscsi. Preparing to unpack .../open-iscsi_2.0.874-4ubuntu3_amd64.deb ... Unpacking open-iscsi (2.0.874-4ubuntu3) ... Processing triggers for ureadahead (0.100.0-20) ... Setting up libisns0:amd64 (0.97-2) ... Processing triggers for initramfs-tools (0.125ubuntu12) ... update-initramfs: Generating /boot/initrd.img-4.13.0-16-generic cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory Setting up open-iscsi (2.0.874-4ubuntu3) ... Job for iscsid.service failed because the control process exited with error code. See "systemctl status iscsid.service" and "journalctl -xe" for details. invoke-rc.d: initscript iscsid, action "restart" failed. ● iscsid.service - iSCSI initiator daemon (iscsid) Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2017-11-22 15:46:40 CET; 6ms ago Docs: man:iscsid(8) Process: 10191 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, status=1/FAILURE) lis 22 15:46:40 n317-pc01 systemd[1]: Starting iSCSI initiator daemon (iscsid)... lis 22 15:46:40 n317-pc01 startup-checks.sh[10191]: Error: configuration file /etc/iscsi/iscsid.conf is missing! lis 22 15:46:40 n317-pc01 startup-checks.sh[10191]: The iSCSI driver has not been correctly installed and cannot start. lis 22 15:46:40 n317-pc01 systemd[1]: iscsid.service: Control process exited, code=exited status=1 lis 22 15:46:40 n317-pc01 systemd[1]: Failed to start iSCSI initiator daemon (iscsid). lis 22 15:46:40 n317-pc01 systemd[1]: iscsid.service: Unit entered failed state. lis 22 15:46:40 n317-pc01 systemd[1]: iscsid.service: Failed with result 'exit-code'. dpkg: error processing package open-iscsi (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.26-0ubuntu2) ... Processing triggers for systemd (234-2ubuntu12.1) ... Processing triggers for man-db (2.7.6.1-2) ... Processing triggers for initramfs-tools (0.125ubuntu12) ... update-initramfs: Generating /boot/initrd.img-4.13.0-16-generic cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory Errors were encountered while processing: open-iscsi E: Sub-process /usr/bin/dpkg returned an error code (1) -- pczekalski@n317-pc01:~$ systemctl status iscsid.service ● iscsid.service - iSCSI initiator daemon (iscsid) Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2017-11-22 15:46:40 CET; 5min ago Docs: man:iscsid(8) lis 22 15:46:40 n317-pc01 systemd[1]: Starting iSCSI initiator daemon (iscsid)... lis 22 15:46:40 n317-pc01 startup-checks.sh[10191]: Error: configuration file /etc/iscsi/iscsid.conf is missing! lis 22 15:46:40 n317-pc01 startup-checks.sh[10191]: The iSCSI driver has not been correctly installed and cannot start. lis 22 15:46:40 n317-pc01 systemd[1]: iscsid.service: Control process exited, code=exited status=1 lis 22 15:46:40 n317-pc01 systemd[1]: Failed to start iSCSI initiator daemon (iscsid). lis 22 15:46:40 n317-pc01 systemd[1]: iscsid.service: Unit entered failed state. lis 22 15:46:40 n317-pc01 systemd[1]: iscsid.service: Failed with result 'exit-code'. ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New ** Tags: 17.10 config files installer ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733887 Title: Instalator crashes on first daemon run after install. Config files seem not to be copied during install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1733887/+subscriptions -- ubuntu-bugs mailing list
