Still present with ISO of 20240421
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2063003
Title:
package manager could not make changes to the installed system
Status in apt
Error does not prevent the installed system from booting, but it still
contains the installer and related items.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2063003
Title:
Public bug reported:
This is the cause of Ubuntu Unity failing to install. Test case requires
system to be offline.
The full error message is:
The package manager could not make changes to the installed system. The command
apt-get --purge -q -y remove ^live-* calamares-settings-ubuntu-unity
I can confirm ajgreeny's message. Installed in a QEMU/KVM VM and got a
working GUI after reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2052489
Title:
Mate Daily
Same message as others. This is on kinetic (VM), and two jammy
(hardware) installs. One of the jammy versions boots via coreboot, not
UEFI.
All are booting normally after the error.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Verification successful.
Package version: systemd-245.4-4ubuntu3.1 from -proposed repository.
Upgraded and rebooted. The network came up normally.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member
Also working here.
'networkctl status' shows:
● State: routable
Address: 192.168.1.65 on br0
192.168.122.1 on virbr0
fe80::3a2c:4aff:febd:306a on br0
Gateway: 192.168.1.1 (PC Engines GmbH) on br0
DNS:
The following has me wondering if this has partly to do with the
presence of containers, VMs and similar items.
I upgraded my router to 20.04 a few days before release. (Plain Ubuntu
command-line OS on a PC Engines APU1 board) That machine has a bridge
network comprising two ethernets and one
I've opened a new bug report: Bug #1874178
I'll mark myself as not affected by this one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
Unlocking existing
Public bug reported:
This has been occurring during the Xubuntu post-install test. It's not
the same as Bug #1776475, as it's not necessary to have logged in as
another user (or even for another user to exist) for the problem to
happen.
My sequence of actions is:
*Create new user.
*Open a
The default value was 0 minutes. I set it to one minute and it made no
difference.
Incidentally, it seems that clicking on the "Switch user" button is
enough to trigger the problem. I did this because I couldn't remember
whether or not I'd added another user (I hadn't at that point). It's not
A fresh install on an external USB3 drive is showing exactly the same
behaviour. Not a VM problem, apparently.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
@Stéphane: Sorry, I didn't see this sooner. I must have forgotten to
subscribe. (oops)
In Xubuntu Final (iso 20200420.1), there is no Security tab in the Power
Manager. Only a "security" checkbox which controls "Lock screen when
system is going to sleep". I had a look in the configuration editor
This seems to have reappeared recently in Xubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1776475
Title:
Unlocking existing session often requires several
Is now working as expected on my EeePC 900. That includes waking from
suspend. (I don't use hibernate.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1574347
@hussain
I installed 1.2 on my EeePC by enabling the Proposed repository in
Software and Updates. This isn't usually recommended for everyone as it
can break things, but is useful for testing.
Once the patched version is released and is moved from the Proposed to
the regular repository, it will
@Cip Man:
That explains it, then. I'm happy to wait for the patched version to
come through.
My current workaround is to add the line
service NetworkManager restart
to /etc/rc.local
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I'm still having the issue on my EeePC 900 after installing
NetWorkManager 1.2.0 from xenial-proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1574347
Title:
Bug has been reported at
https://bugzilla.gnome.org/show_bug.cgi?id=765123
** Bug watch added: GNOME Bug Tracker #765123
https://bugzilla.gnome.org/show_bug.cgi?id=765123
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Additional information:
I ran dpkg from the recovery menu. I'm uncertain whether that's caused
the following behaviour or not.
On logging in, network manager shows "[wireless card name] disconnected"
On turning off wireless with the function key, network manager shows
"[wireless card name]
Public bug reported:
Using xenial on Asus EeePC 900
Network manager has worked fine with the wireless card on this machine,
until the update of 12 April.
Now the wireless card appears greyed out in the nm-applet interface with
no SSIDs visible. Ethernet still works.
wicd works on this machine,
The locale settings were simply the result of following the standard
install process and confirming that my location was Auckland when
requested.
It sounds like something isn't working properly during the install. Do I
need to report a new bug?
--
You received this bug notification because you
I just installed the latest daily ISO for Ubuntu.
Immediately after installation, the command "locale" shows the
following:
LANG=en_NZ.UTF-8
LANGUAGE=en_NZ:en
LC_CTYPE="en_NZ.UTF-8"
LC_NUMERIC="en_NZ.UTF-8"
LC_TIME="en_NZ.UTF-8"
LC_COLLATE="en_NZ.UTF-8"
LC_MONETARY="en_NZ.UTF-8"
Public bug reported:
After updating language-pack-en and language-pack-en-base in Xubuntu
16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-greeter.
Current locale, after fiddling with language support, is:
LANG=en_US.UTF-8
LANGUAGE=en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_NZ.UTF-8
Still crashing on Asus EeePC 900. I've not tried with the battery
removed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1547793
Title:
upowerd crashed with SIGSEGV in
25 matches
Mail list logo
