[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
Same message as "oldfred", but using Ubuntu Kinetic Kudu (development branch) -- 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 1835660] Re: initramfs unpacking failed
The corrected ISO date is this: hirsute-desktop-amd64.iso 2021-01-26 05:51 from Kubuntu daily-live current. It still fails. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1835660] Re: initramfs unpacking failed
This bug is still failing per current ISO dated 01/25/2021 booting from Kubuntu 21.04: $ sudo dmesg|grep failed [0.538632] Initramfs unpacking failed: Decoding failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1835660] Re: initramfs unpacking failed
This bug failure is still present as of current ISO dated 01/25/2021 using Kubuntu: [code]vmc@01-25-21:~$ sudo dmesg|grep failed [0.538632] Initramfs unpacking failed: Decoding failed[/code] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
I found this that removing the file in "/var/crash/", stopped systemd- journal from filling up. Now systemd process is normal after a reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1895573 Title: systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Confirmed Bug description: htop always shows 100% CPU for /sbin/init/splash When I look the journalctl, I have always seen `systemd[1]: Failed to start Process error reports when automatic reporting is enabled.` thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895573/+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 1895573] Re: systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
I'm getting the same error. Systemd-journal is filling up to over a gig of useless data. Just reports: "Sep 18 15:27:51 vmc-TC-885 systemd[1]: Failed to start Process error reports when automatic reporting is enabled." -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1895573 Title: systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Confirmed Bug description: htop always shows 100% CPU for /sbin/init/splash When I look the journalctl, I have always seen `systemd[1]: Failed to start Process error reports when automatic reporting is enabled.` thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895573/+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 1835660] Re: initramfs unpacking failed
Ye, I tried X,K,U,b ubuntu, and all boot without errors. I also prefer gzip. I had the reverse though. I find gzip is faster than lz4, and I'm using nvme for boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1835660] Re: initramfs unpacking failed
In post#14, I showed how my gzip booted faster. "We currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system." If 'harmless', then why the error in the first place? Something is causing it. Sticking the error in the sand is NOT the answer! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1835660] Re: initramfs unpacking failed
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: New Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1784198] Re: lubuntu bash preferences too big
It should be qterminal 0.9.0 and NOT bash ** Package changed: bash (Ubuntu) => qterminal (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1784198 Title: lubuntu bash preferences too big Status in qterminal package in Ubuntu: New Bug description: lubuntu 18.10 LXQt version 0.13.0 When I open bash and select Preferences. The Terminal Settings is much taller than the screen size. I can't see the OK-Cancel-Apply buttons. I need to use the mouse from the top of screen and reduce the size manually. I expect the settings size to be within the parameters so the bottom of the settings screen show. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1784198/+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 1784198] Re: lubuntu bash preferences too big
** Attachment added: "settings.png" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1784198/+attachment/5169115/+files/settings.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1784198 Title: lubuntu bash preferences too big Status in bash package in Ubuntu: New Bug description: lubuntu 18.10 LXQt version 0.13.0 When I open bash and select Preferences. The Terminal Settings is much taller than the screen size. I can't see the OK-Cancel-Apply buttons. I need to use the mouse from the top of screen and reduce the size manually. I expect the settings size to be within the parameters so the bottom of the settings screen show. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1784198/+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 1784198] [NEW] lubuntu bash preferences too big
Public bug reported: lubuntu 18.10 LXQt version 0.13.0 When I open bash and select Preferences. The Terminal Settings is much taller than the screen size. I can't see the OK-Cancel-Apply buttons. I need to use the mouse from the top of screen and reduce the size manually. I expect the settings size to be within the parameters so the bottom of the settings screen show. See attachment. ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Settings size too large" https://bugs.launchpad.net/bugs/1784198/+attachment/5169114/+files/settings.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1784198 Title: lubuntu bash preferences too big Status in bash package in Ubuntu: New Bug description: lubuntu 18.10 LXQt version 0.13.0 When I open bash and select Preferences. The Terminal Settings is much taller than the screen size. I can't see the OK-Cancel-Apply buttons. I need to use the mouse from the top of screen and reduce the size manually. I expect the settings size to be within the parameters so the bottom of the settings screen show. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1784198/+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 1615338] Re: Yakkety fails to start desktop
Fixed on: https://bugs.launchpad.net/bugs/1615341 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1615338 Title: Yakkety fails to start desktop Status in xorg package in Ubuntu: Invalid Bug description: Recent dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system Apport run from Xubuntu installation. Note that booting Xubuntu and Mate to Install options shows ubiquity and allows installation. Tested Ubuntu Gnome, Lubuntu - no issue seen there. For Xubuntu all lead to a black destop For Mate all lead to Mate default wallpaper ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sun Aug 21 07:32:04 2016 InstallationDate: Installed on 2016-08-21 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160821) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615338/+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 1615341] Re: Yakkety desktop fails to start
** Description changed: -- 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/1615341 Title: Yakkety desktop fails to start Status in systemd package in Ubuntu: Fix Released Bug description: Following a set of updates (attached) Saturday 20th I lost a working desktop. Further to that dailies for Xubuntu and Mate both fail to start a working desktop either by: 1 - booting Try option from the first menu 2 - booting Try option from the Try/Install dialogue 3 - logging into installed system For Xubuntu (both locally and in installed daily) Changing the Exec line in /usr/share/xsessions/xubuntu.desktop from Exec=/usr/share/xfce4/scripts/run-systemd-session xubuntu- session.target to Exec=startxfce4 and my normal desktop runs again. (Found all this out after I reported bug 1615338, which I've now marked invalid) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 08:59:13 2016 InstallationDate: Installed on 2016-06-11 (70 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-10-generic root=UUID=246fbeaf-5feb-4078-9c56-10a03b4fafa1 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.systemd.journald.conf: [modified] mtime.conffile..etc.systemd.journald.conf: 2016-07-21T07:46:55.198735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615341/+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 1608988] [NEW] Superblock last mount time is in the future
Public bug reported: xubuntu YAKKETY I live in California and need my time to be set to LOCAL time. When its set, YAKKETY complains "Superblock last mount time is in the future" every time. XENIAL does not complain. tune2fs 1.43.1 (08-Jun-2016) Filesystem volume name: Last mounted on: / Filesystem UUID: d873f8c6-2230-44e6-b865-a0b1c1ef4259 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 4521984 Block count: 18067138 Reserved block count: 903356 Free blocks: 16881867 Free inodes: 4361731 First block: 0 Block size: 4096 Fragment size:4096 Group descriptor size:64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size:16 Filesystem created: Sun Jul 31 21:10:29 2016 Last mount time: Tue Aug 2 07:28:35 2016 Last write time: Tue Aug 2 00:28:33 2016 Mount count: 22 Maximum mount count: -1 Last checked: Sun Jul 31 21:10:31 2016 Check interval: 0 () Lifetime writes: 6354 MB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 32 Desired extra isize: 32 Journal inode:8 First orphan inode: 924487 Default directory hash: half_md4 Directory Hash Seed: d2a27026-ca68-4971-aa6d-964039f8b68b Journal backup: inode blocks Checksum type:crc32c Checksum: 0x13a6f0fa ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1608988 Title: Superblock last mount time is in the future Status in e2fsprogs package in Ubuntu: New Bug description: xubuntu YAKKETY I live in California and need my time to be set to LOCAL time. When its set, YAKKETY complains "Superblock last mount time is in the future" every time. XENIAL does not complain. tune2fs 1.43.1 (08-Jun-2016) Filesystem volume name: Last mounted on: / Filesystem UUID: d873f8c6-2230-44e6-b865-a0b1c1ef4259 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 4521984 Block count: 18067138 Reserved block count: 903356 Free blocks: 16881867 Free inodes: 4361731 First block: 0 Block size: 4096 Fragment size:4096 Group descriptor size:64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size:16 Filesystem created: Sun Jul 31 21:10:29 2016 Last mount time: Tue Aug 2 07:28:35 2016 Last write time: Tue Aug 2 00:28:33 2016 Mount count: 22 Maximum mount count: -1 Last checked: Sun Jul 31 21:10:31 2016 Check interval: 0 () Lifetime writes: 6354 MB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 32 Desired extra isize: 32 Journal inode:8 First orphan inode: 924487 Default directory hash: half_md4 Directory Hash Seed: d2a27026-ca68-4971-aa6d-964039f8b68b Journal backup: inode blocks Checksum type:crc32c Checksum: 0x13a6f0fa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1608988/+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 1484083] Re: Don't work autologin after update lightdm
Using xubuntu-wily removing the line "autologin-session=lightdm- autologin". Now autologin works But, that line is still in xubuntu-trusty and it always worked. ?! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1484083 Title: Don't work autologin after update lightdm Status in One Hundred Papercuts: Confirmed Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Don't work autologin after update lightdm ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.15.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3 Uname: Linux 4.1.0-3-lowlatency x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 12 14:20:00 2015 InstallationDate: Installed on 2015-04-23 (110 days ago) InstallationMedia: SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1484083/+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 1454404] Re: ACPI PCC Probe Failed
I'm seeing this same message on ubuntu 15.10 - Wiley also. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1454404 Title: ACPI PCC Probe Failed Status in xorg package in Ubuntu: Incomplete Bug description: I am running upgrade full version of Ubuntu 15.04 from 14.10 on a Dell XPS-12 laptop. A few months ago, I joined a Linux user group who helped me rid my laptop of a blue screen Microsoft Windows 8.1 Operating system and install Ubuntu 14.10. This laptop has a cinnamon desktop GUI. I have been told that I must put up with the Dell HDD password dialog box on startups before I can start to enter my Ubuntu login prompt screen. The initial boot up message of "ACPI PCC Probe failed occurs prior to my Dell HDD password dialog box logon password window. I will be happy to help you any way I can. I know how to access The Terminal and can do some basic navigation. However, I'm not too thrilled about my Linux user group's low level of involvement with Newbies. I wish I could get the level of training I received many years ago sitting in a classroom learning to use the Apple computer. Back in 2002, I took an introductory Red Hat Linux 6.5 2-day course at Kennesaw State University and loved it! Wish that level of live classroom computer training was in place with Ubuntu! Anyway, I'll help any way I can. This laptop is for learning, and if further issues occur, I can always use my other Windows 7 Professional Dell XPS 9100 Tower to communicate with you if necessary. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue May 12 15:55:00 2015 DistUpgraded: 2015-05-06 10:09:12,951 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0589] InstallationDate: Installed on 2015-01-25 (107 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. XPS 12 9Q23 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=72de4673-bf84-4fb6-811c-ca4ec1a76467 ro splash quiet nopat SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-05-06 (6 days ago) dmi.bios.date: 12/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 089J4R dmi.board.vendor: Dell Inc. dmi.board.version: A00 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.:rn089J4R:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.name: XPS 12 9Q23 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 12 15:53:23 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 957 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1454404/+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
