[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] 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
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 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 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 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 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 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 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 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 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 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 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 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 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
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 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] [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 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 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 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 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 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 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 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 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 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
