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.
** 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
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
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
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
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
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.
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
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.
** 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
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
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
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
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
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
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
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:
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
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
@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.
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
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:
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
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
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
> 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
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
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
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
/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
** 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
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
> # 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
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
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
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
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
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,
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
*** 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
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.
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
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
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
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
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
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
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,
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.
** 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
** 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
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
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
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
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
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.
--
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
** 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
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.
** 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
** 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:
-
** 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:
-
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/
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.
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
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.
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.
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
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.
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
** 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.
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
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
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
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,
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
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
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
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
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
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
*** 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
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
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
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
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
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
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 ;)
--
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
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
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
n 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, whi
** 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
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
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
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]
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.
1 - 100 of 3852 matches
Mail list logo
