Same problem here, during upgrade from mantic 23.10.1 to noble 24.04:
Configurando gdebi-core (0.9.5.7+nmu7) ...
/usr/share/gdebi/GDebi/GDebiCli.py:159: SyntaxWarning: invalid escape sequence
'\S'
c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
In my case gdebi-core isn't the only package wit
Public bug reported:
Problem summary:
I've installed the zram-config package. By default it creates a zram swap
device with half the physical memory size of the system. For instance, in an
8GB RAM system:
# swapon
NAME TYPE SIZE USED PRIO
/dev/zram0 partition 3,8G
As a workaround you can include in the "[Service]" section of the file
"/etc/systemd/system/multi-user.target.wants/zram-config.service" this
line:
ExecStartPost=/usr/bin/systemctl restart systemd-oomd.service
It causes systemd-oomd.service to be restarted after zram-config.service
start.
--
Yo
Public bug reported:
This warning is shown in the system journal (during boot):
nov 06 17:15:23 fpgrpi generate[840]: Permissions for
/etc/netplan/01-use-network-manager.yaml are too open. Netplan
configuration should NOT be accessible by others.
The file /etc/netplan/01-use-network-manager.yaml
Public bug reported:
PROBLEM SUMMARY:
Just upgraded to Ubuntu 23.04 (lunar) from Ubuntu 22.10 (kinetic). systemd-oomd
fails with "ConditionControlGroupController=memory was not met" during boot.
If you manually started it after boot it starts but after a few minutes it
fails wi
I see that memory cgroup is not enabled:
# cat /proc/cgroups | grep y
#subsys_name hierarchy num_cgroups enabled
memory 0 121 0
So a workaround is to enable it adding "cgroup_enable=memory" to
"/boot/firmware/cmdline.txt" kernel parameters file for Raspberr
** Tags added: linux-raspi raspberry-pi
--
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/2017209
Title:
systemd-oomd fails with "ConditionControlGroupController=memory was
** Summary changed:
- systemd-oomd fails with "ConditionControlGroupController=memory was not met"
+ [Raspberry Pi/lunar] systemd-oomd fails with
"ConditionControlGroupController=memory was not met"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
There may be a problem with the proposed repo.
The .deb files version in lunar-proposed repo is 6.2.0-1005.7 but inside
the file http://ports.ubuntu.com/ubuntu-ports/dists/lunar-
proposed/main/binary-arm64/Packages.gz there is also a non-existent
version 6.2.0.1005.8 that causes conflict. Notice t
Just installed and tested the proposed kernel: memory cgroup is enabled
by default and problem is solved.
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
The file /etc/apt/preferences.d/proposed-updates didn't exists in my
system. I've created it with your content and proposed updates now are
working.
But, AFAIK, I've never needed to pin proposed updates repo to make it
work until now (?)
--
You received this bug notification because you are a me
Public bug reported:
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app in
Same problem here in different architecture:
O.S. Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8Gb).
Fails during boot:
# systemctl status systemd-rfkill.service
● systemd-rfkill.service - Load/Save RF Kill Switch Status
Loaded: loaded (/lib/systemd/system/systemd-rfkill.service; static)
Ac
Amr Ibrahim (amribrahim1987) wrote on 2015-08-26:
Is this related?
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1040158
---
It's related but not the same. The report you pointed seems to be quite
old and states that nautilus takes focus only whe
Problem persist in Ubuntu 20.04 LTS stable release:
root@fpglinux:/var/cache# lsb_release -d
Description:Ubuntu 20.04 LTS
root@fpglinux:/var/cache# apt policy procps
procps:
Instalados: 2:3.3.16-1ubuntu2
Candidato: 2:3.3.16-1ubuntu2
Tabla de versión:
*** 2:3.3.16-1ubuntu2 500
@Björn Michaelsen; the fixed pic you posted looks very nice. Hope the
fix reach the repo soon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1580537
Title:
LibreOff
IMHO this is an important bug; well, it doesn't break any important OS
feature but it affects the general image of Unity & Ubuntu the users
should have because it happens with a usually frequent task execution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Problem summary:
After upgrading from Noble to Oracular the kernel parameters enclosed in the
file /etc/sysctl.conf are not being loaded by systemd-sysctl service.
The problem is that Oracular systemd package
(systemd_256.5-2ubuntu3_amd64.deb) lacks the file
I'm sorry but I don't understand your answer. I don't see the relevancy
of the origin or the contents of the /etc/sysctl.conf file; if that file
exists in the system it must be loaded. Otherwise, it's an error.
Apart from Ubuntu installers there are lot's of configuration scripts,
installers, appl
Tested new 25.0.6-0ubuntu0.3 build from ppa:tjaalton/test3. Same
problem:
gnome-remote-de[2227]: [RDP.CLIPRDR] Client capabilities: long format names
gnome-remote-de[2227]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set
with version RDPGFX_CAPVERSION_107, Client cap flags: H264 (AVC444): fa
1st/ 25.0.4 ppa:tjaalton/test
Same error on Remote Desktop Sharing connection:
gnome-remote-de[2237]: [RDP.CLIPRDR] Client capabilities: long format names
gnome-remote-de[2237]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set
with version RDPGFX_CAPVERSION_107, Client cap flags: H264 (AVC44
2nd/ 25.0.5 ppa:tjaalton/test2
Same error on Remote Desktop Sharing connection:
gnome-remote-de[2228]: [RDP.CLIPRDR] Client capabilities: long format names
gnome-remote-de[2228]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set
with version RDPGFX_CAPVERSION_107, Client cap flags: H264 (AVC4
3rd/ 25.0.6 ppa:tjaalton/test3
Same error on Remote Desktop Sharing connection:
gnome-remote-de[2224]: [RDP.CLIPRDR] Client capabilities: long format names
gnome-remote-de[2224]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set
with version RDPGFX_CAPVERSION_107, Client cap flags: H264 (AVC4
I think that probably these messages are not enough to locate the
problem. I just copy them from the messages emitted during the failed
RDP connection using "journalctl -f", and no mesa direct errors are
issued.
If you want more info, please, give me the instructions to extract it.
Thank you very
24 matches
Mail list logo
