Same problem here, with 22.04 and firefox :
https://forum.snapcraft.io/t/cannot-open-path-of-the-current-working-
directory-permission-denied-bis/28704
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@acubuntuone we don't use kerberos authentication for NFS mounts here,
and I face the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662552
Title:
snaps don't work with NFS home
To
Public bug reported:
$ ubuntu-drivers --package-list yolo.txt list
WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support
PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid
Support PBheader, cannot determine
Public bug reported:
$ ubuntu-drivers --no-oem install
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 490, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
File
** Changed in: chromium-browser (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927071
Title:
Fresh install of chromium-browser during installer-like process,
This is not a container, this is the desktop installer iso system.
Yes, "snap list" returns something in the installer system but it is run in the
chrooted env.
"chroot /target snap list" is working too. It should not, is it right ?
As said in the previous issue, i want those snap to be
Public bug reported:
Here is the first bug report : https://bugs.launchpad.net/ubuntu/+source
/chromium-browser/+bug/1882232
It seems that there is a regression, pre-installation script of apt
installed chromium-browser package doesn't detect that it is running in
a chroot anymore.
=>
It seems that there is a regression, see ansible logs attached.
This is run in a post install chroot.
=> Installing the chromium snap
==> Checking connectivity with the snap store
===> Unable to contact the store, trying every minute for the next 30
minutes
===> Still unable to
Public bug reported:
Here the cmdline:
vmlinuz initrd=initrd rootfstype=nfs netboot=nfs
nfsroot=162.38.151.26:/exports/focal-desktop boot=casper ip=dhcp
fsck.mode=skip automatic-ubiquity url=http://162.38.151.26/preseed/fds
/focal-efi.seed
File /run/systemd/netif/leases/2:
# This is private
>The design is based on the idea of a template image. The Ubuntu server
image is ready to boot and on first boot cloud-init handles the tasks
to "instantiate the image".
>Doesn't the autoinstall input generatea cloud-init config that
configures these things?
As i understand it, autoinstall
If i run autoinstall with that user-data file, autoinstall doesn't run
and subiquity prompt for language setting.
#cloud-config
runcmd:
- systemctl daemon-reload
- systemctl restart gdm3
autoinstall:
version: 1
packages:
- gdm3
locale: fr_FR.UTF-8
user-data:
timezone:
This is log collected after first boot with previous minimal user-data
file (which only set locales, timezone and install lightdm package), i
waited for cloud-config to run.
** Attachment added: "cloud-init.tar.gz"
> installing lightdm brings in over 500 packages and took about 12 minutes to
> install;*
It seems normal to me, it installs a big tree of dependencies because its the
first "graphic" package.
> Some package may require post-install configuration.
I used that method with success for many years
That screenshot show time when those services are ready
- gdm
- cloud-init
- cloud-config
** Attachment added: "screenshot"
https://bugs.launchpad.net/subiquity/+bug/1907107/+attachment/5441963/+files/2020-12-08T13%3A28%3A16%2C955532233+01%3A00.png
--
You received this bug notification
Actually, its gdm which runs on tty1, as i did not enabled lightdm...
but it doesnt change the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907107
Title:
cloud-init runs too late at
You can reproduce with that minimal user-data config
#cloud-config
autoinstall:
version: 1
packages:
- lightdm
locale: fr_FR.UTF-8
user-data:
timezone: Europe/Paris
refresh-installer:
update: yes
identity:
hostname: localhost
username: first
password: changeme
As I manually setup a unit which plays with Before=lightdm.service,
maybe it breaks something, i will test and tell later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907107
Title:
cloud-init
I use autoinstall to get my system installed in a specific state, then i need
to boot that state.
I want my tools to use that state (lightdm for exemple), so if cloud-config
needs to run some tasks it should do it before i can interact with my system.
Is that normal that cloud-config starts
It seems that cloud-init runs too late.
When starting host, i get login prompt on tty1 then cloud-init starts running
overriding and messing up output.
When I use installer to install desktop, lightdm starts before cloud-init has
run.
Then, lightdm is in english (no locale is generated yet),
I didn't wait at first startup for scripts to run to finish configurations, i
ran my test too early.
Changing hostname doesn't break timezone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907107
I found what happens but i can't explain:
if I set a different hostname with early command, then timezone is not
correctly set after reboot:
early-commands:
- hostname whatever
Related to https://bugs.launchpad.net/subiquity/+bug/1905932
--
You received this bug notification because you are
21 matches
Mail list logo
