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
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
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/
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 subs
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.launch
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 b
** 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/1877
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 do
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/
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 o
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, whi
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
Tit
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
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 subscribe
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
*** 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
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 o
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 e
*** 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
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 w
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 hav
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 rathe
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
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 m
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
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_DEB
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
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 opt
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 thr
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 bu
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
** 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
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 t
33 matches
Mail list logo
