[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
we funnily have removed these udev rules before (but i guess the patch was dropped when syncing a new version) https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968469] Re: ILITEK_ILI9881C panel driver missing
** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968469 Title: ILITEK_ILI9881C panel driver missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968469] [NEW] ILITEK_ILI9881C panel driver missing
Public bug reported: the current 5.15.0-1004-raspi kernel for 22.04 does not enable the CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels can not be used the cutiepi (https://cutiepi.io/) project does use this hardware for their pi based tablets. booting ubuntu 22.04 on such a tablet is only possible with an external HDMI monitor attached at this moment. it would be nice if Ubuntu could work OOTB on this hardware. while the jammy kernel seems to already ship the required dtb overlay "cutiepi-panel.dtbo", the modules this overlay uses are not there. below is a Kconfig commit outlining the required options: https://github.com/cutiepi- io/linux/commit/de6774dca11b815e647fa08d71f3eac9009c2dff ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968469 Title: ILITEK_ILI9881C panel driver missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963919] [NEW] fbtft overlay is missing
Public bug reported: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it gets extremely tricky to even enable the touchscreen input or to use such a TFT with other sensors attached since rpi-display does not allow any re-assignment of the GPIO pins in use. The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. ** Affects: linux-raspi2 (Ubuntu) Importance: Wishlist Status: New ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Wishlist ** Description changed: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it - gets extremely tricky to even enable the touchscreen or use a TFT with - other sensors attached since rpi-display does not allow any re- - assignment of the GPIO pins in use. + gets extremely tricky to even enable the touchscreen input or to use + such a TFT with other sensors attached since rpi-display does not allow + any re-assignment of the GPIO pins in use. - The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. + The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963919 Title: fbtft overlay is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1963919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
for people not using the official announcement channels, here is a link to the related public announcement (with details on the reasoning and a place for discussion and feedback): https://discourse.ubuntu.com/t/feature-freeze-exception-seeding-the- official-firefox-snap-in-ubuntu-desktop/24210 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
note that i did never really follow up with that setup in the end but i found out that even modern SSDs (not only rotary HDDs) usually draw more power than the USB3 port can provide, you will need an Y-Cable or external power supply ... while i can not fully confirm (due to lack of time and testing), i do assume it is not a kernel issue at all here, feel free to close it for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926911] Re: hctosys not reading hardware clock on CM4
https://github.com/snapcore/core-initrd/issues/17 ** Bug watch added: github.com/snapcore/core-initrd/issues #17 https://github.com/snapcore/core-initrd/issues/17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1926911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926911] Re: hctosys not reading hardware clock on CM4
hirsute does not have Ubuntu Core images ;) It seems to be solvable via a simple defconfig change according to: https://github.com/raspberrypi/linux/issues/4205 We have at least one UC customer implementing a CM4 baseboard with TPM for Full disk encryption and secureboot in UC20, for this the clock needs to be correct. The module also needs to move into the UC initrd so it can load before mounting disks, i added an ubuntu-core-initramfs task for this ... ** Bug watch added: github.com/raspberrypi/linux/issues #4205 https://github.com/raspberrypi/linux/issues/4205 ** Also affects: ubuntu-core-initramfs Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1926911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926911] Re: hctosys not reading hardware clock on CM4
ogra@CM4:~$ snap list pi-kernel Name VersionRev Tracking Publisher Notes pi-kernel 5.4.0-1035.38 282 20/edge canonical✓ kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1926911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926911] Re: hctosys not reading hardware clock on CM4
** Description changed: There is a timing issue when using the CM4 with the official CM4 IO baseboard. The CM4 baseboard comes with a built in rtc and a battery holder by default, to enable it a devicetree overlay needs to be enabled and a matching module gets loaded ... $ tail -2 /run/mnt/ubuntu-seed/config.txt dtparam=i2c_vc=on dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi,addr=0x51 $ lsmod | grep pcf85063 rtc_pcf85063 20480 0 When booting the kernel runs hctosys about 1.5sec into the boot, the rtc module only gets loaded about 10sec later though: $ dmesg|grep rtc [1.593561] hctosys: unable to open rtc device (rtc0) [ 10.767256] rtc-pcf85063 10-0051: registered as rtc0 Looking at the systemd journal the clock does not get set at all, only a network connection actually triggers setting of the clock (note the timestamps in the journal): --- Apr 26 10:27:53 ubuntu kernel: mmc0: SDHCI controller on fe34.emmc2 [fe34.emmc2] using ADMA Apr 26 10:27:53 ubuntu kernel: hctosys: unable to open rtc device (rtc0) Apr 26 10:27:53 ubuntu kernel: of_cfs_init Apr 26 10:27:53 ubuntu kernel: of_cfs_init: OK ... Apr 26 10:28:02 CM4 systemd[1]: Started Network Name Resolution. Apr 26 10:28:02 CM4 kernel: rtc-pcf85063 10-0051: registered as rtc0 Apr 26 10:28:02 CM4 systemd-udevd[459]: Using default interface naming scheme 'v245'. ... Apr 26 10:28:08 CM4 avahi.daemon[593]: Registering new address record for 192.168.2.32 on wlan0.IPv4. Apr 26 10:28:08 CM4 systemd-timesyncd[495]: Network configuration changed, trying to establish connection. May 02 17:14:17 CM4 systemd-timesyncd[495]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubu> May 02 17:14:17 CM4 systemd[1]: Starting Online ext4 Metadata Check for All Filesystems... --- I think the loading of the rtc_pcf85063 module should trigger an - additional hctosys call ... + additional hctosys call (preferably from the module itself, but worst + case a udev rule calling out to hwclock --hctosys might work too)... Just for the record, the hwclock works fine otherwise: - $ sudo hwclock + $ sudo hwclock 2021-05-02 19:56:11.281975+00:00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1926911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926911] [NEW] hctosys not reading hardware clock on CM4
Public bug reported: There is a timing issue when using the CM4 with the official CM4 IO baseboard. The CM4 baseboard comes with a built in rtc and a battery holder by default, to enable it a devicetree overlay needs to be enabled and a matching module gets loaded ... $ tail -2 /run/mnt/ubuntu-seed/config.txt dtparam=i2c_vc=on dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi,addr=0x51 $ lsmod | grep pcf85063 rtc_pcf85063 20480 0 When booting the kernel runs hctosys about 1.5sec into the boot, the rtc module only gets loaded about 10sec later though: $ dmesg|grep rtc [1.593561] hctosys: unable to open rtc device (rtc0) [ 10.767256] rtc-pcf85063 10-0051: registered as rtc0 Looking at the systemd journal the clock does not get set at all, only a network connection actually triggers setting of the clock (note the timestamps in the journal): --- Apr 26 10:27:53 ubuntu kernel: mmc0: SDHCI controller on fe34.emmc2 [fe34.emmc2] using ADMA Apr 26 10:27:53 ubuntu kernel: hctosys: unable to open rtc device (rtc0) Apr 26 10:27:53 ubuntu kernel: of_cfs_init Apr 26 10:27:53 ubuntu kernel: of_cfs_init: OK ... Apr 26 10:28:02 CM4 systemd[1]: Started Network Name Resolution. Apr 26 10:28:02 CM4 kernel: rtc-pcf85063 10-0051: registered as rtc0 Apr 26 10:28:02 CM4 systemd-udevd[459]: Using default interface naming scheme 'v245'. ... Apr 26 10:28:08 CM4 avahi.daemon[593]: Registering new address record for 192.168.2.32 on wlan0.IPv4. Apr 26 10:28:08 CM4 systemd-timesyncd[495]: Network configuration changed, trying to establish connection. May 02 17:14:17 CM4 systemd-timesyncd[495]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubu> May 02 17:14:17 CM4 systemd[1]: Starting Online ext4 Metadata Check for All Filesystems... --- I think the loading of the rtc_pcf85063 module should trigger an additional hctosys call ... Just for the record, the hwclock works fine otherwise: $ sudo hwclock 2021-05-02 19:56:11.281975+00:00 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1926911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911943] Re: pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30
well, is there a released snap including this firmware now ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911943 Title: pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1911943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425677] Re: Arduino IDE v. 1.6 released, can we get in repository?
the 1.8.13 snap runs without issues here https://snapcraft.io/arduino -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425677 Title: Arduino IDE v. 1.6 released, can we get in repository? To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1425677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914919] Re: UC20 initrd misses modules to boot from USB disk
USB3 SATA disk needs: $ diff -ruN mods1.txt mods2.txt --- mods1.txt 2021-02-14 11:46:00.578329987 + +++ mods2.txt 2021-02-14 11:46:23.422140313 + @@ -1,4 +1,5 @@ Module Size Used by +uas28672 0 rtl8xxxu 139264 0 rtl8192cu 77824 0 rtl_usb24576 1 rtl8192cu @@ -113,7 +114,7 @@ virtio_blk 20480 0 virtio_scsi24576 0 nls_iso8859_1 16384 0 -usb_storage81920 0 +usb_storage81920 1 uas libahci40960 0 hid_generic16384 0 usbhid 69632 0 USB3 NVME enclosure disk needs: $ diff -ruN mods1.txt mods3.txt --- mods1.txt 2021-02-14 11:46:00.578329987 + +++ mods3.txt 2021-02-14 11:52:09.191046939 + @@ -1,4 +1,8 @@ Module Size Used by +ses20480 0 +enclosure 20480 1 ses +scsi_transport_sas 49152 1 ses +uas28672 0 rtl8xxxu 139264 0 rtl8192cu 77824 0 rtl_usb24576 1 rtl8192cu @@ -113,7 +117,7 @@ virtio_blk 20480 0 virtio_scsi24576 0 nls_iso8859_1 16384 0 -usb_storage81920 0 +usb_storage81920 1 uas libahci40960 0 hid_generic16384 0 usbhid 69632 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914919 Title: UC20 initrd misses modules to boot from USB disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914919] [NEW] UC20 initrd misses modules to boot from USB disk
Public bug reported: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing console output it simply hangs indefinitely with a black screen https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen). + console output it simply hangs indefinitely with a black screen + LP#1914608 ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen - LP#1914608 ). + console output it simply hangs indefinitely with a black screen #1914608 + ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen #1914608 - ). + console output it simply hangs indefinitely with a black screen + https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914919 Title: UC20 initrd misses modules to boot from USB disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914608] [NEW] no console during boot on UC20
Public bug reported: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Description changed: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. - this is also required to bring any kind of bootsplash back to UC20 with + this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914608 Title: no console during boot on UC20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] chromium spams dmesg
snap run --strace chromium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911943] [NEW] pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30
Public bug reported: supposedly the bluetooth firmware from: https://launchpad.net/ubuntu/+source/linux-firmware- raspi2/3-0ubuntu1~20.04.1 should be shipped in the latest pi-kernel snap in the edge/beta channel. the BCM4345C5.hcd (as mentioned in the last changelog entry above) is essential for proper bluetooth audio playback over A2DP. the linux-firmware-raspi2 package from -proposed does not seem to be included in pi-kernel 20/edge as it should. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911943 Title: pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1911943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902915] Re: snapd doesn't ensure portals are available even when they are needed
the majority of snap packages in the store is *not* desktop focused, snaps are widely commercially used in IoT, embedded, industrial, cloud and server setups ... unlike flatpak which is a delivery mechanism for desktop-only apps, snap is an actual package format, making portals a hard dependency of snapd would pull in desktop bits in all the above installations -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902915 Title: snapd doesn't ensure portals are available even when they are needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1902915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
@kosharskiy this is completely unrelated to this installer bug (which is about configuring packages prior to/during install time), you should open a new bug for your issue ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
so this is indeed not an issue with the modules but with the kernel itself and the support for sas, uas or the enclosure services. i test-built all tags from https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux-raspi/+git/focal/refs/tags from 1023.26 going backwards and found that it reliably works until Ubuntu- raspi-5.4.0-1013.13 and reliably hangs with Ubuntu-raspi-5.4.0-1014.14 so somewhere between these two tags the breakage was introduced ... i have now also tried to boot either of the 20.10 images (desktop, server, UC18) and they all expose the same behavior -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905272] Re: Can't get h/w video acceleration on rpi4
this could surely be part of it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905272] Re: Can't get h/w video acceleration on rpi4
talking to juerg (our kernel maintainer) it seems the codec module should be available in 5.4 in UC20, did you try to manually modprobe it ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905272] Re: Can't get h/w video acceleration on rpi4
the config option seems to be: CONFIG_VIDEO_CODEC_BCM2835=m ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
there are various forum and askubuntu threads about this issue already as well: https://forum.snapcraft.io/t/ui-glitch-after-recent-update/15133 https://forum.snapcraft.io/t/some-snaps-app-have-weird-looking-window- control-and-fonts/17859 https://askubuntu.com/q/1206868/66509 https://discourse.ubuntu.com/t/odd-close-button-with-snaps/19392 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898869] Re: System slow on booting
> a) On theory it compromises the throughput (the whole CPU time that will take > for a > process to finish will be longer) for better responsiveness, even under high > load. So > mouse clicks/UI events should be handled faster and say, when decompressing > large files > or other CPU load by specific process the user interface should not freeze. err, nope ... it will prioritize processes differently (the preemption model is completely different) and is not actually optimized for desktop style performance, i'd really go back to the generic kernel here (we'd ship the lowlatency kernel by default on the desktop images if it would actually behave like you describe ;) ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898869 Title: System slow on booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898869] Re: System slow on booting
okay, thats quite different ... a) you run the lowlatency kernel for whatever reason ... this is clearly the worst choice you can pick for already slow hardware (low latency -> do one thing as fast as you can ... ignore other things ... i.e. you trade overall system performance for the ability to do one single task very fast (a typical use for this kernel is fully reliable professional audio processing (no crackling, no jitter) at the cost of desktop performance) b) the (third party) wlan driver crashes in a loop, preventing the network from coming up for quite some time ... c) you seem to run dnscrypt-proxy and that seems to effectively delay working DNS resolution until the end of the boot for whatever reason ... same question as before ... have you tired running a completely unmodified install of 20.04.1 on this hardware ? did that behave similarly slow ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898869 Title: System slow on booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898869] Re: System slow on booting
oh, and i missed, d) there is a mis-configured postfix install running on that device too ... since it is not configured and crashing in a loop during boot anyway, i'd recomend removing postfix ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898869 Title: System slow on booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898869] Re: System slow on booting
erm ... this is an atom/celeron laptop with 4GB that starts BOINC as a system service during boot ? there seems to also be a lot of broken gnome-shell extensions installed on this system that error out during startup ... there is ifupdown installed which is probably involved with the network manager slowness (was this an upgrade from a former LTS ? (ifupdown is deprecated since years now and should not be installed at all) ... have you ever tried a plain unmodified 20.04.1 on this machine without installing all this extra software on top ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898869 Title: System slow on booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901669] Re: /etc/sudoers.d/99-snapd.conf is ignored
/etc/sudoers.d/README pretty clearly states: # This will cause sudo to read and parse any files in the /etc/sudoers.d # directory that do not end in '~' or contain a '.' character. # i wouldn't call that poorly documented (unless someone deletes the README file) ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901669 Title: /etc/sudoers.d/99-snapd.conf is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1901669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901578] Re: Cannot remove snap package ubuntu 20.10
** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901578 Title: Cannot remove snap package ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900356] Re: transition from systemd to snapd breaks functionality
yeah, i agree, the docs could be better here ... the output of "snap stop --help" and "snap disable --help" do show similar text ... to see the (en/disabled) state of any snap based services you can use the "snap services" command ... does using snap stop solve your issue though ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900356 Title: transition from systemd to snapd breaks functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1900356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900356] Re: transition from systemd to snapd breaks functionality
> # snap enable lxd > lxd enabled could it be that you disabled the whole snap instead of just the daemon in the snap (i think then it is indeed expected that the systemd units go away) ? you need to use "snap stop --disable lxd" to disable the service, not "snap disable lxd" which takes the whole of the snap out of function and disables all connections into the system (i.e. service units). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900356 Title: transition from systemd to snapd breaks functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1900356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900356] Re: transition from systemd to snapd breaks functionality
note that this is not reproducable on any machine i tried, as described in: https://forum.snapcraft.io/t/have-a-snap-be-run-only-when-started- manually/20493 The mechanism to manually start disabled snap services seems to work just as it should (and given how many snaps in IoT use such a setup (disabling services after install from a hook and starting them from some master daemon snap on demand) there would be quite an outcry if it failed): $ sudo snap stop --disable lxd Stopped. $ sudo snap start lxd Started. $ on a side-note the apport data above points to a manually modified conffile in /etc/sudoers.d/99-snapd.conf, this contains the default PATH settings for sudo when dealing with snaps, did you modify it on purpose ... ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900356 Title: transition from systemd to snapd breaks functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1900356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
this exists already at http://iso.qa.ubuntu.com/qatracker/%20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888575] Re: Split motd-news config into a new package
please note that the stable UbuntuCore18 images regressed due to this: https://github.com/snapcore/core18/issues/170 ** Bug watch added: github.com/snapcore/core18/issues #170 https://github.com/snapcore/core18/issues/170 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895382] Re: Ability to install 2 or more versions at once
for reference: https://forum.snapcraft.io/t/parallel-installs/7679 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895382 Title: Ability to install 2 or more versions at once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890817] Re: Request to include pi-bluetooth in raspi images
could we first add a small oneshot daemon script in pi-bluetooth that calls: echo -e 'power on\nquit' | bluetoothctl else the BT is not properly powered and thus non-functional when other snaps try to use it ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890817 Title: Request to include pi-bluetooth in raspi images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1890817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
i'll try over the weekend ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662357] Re: Can't use lsb_release on Ubuntu Core 16
*** This bug is a duplicate of bug 1619420 *** https://bugs.launchpad.net/bugs/1619420 first of all the bug is a duplicate, secondly you can not install deb packages on Ubuntu Core, snap packages (of which Ubuntu Core is built) do use /etc/os-release. Additionally Ubuntu Core only ships the most minimal set of python ... If you see an issue on a Classic Ubuntu installation newer than Ubuntu Core 16, you should open a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662357 Title: Can't use lsb_release on Ubuntu Core 16 To manage notifications about this bug go to: https://bugs.launchpad.net/lsb/+bug/1662357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888055] Re: "error: cannot communicate with server: timeout exceeded while waiting for response" when doing snap refresh
could be related to https://blog.cloudflare.com/cloudflare-outage-on-july-17-2020/ (you can always check the status of the snapcraft.io services at status.snapcraft.io/ ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888055 Title: "error: cannot communicate with server: timeout exceeded while waiting for response" when doing snap refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1888055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887369] Re: Slack (got by snap) crashing on startup
please see https://forum.snapcraft.io/t/slack-4-7-0-sefgault-ubuntu-18-04/18708/8 (you should report it via /feedback to slack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887369 Title: Slack (got by snap) crashing on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1887369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
in fact it seems like in 5.3 USB is not working at all !!! i verified that today ... my self-built kernel uses the focal 5.4 branch where USB works fine then: https://github.com/ogra1/linux-raspberrypi- org/blob/master/snap/snapcraft.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
also note that the fabrica appliance you linked uses a re-built kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
hmm, i wonder why they dont load then ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
ok, answering myself again: https://github.com/lxc/lxd-pkg-snap/blob/latest- edge/snapcraft/commands/daemon.start#L192 which simply calls: chroot /var/lib/snapd/hostfs/ \ useradd --system -M -N --home /var/snap/lxd/common/lxd \ --shell /bin/false --extrausers lxd || true i dont see how the system can end up managed here ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
while ignoring UID's below 1000 might help in the short term, the "managed" state has a lot more meanings in brand stores and we will likely encounter more breakage introduced by it when customers pre-seed lxd on branded device images so this side of things needs to still be examined. the lxd user should never turn the device to managed state. i cant see any code in the lxd snap that would create it, where exactly does the user creation even happen ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
answering my own question: ogra@localhost:~$ grep managed /usr/share/subiquity/console-conf-wrapper if [ "$(snap managed)" = "true" ]; then ogra@localhost:~$ grep PRETTY /etc/os-release PRETTY_NAME="Ubuntu Core 18" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
i was thinking the same when i looked at your patch (and noticed the move-around of the "snap managed" code)... are we sure that version of the code is actually in core18 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 684044] Re: thousands of ica processes on system
** Changed in: italc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684044 Title: thousands of ica processes on system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/italc/+bug/684044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683678] Re: iTalc client does not start on one of 3 "identical" systems
** Changed in: italc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683678 Title: iTalc client does not start on one of 3 "identical" systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/italc/+bug/683678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885901] Re: timedatectl reports wrong status for timesyncd in core18
theer we go ... thanks a lot dimitri, i opened https://github.com/snapcore/core18/issues/157 ** Bug watch added: github.com/snapcore/core18/issues #157 https://github.com/snapcore/core18/issues/157 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885901 Title: timedatectl reports wrong status for timesyncd in core18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885901] Re: timedatectl reports wrong status for timesyncd in core18
i dont know where you guys track core bugs either since foundations took over the responsibility Ubuntu Core with core 18... i can not reproduce it on classic anywhere but on each core18 image i have running at my house ... the customer that initially reported it uses core18, so it is important to get it fixed there, regardless if it works in core 20 (i'll do some testing though, but i currently do not have any core20 installs around). it is likely just core specific (confinement, the different way of assembling the rootfs or the fact that timedatectl has a wrapper on core) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885901 Title: timedatectl reports wrong status for timesyncd in core18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885901] [NEW] timedatectl reports wrong status for timesyncd in core18
Public bug reported: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885901 Title: timedatectl reports wrong status for timesyncd in core18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885901] Re: timedatectl reports wrong status for timesyncd in core18
any fix should be SRUed into the respective LTS releases for Ubuntu Core, added tasks for them -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885901 Title: timedatectl reports wrong status for timesyncd in core18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
sadly this isnt true anymore (not that the slow boards got faster but we rather started to ignore that fact), all images nowadays run cloud-init by default so python is kind of mandatory and gets executed anyway ... with the focus on raspberry pi the actual embedded hardware is rather ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
i dont think there is a snap command to get the managed state (there is
"snap known system-user" but that seems to only work if the user was
actually created with an assertion)
if you actually want shell instead of a simple python http query:
root@pi4:~# cat is-managed.sh
#! /bin/sh
query_snapd() {
RET="$(/bin/echo -e 'GET /v2/'"$1"' HTTP/1.0\r\n\r\n' | \
nc -U /var/run/snapd.socket -q0 2>&1 | \
grep -oP '(^.*"'"$2"'":)[^,]*' | \
grep -o '[^:]*$')"
echo "$RET" | sed 's/\]//g;s/\}//g;s/\"//g'
}
echo "System is managed: $(query_snapd system-info managed)"
echo "By user: $(query_snapd users email)"
root@pi4:~# ./is-managed.sh
System is managed: true
By user: o...@ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881588
Title:
pre-seeding lxd on Core appliances breaks console-conf user creation
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Project changed: subiquity => subiquity (Ubuntu) ** Also affects: subiquity (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: subiquity (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
this is definitely a regression, mounting partitions should work ... marking as critical. ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Description changed: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the - initrd as modules ? + core initrd as modules ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Description changed: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) - adding the following to a re-built kernel makes everything work + adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881623] [NEW] USB support missing in initrd makes booting core with writable on USB impossible
Public bug reported: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: when using a gadget.yaml like: volumes: - pi4-system-boot: - schema: mbr - bootloader: u-boot - structure: - - type: 0C - filesystem: vfat - filesystem-label: system-boot - size: 512M - content: - - source: boot-assets/ - target: / - pi4-usb-writable: - schema: mbr - structure: - - name: writable - type: 83 - filesystem: ext4 - filesystem-label: writable - size: 650M - role: system-data + pi4-system-boot: + schema: mbr + bootloader: u-boot + structure: + - type: 0C + filesystem: vfat + filesystem-label: system-boot + size: 512M + content: + - source: boot-assets/ + target: / + pi4-usb-writable: + schema: mbr + structure: + - name: writable + type: 83 + filesystem: ext4 + filesystem-label: writable + size: 650M + role: system-data - - this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... + this creates two separate img files for a Pi image ... one for SD to + hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - - CONFIG_ENCLOSURE_SERVICES=y - - CONFIG_SCSI_SAS_ATTRS=y - - CONFIG_USB_STORAGE=y - - CONFIG_USB_UAS=y + - CONFIG_ENCLOSURE_SERVICES=y + - CONFIG_SCSI_SAS_ATTRS=y + - CONFIG_USB_STORAGE=y + - CONFIG_USB_UAS=y - can we please have these aither built into the kernel or added to the + can we please have these either built into the kernel or added to the initrd as modules ? ** Summary changed: - USB support missing in initrd makes booting with writable on USB impossible + USB support missing in initrd makes booting core with writable on USB impossible -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
is there any particular reason to not simply adjust the patch to point to $SNAP_DATA/etc/chromium-browser/policies ? after all this is where system-wide configs should go ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
it is a hard requirement of the SRU process that fixes land in the devel release and then propagate backwards through all other releases ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878449] Re: 20.04's desktop installer always fsck's when starting
this is intentional and you can skip it with ctrl-c https://discourse.ubuntu.com/t/defaulting-to-verify-the-image-integrity- before-installing-on-desktop/13472 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878449 Title: 20.04's desktop installer always fsck's when starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1878449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876862] Re: Missing v3d driver disables 3D support on RPi4
adding bionic since we're supposed to fully support the pi4 there too ** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876862 Title: Missing v3d driver disables 3D support on RPi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873797] Re: add_mountroot_fail_hook is either buggy or not used properly, causes boot problems
pleas use 1878378 for further discussion of that issue, there is no relation at all to initramfs-tools-ubuntu-core ** Changed in: initramfs-tools-ubuntu-core (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873797 Title: add_mountroot_fail_hook is either buggy or not used properly, causes boot problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-core/+bug/1873797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877852] Re: Evolution not showing unread count in dock, missing build-dep
seems installing evolution-indicator solves it without re-compiling ... closing the bug as invalid ... ** Changed in: evolution (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877852 Title: Evolution not showing unread count in dock, missing build-dep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877852] [NEW] Evolution not showing unread count in dock, missing build-dep
Public bug reported: Evolution has the ability to show the unread messages count in the Dock app icon, this works for the Ubuntu Dock GNOME extension as well as for Dash to Dock and indeed the old unity7 dock ... simply re-compiling the current focal evolution package with an added libunity-dev build dependency like below makes this feature work fine. --- evolution-3.36.1/debian/control.in 2020-04-15 14:27:07.0 + +++ evolution-3.36.1-unity/debian/control.in2020-05-10 12:26:31.687948740 + @@ -55,6 +55,7 @@ libcryptui-dev, libgnome-autoar-0-dev (>= 0.1.1), libgnome-autoar-gtk-0-dev (>= 0.1.1), + libunity-dev (>=7.1.4), Standards-Version: 4.5.0 X-Ubuntu-Use-Langpack: yes Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Description changed: Evolution has the ability to show the unread messages count in the Dock app icon, this works for the Ubuntu Dock GNOME extension as well as for Dash to Dock and indeed the old unity7 dock ... simply re-compiling the current focal evolution package with an added libunity-dev build dependency like below makes this feature work fine. --- evolution-3.36.1/debian/control.in2020-04-15 14:27:07.0 + +++ evolution-3.36.1-unity/debian/control.in 2020-05-10 12:26:31.687948740 + @@ -55,6 +55,7 @@ - libcryptui-dev, - libgnome-autoar-0-dev (>= 0.1.1), - libgnome-autoar-gtk-0-dev (>= 0.1.1), - + libunity-dev (>=7.1.4), - Standards-Version: 4.5.0 - X-Ubuntu-Use-Langpack: yes - Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git + libcryptui-dev, + libgnome-autoar-0-dev (>= 0.1.1), + libgnome-autoar-gtk-0-dev (>= 0.1.1), + + libunity-dev (>=7.1.4), + Standards-Version: 4.5.0 + X-Ubuntu-Use-Langpack: yes + Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git ** Description changed: Evolution has the ability to show the unread messages count in the Dock app icon, this works for the Ubuntu Dock GNOME extension as well as for Dash to Dock and indeed the old unity7 dock ... simply re-compiling the current focal evolution package with an added libunity-dev build dependency like below makes this feature work fine. --- evolution-3.36.1/debian/control.in2020-04-15 14:27:07.0 + +++ evolution-3.36.1-unity/debian/control.in 2020-05-10 12:26:31.687948740 + @@ -55,6 +55,7 @@ libcryptui-dev, libgnome-autoar-0-dev (>= 0.1.1), libgnome-autoar-gtk-0-dev (>= 0.1.1), - + libunity-dev (>=7.1.4), + + libunity-dev (>=7.1.4), Standards-Version: 4.5.0 X-Ubuntu-Use-Langpack: yes Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877852 Title: Evolution not showing unread count in dock, missing build-dep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877852] Re: Evolution not showing unread count in dock, missing build-dep
** Attachment added: "evo-counter.png" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+attachment/5369430/+files/evo-counter.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877852 Title: Evolution not showing unread count in dock, missing build-dep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
well, rsyslog is completely gone from core after UC16 ... how would you test that in UC18 or UC20 to verify SRUs ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
to move the content of the dir you might be able to: stop all snap apps ... mv ~/snap /whereever/your/bigger/disk/is/mounted mkdir ~/snap sudo mount --bind /whereever/your/bigger/disk/is/mounted/snap ~/snap you might need to adjust permissions on the target disk, the snap dir must be fully read/write for the user using it ... and can indeed create a systemd mount unit to make this permanent ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
To extend what zyga said above ... A major amount of snaps are used on appliance, embedded, IoT and server devices (in fact snaps were used in these environments for two years already before they came to the desktop at all). On many of these systemd XDG doesnt even remotely play a role so it was originally not a big focus when snap development started in 2014... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872736] Re: install from USB to USB device wipes grub setup on NVME disk
Sorry for the late reply, here is my /var/log/installer/syslog ** Attachment added: "/var/log/installer/syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1872736/+attachment/5360826/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872736 Title: install from USB to USB device wipes grub setup on NVME disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1872736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873797] Re: add_mountroot_fail_hook is either buggy or not used properly, causes boot problems
also ... i highly doubt that support for lvm2 is planned in UbuntuCore 20, this bug might rather be for the initramfs-tools package itself ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873797 Title: add_mountroot_fail_hook is either buggy or not used properly, causes boot problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-core/+bug/1873797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872065] Re: 'writable' should not be introduced as a new label for persistence partition in Ubuntu 20.04
side-note: /writable was introduced in 2014 FWIW -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872065 Title: 'writable' should not be introduced as a new label for persistence partition in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1872065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872736] Re: install from USB to USB device wipes grub setup on NVME disk
Note that the install to USB seems to have done what it should just fine ... ...but that it wiped existing the bootloader on the internal disk that was explicitly de-selected everywhere is not okay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872736 Title: install from USB to USB device wipes grub setup on NVME disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1872736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872736] [NEW] install from USB to USB device wipes grub setup on NVME disk
Public bug reported: For a system test I prepared a USB stick with the current focal iso, booted from it and attempted an install to another (identical) USB disk. During partitioning /dev/sdb (the USB disk) was picked as target for the bootloader installation, a 63GB ext4 partition for / and a 1GB swap partition were created. The install went flawless. After finishing my testing I removed all USB keys and rebooted to find out i am now greeted with a grub input prompt and have no way to boot off the internal NVME disk anymore... Plugging in the target USB stick that was used to install focal to gives me a proper grub menu allowing me to select to boot the NVME installation. So i can only boot with plugged in USB now, without it i end up at a grub input prompt ... ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872736 Title: install from USB to USB device wipes grub setup on NVME disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1872736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866193] Re: error: too early for operation, device not yet seeded or device model not acknowledged
*** This bug is a duplicate of bug 1864252 *** https://bugs.launchpad.net/bugs/1864252 ** This bug has been marked a duplicate of bug 1864252 preseeded snap installs fail in images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866193 Title: error: too early for operation, device not yet seeded or device model not acknowledged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1866193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866058] [NEW] gadget hooks should not write to /root/snap by default
Public bug reported: using a qemu image I recently noticed that there is a /root/snap/pc dir on the system ... the pc gadget ships an empty no-op configure hook that apparently gets run during seeding. since snapd knows what a gadget is, it would be nice if gadget hooks could by default made to only write to $SNAP_DATA instead of $SNAP_USER_DATA so the dir does not get created in the /root homedir. this is indeed purely cosmetic and low prio ... ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gadget hooks should not write to /root/snap + gadget hooks should not write to /root/snap by default -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866058 Title: gadget hooks should not write to /root/snap by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1866058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866002] [NEW] ubuntu-image should allow to disable console-conf at build time
Public bug reported: currently various odd hacks exist to make sure that console-conf does not start up on appliance or kiosk systems that are supposed to be user- less and get managed only via the snapd REST API. to disable console-conf starting up the file /var/lib/console- conf/complete must exist in the system. to allow disabling console-conf at image build time (to overcome the various hacks) something like a --no-console-conf option should be added to ubuntu-image so no hacks are necessary anymore for this type of images. ** Affects: ubuntu-image (Ubuntu) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: In Progress ** Description changed: currently various odd hacks exist to make sure that console-conf does not start up on appliance or kiosk systems that are supposed to be user- less and get managed only via the snapd REST API. to disable console-conf starting up the file /var/lib/console- conf/complete must exist in the system. to allow disabling console-conf at image build time (to overcome the various hacks) something like a - --no-console-conf option should be added to ubuntu-image so no hacks ar + --no-console-conf option should be added to ubuntu-image so no hacks are necessary anymore for this type of images. ** Changed in: ubuntu-image (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866002 Title: ubuntu-image should allow to disable console-conf at build time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1866002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864162] Re: Don't install snap programs.
*** This bug is a duplicate of bug 1864252 *** https://bugs.launchpad.net/bugs/1864252 ** This bug has been marked a duplicate of bug 1864252 preseeded snap installs fail in images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864162 Title: Don't install snap programs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1864162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863214] Re: Add storage kernel modules for arm64/armhf build
The pc-kernel snap is essentially just "linux-generic", sadly it was decided back then that the "linux-generic" name was not appropriate and that we would only build the kernel snap for amd64 in core16 In core 18 it was finally accepted to also build this kernel for both arm arches so that we can support all boards that are also supported by the linux-generic deb version of the respective arch (there are cubox, sabrelite, beaglebone, pocketbeagle and a few other community images based on the armhf pc-kernel snap around already). Thus this request is indeed only for core18. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863214 Title: Add storage kernel modules for arm64/armhf build To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools-ubuntu-core/+bug/1863214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852720] Re: docker snap suddenly installed by itself
sadly snapd wipes the logs after a while so your snap changes start only at change 33 and this is only a refresh of the already installed docker snap ... it would be interesting to know why/how it got installed in the first place, perhaps someone from the snapd team has a hint here ... do you have any docker management tools installed that might have pulled in the docker snap ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852720 Title: docker snap suddenly installed by itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1852720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852720] Re: docker snap suddenly installed by itself
unattended-updates do not deal with snap packages (effectively snaps care for their upgrades themselves, there is no external entity like unattended-upgrades needed)... also snap packages do not "just install themselves", something must have actively triggered that ... along with syslog (or rather journald output nowadays) the output of "snap changes" would be interesting as well ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852720 Title: docker snap suddenly installed by itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1852720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
the requirement for policykit (and dropping of gksu/gksudo) came with the switch to gnome upstream, its a hard requirement for the desktop nowadays. while the default here might be wrong (and should be reviewed by someone from the desktop team), this is definitely not a snapd related bug. i added a gnome-software task and will close the snapd one ... ** Changed in: snapd (Ubuntu) Status: Incomplete => Invalid ** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850977 Title: Snap installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850977] Re: Snap installs software without user having sudo access
policyKit does not involve sudo in any way, it uses systemd-logind from the session to elevate privileges. if you are marked as admin in the policyKit setup you will indeed be able to do admin things no matter what is written in sudoers ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850977 Title: Snap installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1850977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
the included snapcraft.yaml means i need to have the whole tree locally on disk, as someone who maintains a ton of community images for UbuntuCore i prefer to just have the snapcraft.yaml locally so the disk is only cluttered during build. along with that i am trying to build the eoan tree for the core18 Pi4 image i provide, the wlan firmware is not in the linux-firmware package in bionic, so i need overrides ... beyond this, a lot of config options that i require to be builtin are modules and the initramfs handling in snapcraft is still a mess, so i prefer to build in MMC support and USB disk support... along with this we have a good bunch of customers building custom kernels with out-of-tree snapcraft file and brand stores so it helps to know what they experience. :) note that once we have an official core image for the Pi4 i'll drop this work anyway ... closing the bug as invalid ... ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
well, as a user/customer building my own kernel i'd kind of expect the defconfig for a flavour to not be a debug config. but indeed you are correct, i should have taken a look at the included snapcraft.yaml which, despite being for the wrong flavour (generic/pc- kernel), indeed contains CONFIG_DEBUG_INFO=n as a defconfig override ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
ok, this looks a bit more reasonable now ... $ ls -lh pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap -rw-r--r-- 1 ogra ogra 211M Nov 4 17:05 pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap so CONFIG_DEBUG_INFO=y should better be turned off by default for people building snaps from our trees ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
yup, seems this is (surprisingly) on by default ... $ grep DEBUG_INFO parts/kernel/build/.config CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_INFO_REDUCED is not set # CONFIG_DEBUG_INFO_SPLIT is not set CONFIG_DEBUG_INFO_DWARF4=y # CONFIG_DEBUG_INFO_BTF is not set i'll try a re-build and override that option from snapcraft.yaml ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
i also tried using the "source-branch: raspi2" argument in the snapcraft.yaml instead of using teh master branch and the "source-tag:" option, but this results in the same big size ... additionally i'd like to remark that due to the transactional nature of UbuntuCore we need to keep the kernel three times on the device for the automatic rollback feature ... the current size would mean 2.1GB for compressed kernels alone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851233] [NEW] building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
Public bug reported: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M/mnt/System.map-5.3.1+ 211K/mnt/config-5.3.1+ 906K/mnt/dtbs 475M/mnt/firmware 4.5M/mnt/initrd-5.3.1+.img 7.0M/mnt/kernel.img 512 /mnt/meta 1.6G/mnt/modules 2.1Gtotal $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560942] Re: Support swap
it is working via manual intervention after login like: https://forum.snapcraft.io/t/enabling-swap-on-ubuntu-core/5440 i.e. i implemented the OS side of it ... but we still do not have any "snap set system.swap=" option to steer it or set via a gadget configuration option in the yaml, this would be a snapd configuration task. ** Changed in: snappy Assignee: Oliver Grawert (ogra) => (unassigned) ** Changed in: ubuntu-core-config (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560942 Title: Support swap To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1560942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796047] Re: update-ieee-data throws error because of wrong url
** Also affects: ieee-data (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796047 Title: update-ieee-data throws error because of wrong url To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ieee-data/+bug/1796047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844498] Re: 18.10+ cloud images have the LXD group as gid 1000
note that the build scripts for core do have an md5sum check to detect changes to /etc/passwd|group|shadow because this file is orignally readonly. dirs created with specific UIDs/GIDs by package postinist scripts that get copied into the writable area of the rootfs during first boot would fail to be owned by the daemon users the packages set up for them during a core update... adding a new entry to one of the readonly password db files is fine but requires changes in livecd-rootfs and an update of the expected md5sum ... additionally to the above, since /etc/group is readonly, you can not add users to the lxd group if you add lxd there so unprivileged containers on core will become impossible, the GID of lxd should be transferred into /var/lib/extrausers/group to make it possible to add a local system user to this group. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844498 Title: 18.10+ cloud images have the LXD group as gid 1000 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1844498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution
after a comment from jamesh in the forum discussion i found that installing nscd from universe works around the issue, but this does not change the fact that it is a regression of an ubuntu default feature, so there still needs to be some solution (snapd dependency on nscd and moving nscd back into main, fixing nssswitch.conf inside the core/core18 snap or some other new solution) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838038 Title: [snap] Chromium does not work with .local mdns/avahi name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution
trying your test on any of my machines does not work here btw (so i assume it has nothing to do with running the server locally) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838038 Title: [snap] Chromium does not work with .local mdns/avahi name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution
well, try something thats not on localhost, i know that i cant resolve anything in my LAN that uses mdns (note that this will also affect printing i guess) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838038 Title: [snap] Chromium does not work with .local mdns/avahi name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
