[Touch-packages] [Bug 1965646] Re: pulseaudio missing even though says installed in software center. Have no audio
Is this bug related to https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963934 ? If doing this solves the issue, then it probably is: sudo touch /usr/share/pipewire/media-session.d/with-pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965646 Title: pulseaudio missing even though says installed in software center. Have no audio Status in pulseaudio package in Ubuntu: New Bug description: Previously: had SoundHissheadphones https://answers.launchpad.net/ubuntu/+question/700984 Messed with pulseaudio until it's totally gone even though on the software center it still says it is installed but unable to remove it because it says: "PulseAudio System Tray": no packages to remove Sudo apt remove pulseaudio Removing pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pipewire-pulse (0.3.48-1ubuntu1) ... Created symlink /etc/systemd/user/default.target.wants/pipewire-pulse.service → /usr/lib/systemd/user/pipewire-pulse.service. Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket → / usr/lib/systemd/user/pipewire-pulse.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for libglib2.0-0:amd64 (2.71.3-1) ... sudo apt purge Purging configuration files for pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Processing triggers for dbus (1.12.20-2ubuntu3) . ___ No audio symbol, it's gone Software center still says it is installed. Unable to remove "PulseAudio" in software center Unable to remove"PulseAudio Volume Control": no packages to remove Version 0.17.0 ___ mate-volume-control No device to configure under Hardware Input: unchecked Monitor of Dummy Output Output: unchecked Dummy Output Stereo __ sudo apt-get update -y sudo apt-get install -y pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libsbc1 libssl1.1 linux-headers-5.13.0-19 Use 'sudo apt autoremove' to remove them. Suggested packages: pavumeter paprefs ubuntu-sounds The following NEW packages will be installed: pulseaudio 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Need to get 0 B/913 kB of archives. After this operation, 4,674 kB of additional disk space will be used. Selecting previously unselected package pulseaudio. (Reading database ... 321785 files and directories currently installed.) Preparing to unpack .../pulseaudio_1%3a15.99.1+dfsg1-1ubuntu1_amd64.deb ... Unpacking pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Adding user pulse to group audio Created symlink /etc/systemd/user/default.target.wants/pulseaudio.service → /usr/lib/systemd/user/pulseaudio.service. Created symlink /etc/systemd/user/sockets.target.wants/pulseaudio.socket → /usr/lib/systemd/user/pulseaudio.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for dbus (1.12.20-2ubuntu3) ...y sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libsbc1 libssl1.1 linux-headers-5.13.0-19 0 upgraded, 0 newly installed, 3 to remove and 7 not upgraded. After this operation, 80.1 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 321976 files and directories currently installed.) Removing libsbc1:amd64 (1.5-3build1) ... Removing libssl1.1:amd64 (1.1.1l-1ubuntu1) ... Removing linux-headers-5.13.0-19 (5.13.0-19.19) ... Processing triggers for libc-bin (2.35-0ubuntu3) ... pulseaudio W: [pulseaudio] pid.c: Stale PID file, overwriting. E: [pulseaudio] socket-server.c: bind(): Address already in use E: [pulseaudio] module.c: Failed to load module "module-native-protocol-unix" (argument: ""): initialization failed. E: [pulseaudio] main.c: D-Bus name org.pulseaudio.Server already taken. pulseaudio -k E: [pulseaudio] main.c: Failed to kill daemon: No such process __ ubuntu-bug -s audio Package pulseaudio 1:15:99.1+dgsg1-1ubuntu1 2.20.11-Outbuntu79 __ killall pulseaudio; pulseaudio -k ; rm -r ~/.config/pulse/* ; rm -r ~/.pulse* rm -r ~/.pulse* pulseaudio: no process found E: [pulseaudio] main.c: Failed to kill daemon: No such process rm: cannot remove '/home/ptosis/.pulse*': No such file or directory pulseaudio --start waited 10 seconds, then reboot wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh bash alsa-info.sh --stdout
[Touch-packages] [Bug 1782854] Re: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13)
Updating to 0.131ubuntu2 solved the problem. Thanks! -- 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/1782854 Title: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782854/+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 1782854] Re: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13)
The other computer (main one I'm writing from) got the same message after update to 0.131ubuntu1, so I booted with the older kernel (4.15), downgraded initramfs-tools, initramfs-tools-bin and initramfs-tools-core to 0.130ubuntu10 and successfully rebooted with the new kernel. I saved the broken and working initrd.img-4.17.0-5-generic images. Please advise if and where to upload them (27MB each). -- 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/1782854 Title: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) Status in initramfs-tools package in Ubuntu: New Bug description: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782854/+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 1782854] [NEW] CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13)
Public bug reported: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Tags added: cosmic ** Summary changed: - CRITICAL BUG IN 0.131ubuntu1: Failed to execute /init (error -13) + CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) -- 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/1782854 Title: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) Status in initramfs-tools package in Ubuntu: New Bug description: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782854/+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 1649156] Re: Dependency on libdouble-conversion1 causes conflict
Thanks Dmitry, I did so. I know this is a development version of Ubuntu and rough edges like are to normal, but can't this transition be done without conflict in package management? Is there a general document describing the GCC5 transition and the future of *v5 packages, aside from these two [1][2] outdated pages, so users can know which variant to keep in situations like this? 1: https://wiki.debian.org/GCC5 2: https://wiki.ubuntu.com/GCC5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1649156 Title: Dependency on libdouble-conversion1 causes conflict Status in double-conversion: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Invalid Bug description: Hi, Since this change: https://launchpadlibrarian.net/295556379/double-conversion_2.0.1-3ubuntu2_2.0.1-4ubuntu1.diff.gz libdouble-conversion1 breaks libdouble-conversion1v5 and since this change: https://launchpadlibrarian.net/296573650/qtdeclarative-opensource-src_5.6.1-7ubuntu2~1_5.6.1-7ubuntu2~2.diff.gz I have a conflict on Zesty with 2 resolutions: 1. Keep libqt5qml5 unupdated 2. Remove libdouble-conversion1v5 and install libdouble-conversion1 What should I do and isn't v5 meant to replace the original libdouble-conversion1? Cheers, Marko To manage notifications about this bug go to: https://bugs.launchpad.net/double-conversion/+bug/1649156/+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 1649156] [NEW] Dependency on libdouble-conversion1 causes conflict
Public bug reported: Hi, Since this change: https://launchpadlibrarian.net/295556379/double-conversion_2.0.1-3ubuntu2_2.0.1-4ubuntu1.diff.gz libdouble-conversion1 breaks libdouble-conversion1v5 and since this change: https://launchpadlibrarian.net/296573650/qtdeclarative-opensource-src_5.6.1-7ubuntu2~1_5.6.1-7ubuntu2~2.diff.gz I have a conflict on Zesty with 2 resolutions: 1. Keep libqt5qml5 unupdated 2. Remove libdouble-conversion1v5 and install libdouble-conversion1 What should I do and isn't v5 meant to replace the original libdouble-conversion1? Cheers, Marko ** Affects: double-conversion Importance: Undecided Status: New ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Also affects: double-conversion Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1649156 Title: Dependency on libdouble-conversion1 causes conflict Status in double-conversion: New Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: Hi, Since this change: https://launchpadlibrarian.net/295556379/double-conversion_2.0.1-3ubuntu2_2.0.1-4ubuntu1.diff.gz libdouble-conversion1 breaks libdouble-conversion1v5 and since this change: https://launchpadlibrarian.net/296573650/qtdeclarative-opensource-src_5.6.1-7ubuntu2~1_5.6.1-7ubuntu2~2.diff.gz I have a conflict on Zesty with 2 resolutions: 1. Keep libqt5qml5 unupdated 2. Remove libdouble-conversion1v5 and install libdouble-conversion1 What should I do and isn't v5 meant to replace the original libdouble-conversion1? Cheers, Marko To manage notifications about this bug go to: https://bugs.launchpad.net/double-conversion/+bug/1649156/+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 1643129] Re: Drop system-config-printer-gnome package
Current state of packages in Zesty (proposed is disabled) produces a conflict for those with system-config-printer 1.5.7+20160812-0ubuntu2 because updating it to 1.5.7+20160812-0ubuntu4 breaks system-config-printer-gnome (<< 1.5.7+20160812-0ubuntu3~) and available version of system-config-printer-gnome is 1.5.7+20160812-0ubuntu2 Proposed resolutions are: 1. keep system-config-printer 2. remove system-config-printer-gnome I resolved the conflict by removing system-config-printer-gnome only after finding this LP bug and figuring out what's going on. I know this is a development version of Ubuntu, but many people will still be confused with this conflict. Maybe there is a different way of making this transition that doesn't create a conflict? Cheers, Marko -- 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/1643129 Title: Drop system-config-printer-gnome package Status in Ubuntu GNOME: Triaged Status in system-config-printer package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Fix Released Bug description: I don't think the system-config-printer-gnome split makes sense any more and it would be nice to get this package closer in sync with Debian. In other words, let's drop system-config-printer-gnome and move most of its contents back to system-config-printer but a few files will end up in system-config-printer-common. The last explicit merge was almost a decade ago: https://launchpad.net/ubuntu/+source/system-config-printer/0.7.70-1ubuntu1 ) The split was done in 2008 for KDE's benefit: https://launchpad.net/ubuntu/+source/system-config-printer/0.7.78+svn1799-0ubuntu2 - system-config-printer-kde no longer exists (it appears to have been part of the kdeadmin source package which was removed a few years ago) - Kubuntu only ships system-config-printer-udev so they aren't affected now http://cdimage.ubuntu.com/cdimage/kubuntu/daily-live/current/zesty-desktop-amd64.manifest - Ubuntu GNOME does not need the files shipped in system-config- printer since GNOME has its own integrated Printers Settings panel. https://packages.debian.org/sid/all/system-config-printer/filelist In Ubuntu 16.10 I attempted to follow Debian's gnome-control-center packaging and depend on system-config-printer-common only, but it broke the Printers panel since Ubuntu's packaging moved the dbus service to the system-config-printer-gnome package (See bug 1496860 & bug 1623150 & bug 1637466 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1643129/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
update the remote watch ** Bug watch added: Debian Bug tracker #735169 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735169 -- 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/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Status in os-prober package in Debian: Unknown Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem
[Touch-packages] [Bug 1539826] Re: initramfs-tools hook-functions error causes failure
I can confirm both the bug (with /dev/sda1 on my computers) and that Jay's patch works. I would like to make a fix, if that's OK (and if it's needed). This would be "my" first fix and I'm following this tutorial: http://packaging.ubuntu.com/html/fixing-a-bug.html -- 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/1539826 Title: initramfs-tools hook-functions error causes failure Status in initramfs-tools package in Ubuntu: Confirmed Bug description: The /usr/share/initramfs-tools/hook-functions contains what appears to be a variable name update (from root to dev_node) error. It appears that one instance of root was not updated correctly; this causes mkinitramfs to fail with the error: mkinitramfs: for device /dev/vda1 missing vda1 /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug A trivial patch that appears to resolve this is attached. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.120ubuntu7 [modified: usr/share/initramfs-tools/hook-functions] ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 29 17:44:20 2016 InstallationDate: Installed on 2016-01-29 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160129) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1539826/+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 1539826] Re: initramfs-tools hook-functions error causes failure
I've tried proposing the merge but got "lp:~sm4rk0/initramfs-tools is not mergeable into this repository." This is where I pushed the patched hook-functions: git+ssh://git.launchpad.net/~sm4rk0/initramfs-tools -- 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/1539826 Title: initramfs-tools hook-functions error causes failure Status in initramfs-tools package in Ubuntu: Confirmed Bug description: The /usr/share/initramfs-tools/hook-functions contains what appears to be a variable name update (from root to dev_node) error. It appears that one instance of root was not updated correctly; this causes mkinitramfs to fail with the error: mkinitramfs: for device /dev/vda1 missing vda1 /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug A trivial patch that appears to resolve this is attached. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.120ubuntu7 [modified: usr/share/initramfs-tools/hook-functions] ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 29 17:44:20 2016 InstallationDate: Installed on 2016-01-29 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160129) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1539826/+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 1538707] Re: package initramfs-tools 0.120ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1539826 *** https://bugs.launchpad.net/bugs/1539826 ** This bug has been marked a duplicate of bug 1539826 initramfs-tools hook-functions error causes failure -- 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/1538707 Title: package initramfs-tools 0.120ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Fail after upgrade, 16.04, 27.01.16 valera@ubuntu-home:~$ sudo apt-get install -f Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово Следующие пакеты устанавливались автоматически и больше не требуются: linux-headers-4.3.0-6 linux-headers-4.3.0-6-generic linux-image-4.3.0-6-generic linux-image-extra-4.3.0-6-generic Для их удаления используйте «sudo apt autoremove». обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 1 пакетов не обновлено. не установлено до конца или удалено 1 пакетов. После данной операции, объём занятого дискового пространства возрастёт на 0 B. Настраивается пакет initramfs-tools (0.120ubuntu7) … update-initramfs: deferring update (trigger activated) Обрабатываются триггеры для initramfs-tools (0.120ubuntu7) … update-initramfs: Generating /boot/initrd.img-4.4.0-040400-generic mkinitramfs: for device /dev/sda1 missing sda1 /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-4.4.0-040400-generic with 1. dpkg: ошибка при обработке пакета initramfs-tools (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 1 При обработке следующих пакетов произошли ошибки: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.120ubuntu7 Uname: Linux 4.4.0-040400-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 Date: Tue Jan 26 23:42:00 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-01-17 (9 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: initramfs-tools Title: package initramfs-tools 0.120ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-01-19 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1538707/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
Hi Romain, Thanks for interesting observation and analysis, but I believe these two problems are not related. As a test, try restarting the computer and then logging in via one of the tty2-tty6 (Ctrl-Alt-F2 - Ctrl-Alt-F6). I'm getting that line with user@1000.service only on first tty login after a boot. Cheers, Marko -- 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/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in systemd package in Ubuntu: Won't Fix Status in systemd-shim package in Ubuntu: Triaged Status in systemd source package in Utopic: Triaged Status in systemd-shim source package in Utopic: Won't Fix Status in systemd-shim package in Debian: New Bug description: ATTENTION: This bug is fully understood, there is *no need* to add even more comments about me too here. [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1359439/+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
