Just tried with -proposed repo, installation of chromium-browser package
doesn't hang in a chroot anymore.
After first reboot the package is installed in version:
83.0.4103.97-0ubuntu0.20.04.1
Please change tag from verification-needed-focal to verification-done-
focal.
--
You received this b
Oups
```
Command '/usr/bin/chromium-browser' requires the chromium snap to be installed.
Please install it with:
snap install chromium
```
when should it trigger snap installation ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Ansible use his own module to wrap apt command, and it uses non-
interactive way, not just "-y".
Anyway i confirm that this fails under a chroot :
$ DEBIAN_FRONTEND=noninteractive chroot /target apt-get -y install
chromium-browser
Reading package lists...
Building dependency tree...
Reading stat
To reproduce
apt install ansible -y
ansible localhost -m apt -a "name=chromium-browser"
You can try it in a container. That's not exactly a chroot but...
docker run --rm -it ubuntu:latest /bin/bash
apt update && apt install ansible -y
ansible localhost -m apt -a "name=chromium-browser"
--
You
I did install with "apt install chromium-browser -y" for the demonstration.
In my specific case, i use ansible so it is non interactive.
That task fails.
- name: install browsers
apt:
state: latest
name:
- firefox
- firefox-locale-fr
- chromium-browser
- chromium
Public bug reported:
Since snapd integration, chromium-browser package fails to install in a post
kickstart chroot.
As APT obfuscate snap installation, I worry about auto installation off any
other snap package.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: N
By the way : user.lastnamelastnamelastn...@domain.fr does not trigger
the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865517
Title:
cannot log in with long username
To manage notifications
Just retried with fresh download of this file :
http://cdimage.ubuntu.com/daily-live/current/focal-desktop-amd64.iso
I confirm that entering on tty3
username.lastnamelastnamelastn...@domain.fr
(not just "user.")
does trigger the bug.
--
You received this bug notification because you are a membe
All Ubuntu systems are affected.
That's not related to a personal configuration, booting live latest ubuntu let
me reproduce this.
Its more clear on tty, as you see username field resets, but it's the
same from ligthdm
So should i open a bug for agetty package instead ?
--
You received this bu
Nothing but i misexplained, bug isn't related to the fact that account exists
or not.
Please try to enter in a tty that exact login :
'username.lastnamelastnamelastn...@domain.fr'
It reset without asking for password, and the error line is added to
auth.log
Then try :
'username.lastn...@domain
Public bug reported:
We use ldap authentication with mail addresses as usernames.
So usernames are not posix and some are > 32 chars but are working.
Some of them fire a bug :
When trying to log, it doesn't asks for password, it just wait some seconds
then reset to ask username.
I can't clearly
11 matches
Mail list logo
