[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
fred@z690-jammy:~$ sudo dmesg | grep mtd [sudo] password for fred: [2.761808] systemd[1]: Starting Load Kernel Module mtdpstore... [2.769635] mtd device must be supplied (device name is empty) running Jammy 22.04 on z690 system. system does boot after error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Confirmed Bug description: After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895490] Re: no destination host name is cups-browsed running
Same error. But changed printer from default to one with .local at end of name then worked. Not sure why hpcups 3.20.3 printer and driverless cups-filter 1.27.4 printer are also configured but do not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1895490 Title: no destination host name is cups-browsed running Status in cups package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 cups-browsed: Installed: 1.27.4-1 cups: Installed: 2.3.1-9ubuntu1.1 I expect to be able to print on my Brother HL-L2350DW printer. I have no problem printing to that printer via Windows 10. I also got this error on Kubuntu 20.04. What happened instead? I cannot get my pdf to print. Instead I get an error that says 'No destination host name supplied by cups-browsed for printer "Brother_HL_L2350DW_series", is cups-browsed running?'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 13 20:30:40 2020 InstallationDate: Installed on 2020-08-16 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Brother_HL_L2350DW_series: implicitclass://Brother_HL_L2350DW_series/ MachineType: LENOVO 20AN00DEUS Papersize: letter PpdFiles: Brother_HL_L2350DW_series: Brother HL-L2350DW series, driverless, cups-filters 1.27.4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=d3493ccb-75ba-4bb9-851d-b3fc4c5adb8f ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GLET96WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00DEUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET96WW(2.50):bd06/20/2018:svnLENOVO:pn20AN00DEUS:pvrThinkPadT440p:rvnLENOVO:rn20AN00DEUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00DEUS dmi.product.sku: LENOVO_MT_20AN_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764860] Re: dbus crashed with SIGABRT in _dbus_abort()
Just had this error in 20.04. But may be related to this already reported: [Bug 1866838] [NEW] ippusbxd crashed with SIGSEGV in usb_conn_acquire() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1764860 Title: dbus crashed with SIGABRT in _dbus_abort() Status in cups package in Ubuntu: Confirmed Bug description: bionic beaver @ dell xps12 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Mon Apr 16 20:42:40 2018 ExecutablePath: /usr/lib/cups/notifier/dbus InstallationDate: Installed on 2018-03-11 (37 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lpstat: device for HP_LaserJet_500_color_M551_2F183C_: ipp://BKPRT777.local:631/ipp/print device for HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: ipps://BKPRT777.local:443/ipp/print device for Lexmark-W820-Bravo: socket://10.42.9.152:9100 MachineType: Dell Inc. XPS 12 9Q23 Papersize: letter PpdFiles: Lexmark-W820-Bravo: Lexmark W820 PS HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: HP LaserJet 500 color M551, driverless, cups-filters 1.20.2 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct i8042.dumbkbd vt.handoff=1 ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct i8042.dumbkbd vt.handoff=1 Signal: 6 SourcePackage: cups StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () __libc_start_main (main=0x55f0c84c81b0, argc=3, argv=0x7ffcaf592438, init=, fini=, rtld_fini=, stack_end=0x7ffcaf592428) at ../csu/libc-start.c:310 Title: dbus crashed with SIGABRT in _dbus_abort() UpgradeStatus: Upgraded to bionic on 2018-03-11 (37 days ago) UserGroups: dmi.bios.date: 12/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.asset.tag: 0004061282 dmi.board.name: 0520M8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 0004061282 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/07/2012:svnDellInc.:pnXPS129Q23:pvrA05:rvnDellInc.:rn0520M8:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.family: 103C_5335KV dmi.product.name: XPS 12 9Q23 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1764860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849534] [NEW] ISO extracted to FAT32 does not support links error
Public bug reported: Attempting to extract ISO to FAT32 partition for UEFI install which used to work. But get error that FAT32 does not support links. Found these links: fred@Bionic-Z170N:/media/fred/Ubuntu 20.04 LTS amd64$ find . -type l -ls 2761 0 lr-xr-xr-x 1 fred fred5 Oct 18 20:36 ./dists/stable -> focal 2765 0 lr-xr-xr-x 1 fred fred5 Oct 18 20:36 ./dists/unstable -> focal 1330 0 lr-xr-xr-x 1 fred fred1 Oct 18 20:36 ./ubuntu -> . ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1849534 Title: ISO extracted to FAT32 does not support links error Status in ubuntu-meta package in Ubuntu: New Bug description: Attempting to extract ISO to FAT32 partition for UEFI install which used to work. But get error that FAT32 does not support links. Found these links: fred@Bionic-Z170N:/media/fred/Ubuntu 20.04 LTS amd64$ find . -type l -ls 2761 0 lr-xr-xr-x 1 fred fred5 Oct 18 20:36 ./dists/stable -> focal 2765 0 lr-xr-xr-x 1 fred fred5 Oct 18 20:36 ./dists/unstable -> focal 1330 0 lr-xr-xr-x 1 fred fred1 Oct 18 20:36 ./ubuntu -> . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1849534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist
At this point better to start a thread on Ubuntu forums. https://ubuntuforums.org/forumdisplay.php?f=339 Already many similar questions and answers. Also from live installer: Please copy & paste link to the Boot-info summary report ( do not post report), the auto fix sometimes can create more issues. https://help.ubuntu.com/community/Boot-Repair -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1675079 Title: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in update-manager source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-manager source package in Artful: Fix Released Bug description: [Impact] * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. [Test Case] 1. Install kernel packages to be removed, mark them auto-installed and run apt's kernel hook script to make apt consider them autoremovable: sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo /etc/kernel/postinst.d/apt-auto-removal 2. Also downgrade a package to be upgraded: sudo apt-get install -y --allow-downgrades ca- certificates=20160104ubuntu1 3. (update-manager). Run update-manager and observe that kernel packages are offered for removal in Details of updates. sudo update-manager 4. (update-manager) Click on Install Now and observe that the kernel packages are removed. 3. (unattended-upgrades) Run unattended-upgrades manually and observe the removal of the autoremovable kernel packages: sudo unattended-upgrade -v [Regression Potential] The change may cause update-manager or unattanded-upgrades to remove used kernel packages or fail to install other package updates. [Other Info] The unattended-upgrades fix is uploaded with many other fixes and those may cause regressions in other areas in unattended-upgrades. [Original bug text] On a 16.04LTS system, the /boot partition will eventually fill with Kernel images, until the point where "apt-get autoremove" can't complete. This issue has previously been reported as fixed, but it is not fixed: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093 Generally what I see is the final kernel image that fills the drive is incompletely installed (the header package does not make it). "apt- get autoremove" tries to work, but fails. I must manually remove kernel images to free enough space. I see this on a machine used by my elderly parents, where 'Download and install updates automatically' is set. And on my home machines, where the setting is elsewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
