Haven't had a crash yet since disabling the tiling-assistant extension.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050865
Title:
GNOME Wayland session crashes with
Disabled now. I will give an update after some time whether the crashing
stopped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050865
Title:
GNOME Wayland session crashes with
If you have a step-by-step, I'm happy to try and get the information you
need.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050865
Title:
GNOME Wayland session crashes with
Yes I can see a corresponding .upload and .uploaded file.
Unique ID is: f8601c66-2247-11ef-8ba3-fa163ec8ca8c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050865
Title:
GNOME Wayland session
I have a crash report from the latest crash today and have run ubuntu-
bug to upload it. It's not showing on errors.ubuntu.com yet, but maybe
it takes some time?
```
ubuntu-bug /var/crash/_usr_bin_gnome-shell.8046.crash
```
--
You received this bug notification because you are a member of
I have these mutter package versions:
```
ii gir1.2-mutter-14:amd64 46.1-2ubuntu1
amd64GObject introspection data for Mutter
ii libmutter-14-0:amd64 46.1-2ubuntu1
amd64
```
Jun 04 08:55:59 ubu-n-c3c04f314633 gnome-shell[4176]:
libmutter:ERROR:../src/core/window.c:5941:meta_window_get_work_area_for_logical_monitor:
assertion failed: (logical_monitor)
Jun 04 08:55:59 ubu-n-c3c04f314633 gnome-shell[4176]: Bail out!
I just had this same crash again on 24.04 with the patched mutter
packages installed. Although, I will say I haven't experienced the issue
as frequently as before installing the patched versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I think I'm having the same issue
I am running TPM+FDE on Ubuntu 24.04. I tried to apply the workaround suggested
with following command:
snap set system system.kernel.dangerous-cmdline-append="i915.enable_dc=0
intel_idle.max_cstate=2"
But I'm still seeing the same after a reboot. In my case,
I've finally had time to test this on a non TPM-FDE machine and can
confirm that services like cups are now working after installing the
systemd version from noble-proposed.
Testing:
- Install clean Ubuntu 24.04 (no TPM-FDE)
- Install dracut & reboot
- Check cups status (failing to start)
-
Hi Łukasz,
Here is the testing I have performed.
- Enabled noble-proposed
- Installed latest systemd from noble-proposed (255.4-1ubuntu8.1)
- removed all systemd drop-in files for cups
- Rebooted the device
After rebooting I monitored the cups.service but it still is failing to start.
I can see
Public bug reported:
On a test laptop running Ubuntu 24.04, I am occasionally seeing my
desktop session crash and return to the login screen.
I haven't identified a pattern for these crashes yet but seems to occur
randomly regardless of which app i have open or if I'm interacting with
the system
Public bug reported:
This was previously reported here:
https://github.com/canonical/ubuntu-desktop-installer/issues/2371
But I think that bug report and those posted in other projects don't seem to be
getting attention.
With the new TPM-backed FDE storage layout for Ubuntu 24.04, it is
Public bug reported:
This is more like a quality-of-life issue. If you have a source
configured which is broken (gpg key error, no release information,
etc.), update-manager will provide a vague error message that doesn't
really help users identify the problem.
See attached screenshot.
Ideally,
On my test VM I can see the cupsd profile DOES have 'attach_disconnected' flag,
but not 'attach_disconnected.path=/run/'
If I add it and restart the cups.service, it starts successfully.
rsyslogd and sssd apparmor profiles do not have either these flags.
Could an apparmor abstraction work for
Answering questions from #2064088
Q: Did you install this fde/tpm setup using the ubuntu desktop noble installer?
Or was hit some manual setup?
A: The install was performed using autoinstall with the desktop ISO. Attached
is a copy of the autoinstall yaml
** Attachment added: "autoinstall
Answering questions from #2064088
Q: Can you also show the output of: ps fauxwZ
A: See attached
** Attachment added: "ps"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+attachment/5774011/+files/ps
--
You received this bug notification because you are a member of Ubuntu
Do you think we should mark #2064088 as a duplicate of this (or vice-
versa), if we're confident this is the same underlying issue?
There are some outstanding questions for me on that bug, but it might
make sense to focus our comments in one place going forward.
--
You received this bug
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+attachment/5773256/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064088
Title:
sssd
Here is the dmesg output when trying to start sssd. I'll attach syslog
as well from the same time period
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+attachment/5773255/+files/dmesg
--
You received this bug notification because you are a member
I've just found that the cups.service is also experiencing the same
behaviour. Again it has the service type 'notify'.
I suspect other services using this type will have the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
This might be related to #2064088
The rsyslog service is continually timing out and restarting. If I use a
service drop-in file and change the 'Type' from 'notify' to 'simple',
the service starts and appears to work normally.
In the journal, I can see the attached apparmor
I should add that this is a system built with TPM-backed FDE if that has
any relevance. I haven't tested on a non-encrypted system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064088
Title:
sssd
Public bug reported:
On a fresh build of Ubuntu 24.04, attempting to run the sssd service is
failing continuously with a systemd service 'timeout' error.
The same /etc/sssd/sssd.conf file is working in 20.04 and 22.04
I believe this issue is specifically related to the sssd systemd
service.
In
This issue is still present with the current latest Libreoffice Snap
version (24.2.2.2) both in Ubuntu 22.04 LTS and in the 24.04 Beta.
SMB shares and other GVFS mounted network locations are not visible in
the Open/Save file window.
If I try to manually navigate to the files under
After revisiting this, I found the issue was on my side.
Our LDAP wasn't returning the members list for groups when queried so polkit
wasn't able to authorise those users.
I fixed this in our sssd.conf using the 'ignore_group_members = false' option.
--
You received this bug notification
Public bug reported:
This was tested on Ubuntu 24.04 with all current updates applied.
To reproduce the issue:
- Open gnome-control-centre
- Navigate to the 'Apps' section
- Click on any app
- Click the 'App Details' button
The system will open the snap-store front-page, but won't show the
Public bug reported:
With a fresh install of the daily Ubuntu 24.04, polkitd does not create
the default config files under /etc/polkit-1/localauthority.conf.d/
This folder should contain some default config files which specify which
users can perform GUI admin authorization.
In fact, even if I
Same issue for me. It looks like this only occurs on the first login
with a given user.
After logging-out and back in again, I can't reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With software-properties-gtk (0.99.44), the 'Other Software' section displays
the full multi-line comment from the new ubuntu.sources file.
This creates an unpleasant looking entry in the list.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Can confirm that the version in noble-proposed fixes this issue.
Although I noticed another bug, possibly related to deb822 sources in
general rather than this specific change: #2058715
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With the latest proposed versions of software-properties-gtk, software-
properties-common, and python3-software-properties (0.99.44), it is
possible to break the default ubuntu.sources list.
How to replicate
1. Open software-properties-gtk
2. Uncheck all of the repository
This issue might also affect 22.04 with the HWE kernel
Going from kernel 6.5.0-21 to 6.5.0-25, we're seeing the same change in
kernel parameters
On a system with kernel 6.5.0-21 I have these kernel parameters set:
vm.mmap_rnd_bits = 28
vm.mmap_rnd_compat_bits = 8
On a system with the new kernel
I've since tested by placing the Include option at the top of the
config, and it works.
I had assumed positioning was irrelevant, or that it should check
/etc/ssh/sshd_config.d by default as described in the man pages:
```
Note that the Debian openssh-server package sets several options as
According to man pages, this is set by default (at least on debian-based
systems) so I tried both with and without specifying 'Include
/etc/ssh/sshd_config.d/*.conf' in the main sshd_config file.
But neither seem to work.
I've attached the sshd_config file used when testing previously. I
** Attachment added: "sshd debug output"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+attachment/5578186/+files/sshd_debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968305
** Attachment added: "Contents of override file"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968305/+attachment/5578185/+files/sshd_config_override
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Creating an sshd_config override file under /etc/ssh/sshd_config.d/ does
not override settings from /etc/ssh/sshd_config
From debugging sshd, I can see the override file is indeed being read,
and the option is supposedly set. But after testing, the options are not
taking
Ubuntu 20.04.4
gnome-font-viewer 3.34.0-2
Have attached the output of 'journalctl -b 0' after seeing this issue twice in
a row.
First time, the entire desktop froze and I had to switch TTY and force kill the
process.
Second time, only gnome-font-viewer froze and eventually prompted to 'force
Public bug reported:
While investigating another issue, I noticed my snap refresh timer was
showing the next refresh as 'yesterday'. The snap changes command also
did not list any recent changes.
jamesps@ubu20-n-0649f43030:~$ snap refresh --time
timer: 00:00~24:00/4
last: yesterday at 12:05 GMT
If it helps, I tried re-installing the kernel metapackage and got the
attached errors, which may be useful for troubleshooting this.
** Attachment added: "kernel_error.txt"
Public bug reported:
Despite configuring unattended-upgrades to run on battery power, the
script will only run automatically when on AC power due to a condition
of the systemd apt-daily.service
Here is my current Unattended-Upgrades config (apt-config dump
Unattended-Upgrade):
```
I can't seem to collect the relevant data with that command. I'm
receiving a popup saying 'No additional information collected', and on
the terminal it says 'Package linux-signed-hwe-5.13 not installed and no
hook available, ignoring'.
In fact I don't have any signed kernel packages. But I do
Public bug reported:
The video driver for my AMD GPU does not seem to be loading properly
with kernel 5.13. The GUI loads but is stuck with a low resolution.
Output of 'lspci -v' command seems to show that no graphics driver is in
use. I expect 'amdgpu' to be the selected driver for my GPU.
44 matches
Mail list logo
