[Kernel-packages] [Bug 1830537] [NEW] missing max_match_rules_per_connection
Public bug reported: Hi, I'm currently trying to debug why my Bluetooth Barcode scanner (emulating a keyboard) with a USB bluetooth dongle does not work anymore with my 18.04, can't connect it anoymore (it used to work at lease occasionally months ago.) It pairs, but can't be connected as a HID. One of the problems was that error message in /var/log/syslog: Connection ":1.182" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=2048) After adding 1024 2048 to the busconfig struct in /etc/dbus-1/system.d/bluetooth.conf at least this error message vanished (while others persist, still does not work). However, this should be in /etc/dbus-1/system.d/bluetooth.conf as delivered from the package and not require the user to debug and change. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 26 14:37:28 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:2128 acl:0 sco:0 events:126 errors:0 TX bytes:4712 acl:0 sco:0 commands:106 errors:0 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1830537 Title: missing max_match_rules_per_connection Status in bluez package in Ubuntu: New Bug description: Hi, I'm currently trying to debug why my Bluetooth Barcode scanner (emulating a keyboard) with a USB bluetooth dongle does not work anymore with my 18.04, can't connect it anoymore (it used to work at lease occasionally months ago.) It pairs, but can't be connected as a HID. One of the problems was that error message in /var/log/syslog: Connection ":1.182" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=2048) After adding 1024 2048 to the busconfig struct in /etc/dbus-1/system.d/bluetooth.conf at least this error message vanished (while others persist, still does not work). However, this should be in /etc/dbus-1/system.d/bluetooth.conf as delivered from the package and not require the user to debug and change. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 26 14:37:28 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/
[Kernel-packages] [Bug 1830538] [NEW] Can't get HIDP connection info
Public bug reported: Hi, I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard emulation mode) with a USB bluetooth dongle in an 18.04 machine, which used to work some months ago. Now I can still pair them, the ubuntu machine sees the devices and lists as paired, but can't connect with human interface device service (HID). /var/log/syslog says May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange (52) Since the scanner and the usb dongle are unchanged, it must be a problem of the ubuntu machine. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 26 14:48:12 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:3400 acl:0 sco:0 events:192 errors:0 TX bytes:5012 acl:0 sco:0 commands:142 errors:0 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1830538 Title: Can't get HIDP connection info Status in bluez package in Ubuntu: New Bug description: Hi, I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard emulation mode) with a USB bluetooth dongle in an 18.04 machine, which used to work some months ago. Now I can still pair them, the ubuntu machine sees the devices and lists as paired, but can't connect with human interface device service (HID). /var/log/syslog says May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange (52) Since the scanner and the usb dongle are unchanged, it must be a problem of the ubuntu machine. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 26 14:48:12 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:3400 acl:0 sco:0 events:192 errors:0 TX bytes:5012 acl:0 sco:0 command
[Kernel-packages] [Bug 1830538] Re: Can't get HIDP connection info
See https://bugzilla.redhat.com/show_bug.cgi?id=1671135 https://forums.fedoraforum.org/showthread.php?320530-Kernel-4-19-15-300-fc29 -broke-bluetooth-HIDP ** Bug watch added: Red Hat Bugzilla #1671135 https://bugzilla.redhat.com/show_bug.cgi?id=1671135 -- 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/1830538 Title: Can't get HIDP connection info Status in linux package in Ubuntu: Confirmed Bug description: Hi, I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard emulation mode) with a USB bluetooth dongle in an 18.04 machine, which used to work some months ago. Now I can still pair them, the ubuntu machine sees the devices and lists as paired, but can't connect with human interface device service (HID). /var/log/syslog says May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange (52) Since the scanner and the usb dongle are unchanged, it must be a problem of the ubuntu machine. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 26 14:48:12 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:3400 acl:0 sco:0 events:192 errors:0 TX bytes:5012 acl:0 sco:0 commands:142 errors:0 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830538/+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 1688017] [NEW] Connection to bluetooth headsets fails
Public bug reported: Hi, since upgrading to 17.04 I can't connect to bluetooth headsets anymore. Headsets are found and listed as devices, but when trying to connect, there's an error blueman.bluez.errors.DBusFailedError: Protocol not available... syslog says: May 3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available] May 3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating services: Operation already in progress (114) May 3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0 May 3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available] Here someone else reports the same observation: http://www.1oo.club/bluetooth-unable-to-connect-to-headphones-after-ubuntu-17-04-upgrade/ ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 3 17:12:51 2017 InstallationDate: Installed on 2016-04-22 (376 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420) InterestingModules: bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash noplymouth nomodeset text SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-04-18 (15 days ago) dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N3150-NUC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. 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.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:BB:58:C1:E9:FA ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:18751 acl:51 sco:0 events:1345 errors:0 TX bytes:27309 acl:48 sco:0 commands:1243 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1688017 Title: Connection to bluetooth headsets fails Status in bluez package in Ubuntu: New Bug description: Hi, since upgrading to 17.04 I can't connect to bluetooth headsets anymore. Headsets are found and listed as devices, but when trying to connect, there's an error blueman.bluez.errors.DBusFailedError: Protocol not available... syslog says: May 3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available] May 3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating services: Operation already in progress (114) May 3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0 May 3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available May 3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available] Here someone else reports the same observation: http://www.1oo.club/bluetooth-unable-to-connect-to-headphones-after-u
[Kernel-packages] [Bug 1901417] Re: zfs mount segmentation fault when target directory is non empty
I was able to reliably reproduce the bug on that machine on the same day several times, so the bug was there definitely, even after rebooting, but I wasn't able to reproduce it after opening the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1901417 Title: zfs mount segmentation fault when target directory is non empty Status in zfs-linux package in Ubuntu: Incomplete Bug description: Hi, I just had made some mistake in a mounting order, thus producing non- empty target directory. Imagine a pool name pool1 and zfs filesystems pool1 and pool1/a which are (due to different encryption keys) to be mounted as /pool1/a one in another. (Because of encryption not automatically mounted) I made a simple mistake and mounted /pool1/a before /pool1, but noticed and unmounted /pool1/a before mounting /pool1, but forget to rmdir /pool1/a, so /pool1 was not empty when mounting /pool1. # zfs mount -a cannot mount '/pool1': directory is not empty zsh: segmentation fault (core dumped) zfs mount -a Segmentation faults should not happen. after rmdir /pool1/a (i.e. make the target empty), things work as normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Oct 25 15:28:45 2020 InstallationDate: Installed on 2018-04-30 (909 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-10-02 (23 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1901417/+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 1901417] [NEW] zfs mount segmentation fault when target directory is non empty
Public bug reported: Hi, I just had made some mistake in a mounting order, thus producing non- empty target directory. Imagine a pool name pool1 and zfs filesystems pool1 and pool1/a which are (due to different encryption keys) to be mounted as /pool1/a one in another. (Because of encryption not automatically mounted) I made a simple mistake and mounted /pool1/a before /pool1, but noticed and unmounted /pool1/a before mounting /pool1, but forget to rmdir /pool1/a, so /pool1 was not empty when mounting /pool1. # zfs mount -a cannot mount '/pool1': directory is not empty zsh: segmentation fault (core dumped) zfs mount -a Segmentation faults should not happen. after rmdir /pool1/a (i.e. make the target empty), things work as normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Oct 25 15:28:45 2020 InstallationDate: Installed on 2018-04-30 (909 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-10-02 (23 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1901417 Title: zfs mount segmentation fault when target directory is non empty Status in zfs-linux package in Ubuntu: New Bug description: Hi, I just had made some mistake in a mounting order, thus producing non- empty target directory. Imagine a pool name pool1 and zfs filesystems pool1 and pool1/a which are (due to different encryption keys) to be mounted as /pool1/a one in another. (Because of encryption not automatically mounted) I made a simple mistake and mounted /pool1/a before /pool1, but noticed and unmounted /pool1/a before mounting /pool1, but forget to rmdir /pool1/a, so /pool1 was not empty when mounting /pool1. # zfs mount -a cannot mount '/pool1': directory is not empty zsh: segmentation fault (core dumped) zfs mount -a Segmentation faults should not happen. after rmdir /pool1/a (i.e. make the target empty), things work as normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Oct 25 15:28:45 2020 InstallationDate: Installed on 2018-04-30 (909 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-10-02 (23 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1901417/+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 1901417] Re: zfs mount segmentation fault when target directory is non empty
I currently can't reproduce the problem myself. I do recall that it was the order of mounting. I have a freshly created zpool where the pool was created with one password, and one of it's sub- ZFS-trees with a different one, wanted to mount it and make the mistake to enter a wrong password for the pool, thus unlocked the inner part only and mounted them in wrong order. It was reproducable and crashed with a segfault every time I tried it until removing the directory stub, but have not yet been able to reproduce since I rebooted the machine. Still trying... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1901417 Title: zfs mount segmentation fault when target directory is non empty Status in zfs-linux package in Ubuntu: Incomplete Bug description: Hi, I just had made some mistake in a mounting order, thus producing non- empty target directory. Imagine a pool name pool1 and zfs filesystems pool1 and pool1/a which are (due to different encryption keys) to be mounted as /pool1/a one in another. (Because of encryption not automatically mounted) I made a simple mistake and mounted /pool1/a before /pool1, but noticed and unmounted /pool1/a before mounting /pool1, but forget to rmdir /pool1/a, so /pool1 was not empty when mounting /pool1. # zfs mount -a cannot mount '/pool1': directory is not empty zsh: segmentation fault (core dumped) zfs mount -a Segmentation faults should not happen. after rmdir /pool1/a (i.e. make the target empty), things work as normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Oct 25 15:28:45 2020 InstallationDate: Installed on 2018-04-30 (909 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-10-02 (23 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1901417/+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 1731693] [NEW] kernel crash/freeze during shutdown
Public bug reported: Hi, I have a brandnew HP Microserver Gen10 with a freshly installed and almoste bare Ubuntu 16.04 and its 4.4.0-98-generic kernel, two additional disks, and zfs. Runs stable, but during shutdown it happened many times that the kernel crashed and the machine completely froze (or hung in shutdown). Since the machine was dead then, the only option to get the details was a "screenshot" of the screen (as attached). I've running a similar configuration on other machines, including older Microserver models, but never saw that on any other machine. Reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=197853 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 11 22:54 seq crw-rw 1 root audio 116, 33 Nov 11 22:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Nov 11 23:16:03 2017 HibernationDevice: RESUME=UUID=05c2d8e4-5d35-415a-bc30-628c0d1e92e3 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HPE ProLiant MicroServer Gen10 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 LC_MESSAGES=C.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=9550da16-2d0f-44fa-acc6-886dca3f9eb7 ro nomodeset nosplash quiet RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ProLiant MicroServer Gen10 dmi.board.vendor: HPE dmi.board.version: 871721-001 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: HPE dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd05/25/2017:svnHPE:pnProLiantMicroServerGen10:pvrRevB:rvnHPE:rnProLiantMicroServerGen10:rvr871721-001:cvnHPE:ct1:cvrDefaultstring: dmi.product.name: ProLiant MicroServer Gen10 dmi.product.version: Rev B dmi.sys.vendor: HPE ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1731693 Title: kernel crash/freeze during shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a brandnew HP Microserver Gen10 with a freshly installed and almoste bare Ubuntu 16.04 and its 4.4.0-98-generic kernel, two additional disks, and zfs. Runs stable, but during shutdown it happened many times that the kernel crashed and the machine completely froze (or hung in shutdown). Since the machine was dead then, the only option to get the details was a "screenshot" of the screen (as attached). I've running a similar configuration on other machines, including older Microserver models, but never saw that on any other machine. Reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=197853 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 11 22:54 seq crw-rw 1 root audio 116, 33 Nov 11 22:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Nov 11 23:16:03 2017 HibernationDevice: RESUME=UUID=05c2d8e4-5d35-415a-bc30-628c0d1e92e3 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 001 De
[Kernel-packages] [Bug 1731693] Re: kernel crash/freeze during shutdown
** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731693/+attachment/5007643/+files/screen.jpg -- 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/1731693 Title: kernel crash/freeze during shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a brandnew HP Microserver Gen10 with a freshly installed and almoste bare Ubuntu 16.04 and its 4.4.0-98-generic kernel, two additional disks, and zfs. Runs stable, but during shutdown it happened many times that the kernel crashed and the machine completely froze (or hung in shutdown). Since the machine was dead then, the only option to get the details was a "screenshot" of the screen (as attached). I've running a similar configuration on other machines, including older Microserver models, but never saw that on any other machine. Reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=197853 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 11 22:54 seq crw-rw 1 root audio 116, 33 Nov 11 22:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Nov 11 23:16:03 2017 HibernationDevice: RESUME=UUID=05c2d8e4-5d35-415a-bc30-628c0d1e92e3 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HPE ProLiant MicroServer Gen10 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 LC_MESSAGES=C.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=9550da16-2d0f-44fa-acc6-886dca3f9eb7 ro nomodeset nosplash quiet RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ProLiant MicroServer Gen10 dmi.board.vendor: HPE dmi.board.version: 871721-001 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: HPE dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd05/25/2017:svnHPE:pnProLiantMicroServerGen10:pvrRevB:rvnHPE:rnProLiantMicroServerGen10:rvr871721-001:cvnHPE:ct1:cvrDefaultstring: dmi.product.name: ProLiant MicroServer Gen10 dmi.product.version: Rev B dmi.sys.vendor: HPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731693/+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 1731693] Re: kernel crash/freeze during shutdown
I've made some tests meanwhile with the latest 4.14 ubuntu kernel package, but could not reproduce the bug with the tests under that kernel so far, but that does not really and realiably mean anything, because - the kernel freeze occures occasionally only, therefore difficult to prove the absence by a few tests. - the machine needs zfs to use it's additional disks and I don't get the zfs kernel modules with that 4.14 package, so it's unclear whether the bug is somehow caused by zfs modules. Furthermore, I cannot test the machine intensively (and under similar usage) without zfs. To be comparable, the 4.14 kernel package would need to be compiled in the very same way as the 4.4 kernel that comes with 16.04. -- 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/1731693 Title: kernel crash/freeze during shutdown Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hi, I have a brandnew HP Microserver Gen10 with a freshly installed and almoste bare Ubuntu 16.04 and its 4.4.0-98-generic kernel, two additional disks, and zfs. Runs stable, but during shutdown it happened many times that the kernel crashed and the machine completely froze (or hung in shutdown). Since the machine was dead then, the only option to get the details was a "screenshot" of the screen (as attached). I've running a similar configuration on other machines, including older Microserver models, but never saw that on any other machine. Reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=197853 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 11 22:54 seq crw-rw 1 root audio 116, 33 Nov 11 22:54 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Nov 11 23:16:03 2017 HibernationDevice: RESUME=UUID=05c2d8e4-5d35-415a-bc30-628c0d1e92e3 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HPE ProLiant MicroServer Gen10 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 LC_MESSAGES=C.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=9550da16-2d0f-44fa-acc6-886dca3f9eb7 ro nomodeset nosplash quiet RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ProLiant MicroServer Gen10 dmi.board.vendor: HPE dmi.board.version: 871721-001 dmi.chassis.asset.tag: Default string dmi.chassis.type: 1 dmi.chassis.vendor: HPE dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd05/25/2017:svnHPE:pnProLiantMicroServerGen10:pvrRevB:rvnHPE:rnProLiantMicroServerGen10:rvr871721-001:cvnHPE:ct1:cvrDefaultstring: dmi.product.name: ProLiant MicroServer Gen10 dmi.product.version: Rev B dmi.sys.vendor: HPE To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1731693/+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 1729608] [NEW] arithmetic expression: expecting primary: " (32-)/4 "
Public bug reported:
Hi,
I've configured a bridge interface (named vlan0) through interfaces, but
can't take it up with ifup, since the if-up-script from ubuntu-fan
aborts with error status
reason:
# fanctl net start vlan0
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting
primary: " (32-)/4 "
As far as I can see the problem is that in cmd_net_up() the line
addr="${addr%/*}"
cuts the mask from the interface config and passes the pure ip address
only, but later config_filename() calls width_to_mask(), which tries to
use the (now missing) mask.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-fan 0.12.6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov 2 14:26:42 2017
InstallationDate: Installed on 2017-10-24 (9 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitecture: all
SourcePackage: ubuntu-fan
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-fan (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1729608
Title:
arithmetic expression: expecting primary: " (32-)/4 "
Status in ubuntu-fan package in Ubuntu:
New
Bug description:
Hi,
I've configured a bridge interface (named vlan0) through interfaces,
but can't take it up with ifup, since the if-up-script from ubuntu-fan
aborts with error status
reason:
# fanctl net start vlan0
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting
primary: " (32-)/4 "
As far as I can see the problem is that in cmd_net_up() the line
addr="${addr%/*}"
cuts the mask from the interface config and passes the pure ip address
only, but later config_filename() calls width_to_mask(), which tries
to use the (now missing) mask.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-fan 0.12.6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov 2 14:26:42 2017
InstallationDate: Installed on 2017-10-24 (9 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
PackageArchitecture: all
SourcePackage: ubuntu-fan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1729608/+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 1568466] [NEW] BIOS function to disable touchpad not working
Public bug reported: Hi, I have an ASUS notebook with - like virtually all notebooks - a touchpad in front, which generates bogus mouse input when using the keyboard due to hand movements. Therefore the notebook has - like most notebooks - a special function (press Fn + blue symbols on keys) to disable the touchpad when using an external mouse. This worked well with 14.04, but doesn't work with 15.10 and 16.04. Since the mousepad is rather sensible, it makes using the notebook under Ubuntu rather difficult. Cursor quite often jumpst to arbitrary location while typing text. regards ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 3196 F pulseaudio CurrentDesktop: LXDE Date: Sun Apr 10 10:55:52 2016 HibernationDevice: RESUME=/dev/mapper/sda2_crypt MachineType: ASUSTeK Computer Inc. K73SV ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=UUID=3e286927-f1b6-4954-8b0d-7cf23484309f ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-06 (4 days ago) dmi.bios.date: 07/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K73SV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K73SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK73SV.207:bd07/01/2011:svnASUSTeKComputerInc.:pnK73SV:pvr1.0:rvnASUSTeKComputerInc.:rnK73SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K73SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1568466 Title: BIOS function to disable touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have an ASUS notebook with - like virtually all notebooks - a touchpad in front, which generates bogus mouse input when using the keyboard due to hand movements. Therefore the notebook has - like most notebooks - a special function (press Fn + blue symbols on keys) to disable the touchpad when using an external mouse. This worked well with 14.04, but doesn't work with 15.10 and 16.04. Since the mousepad is rather sensible, it makes using the notebook under Ubuntu rather difficult. Cursor quite often jumpst to arbitrary location while typing text. regards ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 3196 F pulseaudio CurrentDesktop: LXDE Date: Sun Apr 10 10:55:52 2016 HibernationDevice: RESUME=/dev/mapper/sda2_crypt MachineType: ASUSTeK Computer Inc. K73SV ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic root=UUID=3e286927-f1b6-4954-8b0d-7cf23484309f ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-06 (4 days ago) dmi.bios.date: 07/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K73SV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K73SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK73SV.207:bd07/01/2011:svnASUSTeKComputerInc.:pnK73SV:pvr1.0:rvnASUSTeKComputerInc.:rnK73SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K73SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Un
[Kernel-packages] [Bug 1291042] [NEW] Can't disable touchpad anymore after upgrade to 14.04
Public bug reported: Hi, it's quite annoying if typing on a notebook's keyboard the touchpad is accidently activated and moves the mouse or generates mouse klicks. On both of my notebook computers I could disable this through keyboard shortcuts (Fn+ a blue function key, I guess BIOS-driven). Since upgrading to 14.04 on one of my notebooks this still works, while on the other (ASUS) it does not work anymore. No way to disable the touchpad, causing plenty of typing faults due to a magically moving mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 2782 F pulseaudio CurrentDesktop: XFCE Date: Tue Mar 11 21:39:54 2014 HibernationDevice: RESUME=/dev/mapper/monstrum-swap MachineType: ASUSTeK Computer Inc. K73SV ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic root=UUID=26ca7c1c-5376-45a1-99f1-40a2f4674470 ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K73SV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K73SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK73SV.207:bd07/01/2011:svnASUSTeKComputerInc.:pnK73SV:pvr1.0:rvnASUSTeKComputerInc.:rnK73SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K73SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** 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/1291042 Title: Can't disable touchpad anymore after upgrade to 14.04 Status in “linux” package in Ubuntu: New Bug description: Hi, it's quite annoying if typing on a notebook's keyboard the touchpad is accidently activated and moves the mouse or generates mouse klicks. On both of my notebook computers I could disable this through keyboard shortcuts (Fn+ a blue function key, I guess BIOS-driven). Since upgrading to 14.04 on one of my notebooks this still works, while on the other (ASUS) it does not work anymore. No way to disable the touchpad, causing plenty of typing faults due to a magically moving mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 2782 F pulseaudio CurrentDesktop: XFCE Date: Tue Mar 11 21:39:54 2014 HibernationDevice: RESUME=/dev/mapper/monstrum-swap MachineType: ASUSTeK Computer Inc. K73SV ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic root=UUID=26ca7c1c-5376-45a1-99f1-40a2f4674470 ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K73SV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K73SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK73SV.207:bd07/01/2011:svnASUSTeKComputerInc.:pnK73SV:pvr1.0:rvnASUSTeKComputerInc.:rnK73SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K73SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291042/+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 1291042] Re: Can't disable touchpad anymore after upgrade to 14.04
Yeah, I can test that - but not before saturday/sunday, because I'll be away from home til friday late, and won't take that particular machine with me. -- 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/1291042 Title: Can't disable touchpad anymore after upgrade to 14.04 Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, it's quite annoying if typing on a notebook's keyboard the touchpad is accidently activated and moves the mouse or generates mouse klicks. On both of my notebook computers I could disable this through keyboard shortcuts (Fn+ a blue function key, I guess BIOS-driven). Since upgrading to 14.04 on one of my notebooks this still works, while on the other (ASUS) it does not work anymore. No way to disable the touchpad, causing plenty of typing faults due to a magically moving mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-16-generic 3.13.0-16.36 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 2782 F pulseaudio CurrentDesktop: XFCE Date: Tue Mar 11 21:39:54 2014 HibernationDevice: RESUME=/dev/mapper/monstrum-swap MachineType: ASUSTeK Computer Inc. K73SV ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-16-generic root=UUID=26ca7c1c-5376-45a1-99f1-40a2f4674470 ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-16-generic N/A linux-backports-modules-3.13.0-16-generic N/A linux-firmware 1.126 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K73SV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K73SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK73SV.207:bd07/01/2011:svnASUSTeKComputerInc.:pnK73SV:pvr1.0:rvnASUSTeKComputerInc.:rnK73SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K73SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291042/+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 1245052] Re: Ubuntu 13.10 netboot code freezes
apport information ** Tags added: apport-collected ** Description changed: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt- del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: lightdm1859 F pulseaudio + /dev/snd/controlC0: lightdm1859 F pulseaudio + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 + InstallationDate: Installed on 2013-10-26 (139 days ago) + InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) + MachineType: FOXCONN NT-A2400&NT-A3500 + MarkForUpload: True + NonfreeKernelModules: fglrx + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.11.0-15-generic N/A + linux-backports-modules-3.11.0-15-generic N/A + linux-firmware 1.116 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: saucy + Uname: Linux 3.11.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + dmi.bios.date: 12/16/2011 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4.6.4 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: NT-A2400&NT-A3500 + dmi.board.vendor: FOXCONN + dmi.board.version: FAB 2.0 + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 4 + dmi.chassis.vendor: FOXCONN + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: + dmi.product.name: NT-A2400&NT-A3500 + dmi.product.version: FAB 2.0 + dmi.sys.vendor: FOXCONN ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026079/+files/AlsaInfo.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon runn
[Kernel-packages] [Bug 1245052] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026091/+files/UdevLog.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026081/+files/CRDA.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026085/+files/Lsusb.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026087/+files/ProcEnviron.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026080/+files/BootDmesg.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026092/+files/WifiSyslog.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026084/+files/Lspci.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026083/+files/IwConfig.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026082/+files/CurrentDmesg.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026089/+files/ProcModules.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026088/+files/ProcInterrupts.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026090/+files/UdevDb.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 1245052] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1245052/+attachment/4026086/+files/ProcCpuinfo.txt -- 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/1245052 Title: Ubuntu 13.10 netboot code freezes Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I have installed the Ubuntu 13.10 netboot code on my pxe server and just tested it. It worked correctly to install ubuntu on an old, intel based notebook. But on my Foxconn NT-A3500 Mini-PC (AMD E350 CPU) it freezes immediately after showing the first selection menu (which language to use for installation), i.e. keyboard does not work anymore, not even ctrl-alt-del. Needs poweroff to reboot. The problem occurs both with the 386 and amd64 code. I have also installed the old 12.04 netboot, which works properly on that device. BTW, the device ran 12.04 for a long time properly, and even 13.10 works if booted from a USB pendrive. The PC properly runs Ubuntu, both 12.04 and 13.10. So something's wrong with the 13.10 netboot code. regards --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1859 F pulseaudio /dev/snd/controlC0: lightdm1859 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=22e01bb0-6b28-4191-958f-dc414180b7b9 InstallationDate: Installed on 2013-10-26 (139 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: FOXCONN NT-A2400&NT-A3500 MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=67f09122-5f80-4f74-8386-30db9fac2aca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/16/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB2.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB2.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 2.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245052/+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 429044] Re: USB barcode scanner (emulating keyboard) crashes with current kernel
I apologize, but I currently have no ubuntu later than 12.04 LTS for several reasons. However, as far as I used the device, it seems to work well current 12.04 LTS. regards -- 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/429044 Title: USB barcode scanner (emulating keyboard) crashes with current kernel Status in The Linux Kernel: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I just experienced a problem that seems to be related to the kernel's HID driver. I have a USB barcode reader that I sometimes use to read the ISBN of books of my library. That barcode reader emulates a keyboard. If you scan a barcode, it just appears as if you had entered the encoded number on a keyboard, so it does not require a special driver. I used that scanner last spring (not sure whether this was ubuntu 08.04 or 08.10) for the last time, where it worked pretty well. Now I tried to use it again (checked with two ubuntu machines) but it does not work anymore. When plugging in, the LEDs are lit, but the beeper gives an unusual sound. When trying to scan, it scans once, but nothing appears on the console, and then the scanner is dead (until pulling it from USB to cut it from power supply). The scanner itself is ok, it still works under windows on the same machine, although it requires a reset to factory defaults after having it tried with Linux. I guess that the current kernel tries to perform some configuration or any other special things with USB keyboards, that is not compatible with the 'keyboard type' USB scanner. dmesg when plugging it in: [34828.208582] usb 6-3: new low speed USB device using ohci_hcd and address 7 [34828.374898] usb 6-3: configuration #1 chosen from 1 choice lsusb: Bus 006 Device 007: ID 1130:0001 Tenx Technology, Inc. Probably it is the bug described under https://lists.linux-foundation.org/pipermail/bugme-new/2009-May/021980.html regards To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/429044/+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 1503695] Re: nft nat not working
BTW., I've noticed that the nf tables defined in /etc/nftables.conf are
not loaded at all by boot/systemd, manual loading is needed.
systemctl status nftables says
# systemctl status nftables
● nftables.service - nftables
Loaded: loaded (/lib/systemd/system/nftables.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
Docs: man:nft(8)
http://wiki.nftables.org
It's disabled.
So a central question is:
What is the default firewall system of ubuntu 15.10: iptables or
nftables?
--
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/1503695
Title:
nft nat not working
Status in linux package in Ubuntu:
Confirmed
Status in nftables package in Ubuntu:
New
Bug description:
Hi ,
I have installed an ubuntu 15.10 beta machine and configured nftables
firewalling.
While the regular firewalling works (using the default settings that
come with the package), I found that nat rules are silently ignored.
I've added this to the /etc/nftables.conf and read it:
table ip nat {
chain prerouting {
type nat hook prerouting priority 0;
ip daddr 1.2.3.4 tcp dport 80 redirect to 1234
tcp dport 80 redirect to 1235
}
chain postrouting {
type nat hook postrouting priority 0;
}
}
following the example from
http://wiki.nftables.org/wiki-
nftables/index.php/Performing_Network_Address_Translation_%28NAT%29#Redirect
(1.2.3.4 is just a placeholder for the address actually used here, i
do not want to reveal the address to the bug report). nft reads this
without complaining, and
nft list table ip nat
gives exactly that output (except for replacing 80 with "http"), so
the configuration is read correctly.
But it simply does not work. Without having any daemon listening on
ports 1234, 1235 , traffic to port 80 works as usual. As long as there
is not process waiting on 1234/1235, connection should be refused.
Which is dangerous and a security flaw, since this was meant (and used
in a similar way with iptables and Ubuntu 14.04) to avoid revealing
sensitive data over the internet (an application that is not able to
use https should be tunneled). When firewall rules have been loaded
and accepted without any warning, one would expect them to run.
Ive tried to unload all iptables-related kernel packages and to load
packages like nft_nat, nft_redir, nft_redir_ipv4, but the direct
connection to port 80 still works although it shouldn't.
No error warning, no message. It just allows outgoing port 80 although
it shouldn't.
Which is a problem, since this is security-relevant. If it doesn't
work, it should spit out some error message.
(FYI: It was implemented under Ubuntu 14.04 with
iptables -t nat -I OUTPUT -d 1.2.3.4 -p tcp --dport 80 -j REDIRECT --to-port
1234
)
My current guess: On that wiki page's bottem there's a hint that iptables and
nft nat cannot be used at the same time. Unfortunately Ubuntu 15.10 still loads
plenty of iptables stuff. Although I've tried to remove it all and it's kernel
modules, I guess this could be a problem.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nftables 0.4-7
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Oct 7 15:21:36 2015
InstallationDate: Installed on 2015-09-03 (33 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
SourcePackage: nftables
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503695/+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 1503695] Re: nft nat not working
I've received a message asking me to either do apport-collect or add a
statement that I would not wish to upload confidential data. The latter
is the case, I cannot reveal details.
** 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/1503695
Title:
nft nat not working
Status in linux package in Ubuntu:
Confirmed
Status in nftables package in Ubuntu:
New
Bug description:
Hi ,
I have installed an ubuntu 15.10 beta machine and configured nftables
firewalling.
While the regular firewalling works (using the default settings that
come with the package), I found that nat rules are silently ignored.
I've added this to the /etc/nftables.conf and read it:
table ip nat {
chain prerouting {
type nat hook prerouting priority 0;
ip daddr 1.2.3.4 tcp dport 80 redirect to 1234
tcp dport 80 redirect to 1235
}
chain postrouting {
type nat hook postrouting priority 0;
}
}
following the example from
http://wiki.nftables.org/wiki-
nftables/index.php/Performing_Network_Address_Translation_%28NAT%29#Redirect
(1.2.3.4 is just a placeholder for the address actually used here, i
do not want to reveal the address to the bug report). nft reads this
without complaining, and
nft list table ip nat
gives exactly that output (except for replacing 80 with "http"), so
the configuration is read correctly.
But it simply does not work. Without having any daemon listening on
ports 1234, 1235 , traffic to port 80 works as usual. As long as there
is not process waiting on 1234/1235, connection should be refused.
Which is dangerous and a security flaw, since this was meant (and used
in a similar way with iptables and Ubuntu 14.04) to avoid revealing
sensitive data over the internet (an application that is not able to
use https should be tunneled). When firewall rules have been loaded
and accepted without any warning, one would expect them to run.
Ive tried to unload all iptables-related kernel packages and to load
packages like nft_nat, nft_redir, nft_redir_ipv4, but the direct
connection to port 80 still works although it shouldn't.
No error warning, no message. It just allows outgoing port 80 although
it shouldn't.
Which is a problem, since this is security-relevant. If it doesn't
work, it should spit out some error message.
(FYI: It was implemented under Ubuntu 14.04 with
iptables -t nat -I OUTPUT -d 1.2.3.4 -p tcp --dport 80 -j REDIRECT --to-port
1234
)
My current guess: On that wiki page's bottem there's a hint that iptables and
nft nat cannot be used at the same time. Unfortunately Ubuntu 15.10 still loads
plenty of iptables stuff. Although I've tried to remove it all and it's kernel
modules, I guess this could be a problem.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nftables 0.4-7
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Oct 7 15:21:36 2015
InstallationDate: Installed on 2015-09-03 (33 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
SourcePackage: nftables
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503695/+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 1503590] Re: Trouble with DisplayPort
> Hadmut Danisch, why do you read half of the instructions before following them? ;) Because I follow instruction in order, and because it wasn't obvious that these were two instructions, because one explicitely stated and outstanding, the other hidden in the text. That's what we call misleading (and such wasting other people's time). I've tested yesterday's kernel 4.3.0-040300rc6-generic #201510182030 SMP which works as normal, no installation problems, but the DisplayPort- problem still exists: Boot code and boot splash are shown on DisplayPort, but as soon as X11 takes control, screen becomes black. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.3-rc6 -- 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/1503590 Title: Trouble with DisplayPort Status in linux package in Ubuntu: Incomplete Bug description: I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This device has three display connectors, 1x DisplayPort, 2xHDMI. I'm having a Display with 2560x1600, and thus want to use with with DisplayPort for full resolution. When connecting screen and PC with DisplayPort, both the BIOS and the Linux BootSplash/Console correctly recognize the screen to be connected to DisplayPort and are displayed as usual. But as soon as X starts, screen becomes black (and the screen itself somewhat confused, because it does not even respond to the menu button anymore). Interestingly, the same screen worked properly when connected with DisplayPort to another Linux machine with 14.04. Connecting the screen with HDMI instead works without any problems, but gives a reduced resolution of 1920x1080 only. --- ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:22b1] InstallationDate: Installed on 2015-09-03 (45 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) LightdmGreeterLog: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process (1991) killed by TERM signal LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1537) killed by TERM signal Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Tags: wily ubuntu UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo video www-data _MarkForUpload: True dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: N3150-NUC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. 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.:bvrP1.10:bd07/16/2015:
[Kernel-packages] [Bug 2001924] [NEW] Sudden crashes on Ryzen 7/AMD (Gigabyte GB-BER7(HS)-5700)
Public bug reported: Hi, I'm having a brand new GB-BER7(HS)-5700, recently installed with Xubuntu, and around every other day it crashes: Suddenly Screen is black and machine rebooting, no log, no hint, no information, nothing. No chance to debug or read a kernel log. Sudden death of kernel. I, however, noticed, that this does not seem to happen as long as I am just working in a shell. I believe, to the best I can recall, that it always happened when I started to play a video or scroll a browser window, so my guess is that it is somewhat related to the graphics. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hadmut 3228 F pulseaudio /dev/snd/controlC0: hadmut 3228 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jan 5 13:49:28 2023 InstallationDate: Installed on 2022-12-25 (10 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: GIGABYTE GB-BER7(HS)-5700 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F09 dmi.board.asset.tag: Default string dmi.board.name: GB-BER7(HS)-5700 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF09:bd03/08/2022:br5.19:svnGIGABYTE:pnGB-BER7(HS)-5700:pvr1.x:rvnGIGABYTE:rnGB-BER7(HS)-5700:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:sku01: dmi.product.family: BRIX dmi.product.name: GB-BER7(HS)-5700 dmi.product.sku: 01 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2001924 Title: Sudden crashes on Ryzen 7/AMD (Gigabyte GB-BER7(HS)-5700) Status in linux package in Ubuntu: New Bug description: Hi, I'm having a brand new GB-BER7(HS)-5700, recently installed with Xubuntu, and around every other day it crashes: Suddenly Screen is black and machine rebooting, no log, no hint, no information, nothing. No chance to debug or read a kernel log. Sudden death of kernel. I, however, noticed, that this does not seem to happen as long as I am just working in a shell. I believe, to the best I can recall, that it always happened when I started to play a video or scroll a browser window, so my guess is that it is somewhat related to the graphics. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hadmut 3228 F pulseaudio /dev/snd/controlC0: hadmut 3228 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jan 5 13:49:28 2023 InstallationDate: Installed on 2022-12-25 (10 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: GIGABYTE GB-BER7(HS)-5700 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F09 dmi.board.asset.tag: Default string dmi.board.name: GB-BER7(HS)-5700 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string
[Kernel-packages] [Bug 1947498] [NEW] zfs/zpool encryption crash on server 21.10
Public bug reported: Hi, just installed a new HPE microserver with SSD and four harddisks with new 21.10 server and tried to create a zpool with zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O encryption=on -O keyformat=passphrase which reproducably crashed twice with the attached kernel message. The zpool then exists, but is not encrypted. zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd without the option works and a subsequent zfs create pool1/sub -o encryption=on -o keyformat=passphrase works as well. Which is, however, not a real workaround for a fully encrypted pool (which worked under 20.04). regards ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 17 12:44:15 2021 InstallationDate: Installed on 2021-10-17 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish uec-images ** Attachment added: "dmesg output of kernel crash" https://bugs.launchpad.net/bugs/1947498/+attachment/5533647/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1947498 Title: zfs/zpool encryption crash on server 21.10 Status in zfs-linux package in Ubuntu: New Bug description: Hi, just installed a new HPE microserver with SSD and four harddisks with new 21.10 server and tried to create a zpool with zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O encryption=on -O keyformat=passphrase which reproducably crashed twice with the attached kernel message. The zpool then exists, but is not encrypted. zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd without the option works and a subsequent zfs create pool1/sub -o encryption=on -o keyformat=passphrase works as well. Which is, however, not a real workaround for a fully encrypted pool (which worked under 20.04). regards ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 17 12:44:15 2021 InstallationDate: Installed on 2021-10-17 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947498/+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 1947498] Re: zfs/zpool encryption crash on server 21.10
There's more trouble. I just copied several TB of data by zfs send | zfs recv from a 20.04 machine to this new machine. Worked well for hours, but at the end some crash messages, see attached second dmesg. ZFS as it comes with 21.10 is definitely not production ready. ** Attachment added: "dmesg output of kernel problems" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947498/+attachment/5534455/+files/dmesg2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1947498 Title: zfs/zpool encryption crash on server 21.10 Status in zfs-linux package in Ubuntu: New Bug description: Hi, just installed a new HPE microserver with SSD and four harddisks with new 21.10 server and tried to create a zpool with zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O encryption=on -O keyformat=passphrase which reproducably crashed twice with the attached kernel message. The zpool then exists, but is not encrypted. zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd without the option works and a subsequent zfs create pool1/sub -o encryption=on -o keyformat=passphrase works as well. Which is, however, not a real workaround for a fully encrypted pool (which worked under 20.04). regards ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 17 12:44:15 2021 InstallationDate: Installed on 2021-10-17 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947498/+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 1947498] Re: zfs/zpool encryption crash on server 21.10
Even more trouble: The machine, although freshly installed, can't even properly mount the filesystems received by zfs send|zfs receive from a 20.04 machine, and hangs in shutdown, does not even turn itself off. Several PANICs. ZFS for 21.10 is really broken. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1947498 Title: zfs/zpool encryption crash on server 21.10 Status in zfs-linux package in Ubuntu: New Bug description: Hi, just installed a new HPE microserver with SSD and four harddisks with new 21.10 server and tried to create a zpool with zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd -O encryption=on -O keyformat=passphrase which reproducably crashed twice with the attached kernel message. The zpool then exists, but is not encrypted. zpool create pool1 raidz2 /dev/sda /dev/sdb /dev/sdc /dev/sdd without the option works and a subsequent zfs create pool1/sub -o encryption=on -o keyformat=passphrase works as well. Which is, however, not a real workaround for a fully encrypted pool (which worked under 20.04). regards ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 17 12:44:15 2021 InstallationDate: Installed on 2021-10-17 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947498/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
5.15.0-39-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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
vmlinuz-5.15.0-43-generic still has the issue. -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
** Attachment added: "dmesg 5.15.0-39" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+attachment/5606282/+files/dmesg_5.15.0-39-generic.txt -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
** Attachment added: "dmesg 5.15.0-40" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+attachment/5606283/+files/dmesg_5.15.0-40-generic.txt -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
Oh ... YES. :-) At least at the relevant parts. - X11 good with -40 and -43 :-) - boot time text console good - but console after X11 (when shutting down) still shows some jumping effect - even after removing the nosplash option, I still get the text console instead of graphical splash at boot time -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
Comment #23 indeed helped. Sorry for the delay, I was away from home. Not sure yet, which of the options is the one that actually helps. thanks! -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 2004470] [NEW] macvlan network mode setting probably broken
Public bug reported: Hi, using Ubuntu 22.04, Kernel 5.15.0-58-generic, LXD 5.10-b392610, iproute2 5.15.0-1ubuntu2 I ran into the problem that a virtual LXD container with an macvlan network interface mapped to the hosts ethernet adapter works as expected with all other machines in the LAN, including getting an IP address assigned by the DHCP server. But it cannot be reached from the HOST machine itself. My first guess was that LXD does not set the macvlan into bridge mode, but leaves it in the default private mode, which would explain the problem. But LXD's source code showed that it sets the mode to bridge and uses iproute2's ip program to set the interface. I therefore tried commands like ip link add name blubb address 02:4e:a6:27:01:07 link enp4s0 type macvlan mode bridge ip link add link enp4s0 name sugar type macvlan mode bridge which succeed without error message. But ip link show reports 9: blubb@enp4s0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 02:4e:a6:27:01:07 brd ff:ff:ff:ff:ff:ff 10: sugar@enp4s0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 26:99:d1:52:ba:e0 brd ff:ff:ff:ff:ff:ff in both cases "mode DEFAULT", where I would expect „bridge“. Same with the interface assigned to the LXD virtual container. Shouldn't this show the mode used in the ip link add command instead of DEFAULT? - I reported the problem to the iproute2 maintainer, but he told me to report to net...@vger.kernel.org - on net...@vger.kernel.org I did not get a response - Kernel.org bugzilla tells to report problems not to kernel.org, but to the distributions bug system regards ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 3252 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Feb 1 11:57:58 2023 InstallationDate: Installed on 2020-06-12 (963 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Medion G24 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=e1e9c4ee-42ab-4be4-9160-7d4d0e23f95c ro quiet cryptdevice=UUID=66118fb4-e7e6-4516-872a-67d93f44b554:luks-66118fb4-e7e6-4516-872a-67d93f44b554 root=/dev/mapper/luks-66118fb4-e7e6-4516-872a-67d93f44b554 resume=/dev/mapper/luks-66118fb4-e7e6-4516-872a-67d93f44b554 splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-28 (248 days ago) dmi.bios.date: 10/12/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:br4.6:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Medion ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2004470 Title: macvlan network mode setting probably broken Status in linux package in Ubuntu: New Bug description: Hi, using Ubuntu 22.04, Kernel 5.15.0-58-generic, LXD 5.10-b392610, iproute2 5.15.0-1ubuntu2 I ran into the problem that a virtual LXD container with an macvlan network interface mapped to the hosts ethernet adapter works as expected with all other machines in the LAN, including getting an IP address assigned by the DHCP server. But it cannot be reached from the HOST machine itself. My first guess was that LXD does not set the macvlan into bridge mode, but leaves it in the default private mode, which would explain the problem. But LXD's source code showed that it sets the mode to bridge and uses iproute2's ip program to set the interface. I therefore tried commands like ip link add name blubb address 02:4e:a6:27:01:07 link enp4s0 type macvlan mode bridge ip link add link enp4s0 name su
[Kernel-packages] [Bug 2033974] [NEW] linux-image-kvm lacks nfsd module
Public bug reported: Hi, (this is a bug report against package linux-image-5.15.0-1040-kvm, but launchpad requires to file bugs against source packages, not binaries.) I was just debugging an application that ran on a local test machine but not on the cloud, and stumbled upon the fact that the linux-image-kvm series lacks the nfsd module. It even lets you install the nfs packages and daemons without further warnings, no package collisions, it then just silently doesn't work. Nasty thing, definitely not reliable. Package dependencies and collisions should avoid that. Nasty trap. I found some discussions in forums from angry users, but no explanation why the kvm/cloud kernel series do lack the nfs support. I was under the impression that the lean cloud kernel series has been stripped from all the hardware support, since it is intended to run on virtualized hardware only and boot faster, but wasn't supposed to be reduced in functionality. And it still does make sense to have a cloud machine export some file systems to other cloud machines through NFS (what else could they use in a multiuser environment?) And since it is a module and not part of the kernel file itself, it wouldn't increase the kernel size if not loaded. So has this been dropped accidently, or is there a good, but widely unknown reason to dismiss NFS from cloud kernels (and use whatever else instead)? regards ** Affects: linux-signed-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2033974 Title: linux-image-kvm lacks nfsd module Status in linux-signed-kvm package in Ubuntu: New Bug description: Hi, (this is a bug report against package linux-image-5.15.0-1040-kvm, but launchpad requires to file bugs against source packages, not binaries.) I was just debugging an application that ran on a local test machine but not on the cloud, and stumbled upon the fact that the linux-image-kvm series lacks the nfsd module. It even lets you install the nfs packages and daemons without further warnings, no package collisions, it then just silently doesn't work. Nasty thing, definitely not reliable. Package dependencies and collisions should avoid that. Nasty trap. I found some discussions in forums from angry users, but no explanation why the kvm/cloud kernel series do lack the nfs support. I was under the impression that the lean cloud kernel series has been stripped from all the hardware support, since it is intended to run on virtualized hardware only and boot faster, but wasn't supposed to be reduced in functionality. And it still does make sense to have a cloud machine export some file systems to other cloud machines through NFS (what else could they use in a multiuser environment?) And since it is a module and not part of the kernel file itself, it wouldn't increase the kernel size if not loaded. So has this been dropped accidently, or is there a good, but widely unknown reason to dismiss NFS from cloud kernels (and use whatever else instead)? regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-kvm/+bug/2033974/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
Interesting effect: When the distortion is shown and I do plugin a second screen, then both screens are working well. Obviously, some sort of reconfiguration happens. -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
Unforunately, this did not fully fix the problem. Although the screen appears stable (unless shutting down), every now and then (around evern 20 Minutes) the screen shows a jerk. -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] [NEW] Latest kernel breaks LCD screen
Public bug reported: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1982479 Title: Latest kernel breaks LCD screen Status in linux package in Ubuntu: New Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do
[Kernel-packages] [Bug 1982479] Re: Latest kernel breaks LCD screen
Is there instructions how to install older than recent kernel images? -- 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/1982479 Title: Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: Latest kernel breaks LCD screen
I'm still looking for a method to test different build versions of kernels. I tried that mainline tool described here https://davejansen.com/install-a-linux-kernel-of-choice-under-ubuntu/ but that offers only different Linux versions (i.e. those who differ in the first three numbers like 5.15.0 and 5.15.1, but not in the ubuntu build number such as 5.15.0-25 and 5.15.0-41. I am willing to do debugging for you, but you need to hint me about how to get these versions. -- 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/1982479 Title: Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: Latest kernel breaks LCD screen
OK, got it. I wasn't aware that the older versions are still in the regular linux repository with different version numbers. -- 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/1982479 Title: Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: Latest kernel breaks LCD screen
5.15.0-25 good 5.15.0-41 bad and all available versions between hanging at boot time, not enabling the network. Last message on console for these versions is [ OK ] Finished Record Runlevel Change in UTMP. no visible error message, but I can login on console 1. I need to figure out why these versions are hanging. -- 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/1982479 Title: Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: Latest kernel breaks LCD screen
Boot with versions betwenn 25 and 41 is not hanging, it is the sddm (and thus X11) that is not running for yet unknown reasons, and thus the NetworkManager is not getting active. What did you change betwenn 25 and 33 and between 40 and 41? -- 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/1982479 Title: Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: Latest kernel breaks LCD screen
OK, I got further. The distortion depends on the presence of the linux-modules-extra-5.15.0-*-generic package. I first did omit these extra modules and found a completely different behaviour without. With linux-modules-extra-5.15.0-*-generic: Kernels up to including 5.15.0-39-generic are fine. The bug came in with 5.15.0-40-generic Without linux-modules-extra-5.15.0-*-generic: System can't active ethernet and sddm hangs for unknown reasons when booting normally. But when booting into maintenance mode in grub, and just activating the "networking" (although it can't activate ethernet without the module), the system then comes up into a stable and normal X11 session, just the mouse pad not working (missing module) even with the 5.15.0-40-generic kernel! So it must be - something that came in with the -40 version - probably something that is in the linux-modules-extra package and not the linux-image or the linux-modules package. -- 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/1982479 Title: Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+subscriptions -
[Kernel-packages] [Bug 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
I just verified: 5.15.0-40-generic definitely shows the symptoms. -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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
