[Touch-packages] [Bug 1696500] Re: /var/log/wtmp is updated to 1970-01-01 before systemd-update-utmp.service (or fake-hwclock)
This is still a problem in June 2021. Would you mind please explaining the reason for not fixing it? -- 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/1696500 Title: /var/log/wtmp is updated to 1970-01-01 before systemd-update- utmp.service (or fake-hwclock) Status in systemd package in Ubuntu: Won't Fix Bug description: I have a raspberry pi with fake-hwclock installed and it seems the documented behaviour doesn't work E.g. from /lib/systemd/system /systemd-timesyncd.service, specifically: "ensure [clock] monotonically advances even if the system lacks a battery-buffered RTC chip" - this doesn't actually happen. I have tried editing /lib/systemd/system/fake-hwclock.service to have: [Unit] Description=Restore / save the current clock Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=systemd-update-utmp.service sysinit.target Conflicts=shutdown.target I also tried to edit /lib/systemd/system/systemd-update-utmp.service to have: [Unit] Description=Update UTMP about System Boot/Shutdown Documentation=man:systemd-update-utmp.service(8) man:utmp(5) DefaultDependencies=no RequiresMountsFor=/var/log/wtmp Conflicts=shutdown.target # After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service fake-hwclock.service After=systemd-timesyncd.service fake-hwclock.service time-sync.target Before=sysinit.target shutdown.target [Service] Type=oneshot RemainAfterExit=yes ExecStartPre=/sbin/fake-hwclock load ExecStart=/lib/systemd/systemd-update-utmp reboot ExecStop=/lib/systemd/systemd-update-utmp shutdown However on reboot, the wtmp file is still being updated before systemd-update-utmp.service and fake-hwclock: $ last reboot | head -n 3 reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 still running reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 - 22:04 (17316+21:04) reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 - 22:04 (17316+21:04) Looking at the journalctl I can see the time is already set and /var/log/wtmp is already updated to 1970 before any of the above can run: $ sudo journalctl -u systemd-update-utmp -- Logs begin at Wed 2017-06-07 17:18:08 IST, end at Wed 2017-06-07 17:19:05 IST. -- Jun 07 17:18:14 TimeBox systemd[1]: Starting Update UTMP about System Boot/Shutdown... Jun 07 17:18:14 TimeBox fake-hwclock[823]: Current system time: 2017-06-07 16:18:14 Jun 07 17:18:14 TimeBox fake-hwclock[823]: fake-hwclock saved clock information is in the past: 2017-06-07 16:18:08 Jun 07 17:18:14 TimeBox fake-hwclock[823]: To set system time to this saved clock anyway, use "force" Jun 07 17:18:14 TimeBox systemd[1]: Started Update UTMP about System Boot/Shutdown. So the "Update UTMP about System Boot/Shutdown." doesn't work, the time is already set to 1 Jan 1970 by something else. How do I run a service/command before /var/log/wtmp is touched and set to 1 Jan 1970? - It seems the documented behaviour/methods do not work. I'm using Ubuntu 16.04 with systemd 229-4ubuntu17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1696500/+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 1795936] Re: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
** Package changed: apport (Ubuntu) => linux (Ubuntu) -- 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/1795936 Title: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Status in linux package in Ubuntu: Incomplete Bug description: This was working an hour ago, but at the moment I get the following when I run: apt-get install linux-image-generic: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic partner ``` Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795936/+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 1795936] [NEW] linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable
Public bug reported: This was working an hour ago, but at the moment I get the following when I run: apt-get install linux-image-generic: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic partner ``` Any ideas? ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1795936 Title: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Status in apport package in Ubuntu: New Bug description: This was working an hour ago, but at the moment I get the following when I run: apt-get install linux-image-generic: ``` Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable Recommends: thermald but it is not going to be installed ``` My sources.list look like this: ``` ## Ubuntu Main Repos deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse ## Ubuntu Update Repos deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse ## Ubuntu Partner Repo deb http://archive.canonical.com/ubuntu bionic partner deb-src http://archive.canonical.com/ubuntu bionic partner ``` Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1795936/+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 1696500] [NEW] /var/log/wtmp is updated to 1970-01-01 before systemd-update-utmp.service (or fake-hwclock)
Public bug reported: I have a raspberry pi with fake-hwclock installed and it seems the documented behaviour doesn't work E.g. from /lib/systemd/system/systemd- timesyncd.service, specifically: "ensure [clock] monotonically advances even if the system lacks a battery-buffered RTC chip" - this doesn't actually happen. I have tried editing /lib/systemd/system/fake-hwclock.service to have: [Unit] Description=Restore / save the current clock Documentation=man:fake-hwclock(8) DefaultDependencies=no Before=systemd-update-utmp.service sysinit.target Conflicts=shutdown.target I also tried to edit /lib/systemd/system/systemd-update-utmp.service to have: [Unit] Description=Update UTMP about System Boot/Shutdown Documentation=man:systemd-update-utmp.service(8) man:utmp(5) DefaultDependencies=no RequiresMountsFor=/var/log/wtmp Conflicts=shutdown.target # After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service fake-hwclock.service After=systemd-timesyncd.service fake-hwclock.service time-sync.target Before=sysinit.target shutdown.target [Service] Type=oneshot RemainAfterExit=yes ExecStartPre=/sbin/fake-hwclock load ExecStart=/lib/systemd/systemd-update-utmp reboot ExecStop=/lib/systemd/systemd-update-utmp shutdown However on reboot, the wtmp file is still being updated before systemd- update-utmp.service and fake-hwclock: $ last reboot | head -n 3 reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 still running reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 - 22:04 (17316+21:04) reboot system boot 4.4.0-1055-raspi Thu Jan 1 01:00 - 22:04 (17316+21:04) Looking at the journalctl I can see the time is already set and /var/log/wtmp is already updated to 1970 before any of the above can run: $ sudo journalctl -u systemd-update-utmp -- Logs begin at Wed 2017-06-07 17:18:08 IST, end at Wed 2017-06-07 17:19:05 IST. -- Jun 07 17:18:14 TimeBox systemd[1]: Starting Update UTMP about System Boot/Shutdown... Jun 07 17:18:14 TimeBox fake-hwclock[823]: Current system time: 2017-06-07 16:18:14 Jun 07 17:18:14 TimeBox fake-hwclock[823]: fake-hwclock saved clock information is in the past: 2017-06-07 16:18:08 Jun 07 17:18:14 TimeBox fake-hwclock[823]: To set system time to this saved clock anyway, use "force" Jun 07 17:18:14 TimeBox systemd[1]: Started Update UTMP about System Boot/Shutdown. So the "Update UTMP about System Boot/Shutdown." doesn't work, the time is already set to 1 Jan 1970 by something else. How do I run a service/command before /var/log/wtmp is touched and set to 1 Jan 1970? - It seems the documented behaviour/methods do not work. I'm using Ubuntu 16.04 with systemd 229-4ubuntu17 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: fakehw-clock raspberrypi rtc systemd ** Description changed: I have a raspberry pi with fake-hwclock installed and it seems the documented behaviour doesn't work E.g. from /lib/systemd/system/systemd- timesyncd.service, specifically: "ensure [clock] monotonically advances even if the system lacks a battery-buffered RTC chip" - this doesn't actually happen. I have tried editing /lib/systemd/system/fake-hwclock.service to have: - [Unit] - Description=Restore / save the current clock - Documentation=man:fake-hwclock(8) - DefaultDependencies=no - Before=systemd-update-utmp.service sysinit.target - Conflicts=shutdown.target + [Unit] + Description=Restore / save the current clock + Documentation=man:fake-hwclock(8) + DefaultDependencies=no + Before=systemd-update-utmp.service sysinit.target + Conflicts=shutdown.target + + I also tried to edit /lib/systemd/system/systemd-update-utmp.service to have: - [Unit] - Description=Update UTMP about System Boot/Shutdown - Documentation=man:systemd-update-utmp.service(8) man:utmp(5) - DefaultDependencies=no - RequiresMountsFor=/var/log/wtmp - Conflicts=shutdown.target - # After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service fake-hwclock.service - After=systemd-timesyncd.service fake-hwclock.service time-sync.target - Before=sysinit.target shutdown.target + [Unit] + Description=Update UTMP about System Boot/Shutdown + Documentation=man:systemd-update-utmp.service(8) man:utmp(5) + DefaultDependencies=no + RequiresMountsFor=/var/log/wtmp + Conflicts=shutdown.target + # After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service fake-hwclock.service + After=systemd-timesyncd.service fake-hwclock.service time-sync.target + Before=sysinit.target shutdown.target - [Service] - Type=oneshot - RemainAfterExit=yes - ExecStartPre=/sbin/fake-hwclock load - ExecStart=/lib/systemd/systemd-update-utmp reboot - ExecStop=/lib/systemd/systemd-update-utmp shutdown - However on reboot, the wtmp file is still being upda
[Touch-packages] [Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
I'm on systemd 229-4ubuntu10 -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
I'm on Xenial and I ran an apt-get update; apt-get dist-upgrade and my eth0 changed back to enxb827djdk after reboot :( My biggest issue is virtual interfaces do NOT work with these "predictable" network names. I can do ifconfig eth0:0 192.168.123.123 but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just overrites the main IP, rather than creating another virtual interface :( Previously, I was able to follow these steps: Edit/boot/firmware/config.txt to add: net.ifnames=0 biosdevname=0 Run: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules Make sure this file is absent (which it was anyway): /lib/udev/rules.d/73-usb-net-by-mac.rules Run: update-initramfs -k all -u But now, running the above steps no longer works and I'm getting enxb827djdk again :( I also checked /proc/cmdline and I have net.ifnames=0 there so it's definitely being passed. I'm running kernel 4.4.0-1023-raspi2 Sep 6 16:12:44 UTC 2016 Is there a solution/workaround? -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Any solution to this? - I'm passing net.ifnames=0 biosdevname=0 but after the latest apt-get upgrade, it is ignored :( -- deployer@ubuntu:~$ uname -a Linux ubuntu 4.4.0-1021-raspi2 #27-Ubuntu SMP Fri Aug 12 11:44:06 UTC 2016 armv7l armv7l armv7l GNU/Linux deployer@ubuntu:~$ cat /proc/cmdline 8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa02082 bcm2709.serial=0x80f5f71c smsc95xx.macaddr=B8:27:EB:F5:F7:1C bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait net.ifnames=0 biosdevname=0 deployer@ubuntu:~$ ifconfig -a enxb827ebf5f71c Link encap:Ethernet HWaddr b8:27:eb:f5:f7:1c inet addr:192.168.101.69 Bcast:192.168.101.255 Mask:255.255.255.0 inet6 addr: fe80::ba27:ebff:fef5:f71c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:666 errors:0 dropped:0 overruns:0 frame:0 TX packets:514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:106425 (106.4 KB) TX bytes:94870 (94.8 KB) -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1554806] Re: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now
Any workaround for this? - How would one automate setting a timezone on 16.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1554806 Title: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now Status in tzdata package in Ubuntu: Confirmed Bug description: In previous versions it was possible to set the system's timezone by editing /etc/timezone before running "dpkg-reconfigure -f noninteractive tzdata". This behavior changed, /etc/timezone gets overwritten unconditionally during "dpkg-reconfigure -f noninteractive tzdata": --- root@xenial:/# echo "Europe/Berlin" > /etc/timezone root@xenial:/# cat /etc/timezone Europe/Berlin root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Tue Mar 8 23:09:39 UTC 2016. Universal Time is now: Tue Mar 8 23:09:39 UTC 2016. root@xenial:/# cat /etc/timezone Etc/UTC --- As a workaround to programmatically set the timezone one now needs to point "/etc/localtime" to the new timezone: --- root@xenial:/# ln -fs /usr/share/zoneinfo/Europe/Berlin /etc/localtime root@xenial:/# ll /etc/localtime lrwxrwxrwx 1 root root 33 Mar 9 00:48 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin root@xenial:/# cat /etc/timezone Etc/UTC root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Europe/Berlin' Local time is now: Wed Mar 9 00:49:05 CET 2016. Universal Time is now: Tue Mar 8 23:49:05 UTC 2016. root@xenial:/# cat /etc/timezone Europe/Berlin --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1554806/+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 1554806] Re: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now
Ah, sorry, didn't read the report properly. Thank you for the workaround! -- Any workaround for echo "en_GB.UTF-8 UTF-8" > /var/lib/locales/supported.d/local? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1554806 Title: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now Status in tzdata package in Ubuntu: Confirmed Bug description: In previous versions it was possible to set the system's timezone by editing /etc/timezone before running "dpkg-reconfigure -f noninteractive tzdata". This behavior changed, /etc/timezone gets overwritten unconditionally during "dpkg-reconfigure -f noninteractive tzdata": --- root@xenial:/# echo "Europe/Berlin" > /etc/timezone root@xenial:/# cat /etc/timezone Europe/Berlin root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Tue Mar 8 23:09:39 UTC 2016. Universal Time is now: Tue Mar 8 23:09:39 UTC 2016. root@xenial:/# cat /etc/timezone Etc/UTC --- As a workaround to programmatically set the timezone one now needs to point "/etc/localtime" to the new timezone: --- root@xenial:/# ln -fs /usr/share/zoneinfo/Europe/Berlin /etc/localtime root@xenial:/# ll /etc/localtime lrwxrwxrwx 1 root root 33 Mar 9 00:48 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin root@xenial:/# cat /etc/timezone Etc/UTC root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Europe/Berlin' Local time is now: Wed Mar 9 00:49:05 CET 2016. Universal Time is now: Tue Mar 8 23:49:05 UTC 2016. root@xenial:/# cat /etc/timezone Europe/Berlin --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1554806/+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 1330262] Re: HUAWEI E3531 not connected on Ubuntu 14.04
I am seeing something completely different and for me the issue is with usb_modeswitch first: This is what I see when I plug mine in: https://gist.github.com/xanview/3a37e6eb0cf24a12908b The key lines are: Jan 28 16:19:23 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:19:23 TimeBox systemd[1]: usb_modeswitch@1-1.5-1-1.5:1.0.service: main process exited, code=exited, status=1/FAILURE It seems Ubuntu is trying to do the wrong thing, it is trying to do systemctl start usb_modeswitch@1-1.5-1-1.5:1.0 when in reality the command should be: $ systemctl start usb_modeswitch@1-1.5:1.0 When I run the correct command, I see this in syslog: Jan 28 16:34:05 TimeBox systemd[1]: Starting USB_ModeSwitch... Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: Could not read attribute: No such file or directory Jan 28 16:34:06 TimeBox usb_modeswitch: switch device 12d1:14fe on 001/008 Jan 28 16:34:05 TimeBox usb_modeswitch_dispatcher[10502]: message repeated 2 times: [ Could not read attribute: No such file or directory] Jan 28 16:34:07 TimeBox usb_modeswitch[10502]: usb_modeswitch: switched to 12d1:14fe on 1/8 Jan 28 16:34:08 TimeBox usb_modeswitch_dispatcher[10502]: Unable to open bind list file: No such file or directory Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: add device ID 12d1:14fe to driver option Jan 28 16:34:08 TimeBox usb_modeswitch[10502]: usb_modeswitch: please report the device ID to the Linux USB developers! Jan 28 16:34:15 TimeBox systemd[1]: Started USB_ModeSwitch. So seems this is an unsupported device still? (I'm on Ubuntu 15.04 Vivid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1330262 Title: HUAWEI E3531 not connected on Ubuntu 14.04 Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Triaged Bug description: PC: Dell 3721 OS:Ubuntu 14.04 i386 DE: KDE Kernel: 3.13.0-29 and 3.15.0 (Stable) usb-modeswitch 2.2.0 (Debian Unstable)/2.1.1 A connection is defined and a modem in the system, but an error while connecting: "Connection deactivated". Upgrading to kernel 3.15 (stable) and usb-modeswitch (2.2.0) not solve the problem. LOGS: dmesg [ 84.302769] usb 3-4: new high-speed USB device number 3 using xhci_hcd [ 84.431625] usb 3-4: New USB device found, idVendor=12d1, idProduct=1506 [ 84.431632] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 84.431635] usb 3-4: Product: Mobile Connect [ 84.431638] usb 3-4: Manufacturer: .. [ 84.731329] usbcore: registered new interface driver usbserial [ 84.731348] usbcore: registered new interface driver usbserial_generic [ 84.731362] usbserial: USB Serial support registered for generic [ 84.762404] usbcore: registered new interface driver option [ 84.762424] usbserial: USB Serial support registered for GSM modem (1-port) [ 84.762598] option 3-4:1.0: GSM modem (1-port) converter detected [ 84.762763] usb 3-4: GSM modem (1-port) converter now attached to ttyUSB0 [ 84.762820] option 3-4:1.1: GSM modem (1-port) converter detected [ 84.762947] usb 3-4: GSM modem (1-port) converter now attached to ttyUSB1 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1330262/+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 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Any workaround? -- 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/1509769 Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in ubuntu-mate: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Error occured during UBUNTU Mate upgrade to 15.10 on Raspberry PI2 and once trying perform manual update getting: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.120ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.120ubuntu6) ... update-initramfs: Generating /boot/initrd.img-3.18.0-25-rpi2 Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 15.10 Package: initramfs-tools 0.120ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17 Uname: Linux 3.18.0-25-rpi2 armv7l ApportVersion: 2.19.1-0ubuntu3 Architecture: armhf Date: Sun Oct 25 08:19:08 2015 DuplicateSignature: package:initramfs-tools:0.120ubuntu6:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1509769/+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 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Any temporary solution in the mean time? -- 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/1509769 Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Error occured during UBUNTU Mate upgrade to 15.10 on Raspberry PI2 and once trying perform manual update getting: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.120ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.120ubuntu6) ... update-initramfs: Generating /boot/initrd.img-3.18.0-25-rpi2 Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 15.10 Package: initramfs-tools 0.120ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17 Uname: Linux 3.18.0-25-rpi2 armv7l ApportVersion: 2.19.1-0ubuntu3 Architecture: armhf Date: Sun Oct 25 08:19:08 2015 DuplicateSignature: package:initramfs-tools:0.120ubuntu6:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509769/+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
