Public bug reported:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:
* soft memlock 262144
* hard memlock 262144
Should all lightdm users manually put that in limits.conf, or should we
expect some update?
--
You received this bug
Thank you Łukasz, I filed it in LP: #1902879.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1830746
Title:
memlock setting in systemd (pid 1) too low for containers
Hi, this update makes slick-greeter segfault, so Ubuntu MATE 18.04 users
doing normal updates now get a black screen with a flicking cursor.
A temporary workaround is to enable autologin in
/etc/lightdm/lightdm.conf:
[Seat:*]
autologin-guest=false
autologin-user=administrator
Hi, a recent systemd update in 18.04 makes slick-greeter segfault.
So all Ubuntu MATE 18.04 users now get black screens instead of lightdm.
It's related to memory limits so I'm cross-referencing it here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746
This didn't help:
[LightDM]
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:
* soft memlock 262144
* hard memlock 262144
Should all lightdm users manually put that in limits.conf, or should we
expect some update?
--
You received this bug
** No longer affects: ltsp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/206924
Title:
Make it possible to create a guest account
Status in accountsservice:
While working on a remote server, it took me 2-3 hours to locate this
bug report and apply its workarounds. It's certainly not a good default
behavior.
In case someone has already removed netplan, the recommended steps to
get network-manager to manage the interfaces, as I understood them, are:
The issue is still there in today's Ubuntu MATE 22.04 daily built.
Greeks cannot even type their names in the installer (ubiquity)...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
My problem is a bit different: everything works fine, but the dialog
appears when we ACTIVATE a VPN connection, even if we don't want to
modify it.
1) I've prepared a VPN connection for my non-admin users and put it in
/etc/NetworkManager/system-connections/vpn.nmconnection.
2) When they click
Public bug reported:
Hi, recently netplan added support for a yaml NM backend:
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-
settings/32420
The rationale is that "the descriptive YAML layer is especially useful
in cloud environments":
Public bug reported:
I updated my Kubuntu 23.04 to 23.10 using do-release-upgrade. It
finished 100% successfully. But after rebooting into 23.10, I noticed
that network-manager was kept back to the 23.04 version due to phased
updates. Specifically:
# apt policy network-manager
network-manager:
Thank you; if I understood correctly, that method would render all the
NM GUI/console tools unusable; it's not a viable workaround, as I would
like to be able to use these tools as well... E.g.:
- Create a new bond => GUI, nmtui, nmcli
- Did I forget any setting while creating that bond? Let's
I too got affected by this regression.
On servers with network-manager, without netplan (01-network-manager-all.yaml),
systemd-networkd-wait-online.service started failing after the latest updates
and leaves systemd in a degraded state.
Example:
root@gldap:/var/log/apt# ip a
1: lo: mtu 65536
I also see it on Ubuntu MATE Jammy.
Will the fix come from Xorg,
or should we add LightDM to the affected projects list?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1922414
Schools have started installing/upgrading to 22.04.1 and we're just now
seeing this.
This change takes away the ability of the users to share some of their data
WITHOUT involving the administrator.
It's not "privacy by default", it's "mandatory privacy".
Privacy by default could be done with
Reproduced in Ubuntu 22.04 and 20.04.
Could NOT reproduce in Ubuntu 18.04.
I think the problem is in `agetty` though, not in `login`.
Added `util-linux` to affected packages.
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
Please do not add "universe" in "deb cdrom:" lines of
/etc/apt/sources.list.
To reproduce the issue, boot Ubuntu GNOME 22.04, and at the live
session, run:
sudo add-apt-repository universe
After that, `apt update` will keep complaining:
W: Skipping acquire of configured
Public bug reported:
The Debian packaging contains these lines:
https://salsa.debian.org/debian/rsyslog/-/blob/debian/master/debian/rules#L43
--enable-pmnormalize \
--enable-mmnormalize \
AFAIK these were removed because liblognorm was in universe:
- Drop
> I will point out that Firefox, regardless of how it's launched, seems
to not be affected anymore.
If you're testing firefox.snap, that might be the cause, i.e. maybe snap does
the parenting.
While e.g. firefox.deb from the mozillateam PPA (or firefox in Debian) could
still have the issue.
** Changed in: ltsp (Ubuntu)
Status: New => Invalid
--
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/2019940
Title:
Directly manipulating NetworkManager
101 - 121 of 121 matches
Mail list logo
