This is still a problem in 24.04 with the Snap version of LibreOffice
(which of course is the default version you're presented with when you
search for it in the store)
I have multiple network drives mounted with gvfs. From LibreOffice, I
cannot open or save files to these locations using the file
Public bug reported:
With the Ubuntu 24.04 Desktop ISO, and the latest stable ubuntu-desktop-
bootstrap snap (0+git.9b015d0d6), autoinstall is failing when attempting
to add a recovery key.
I have attached the relevant installer logs and autoinstall user-data.
I've inspected them myself and can s
** Attachment added: "Original user-data contents"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2073594/+attachment/5798579/+files/user-data
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I'm seeing similar issue for a user at our organisation.
Same make/model of laptop.
Same error message:
i915 :00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
Apparently shutting the lid (suspend) then wake seems to temporarily fix the
problem.
--
You received this bug
I think I'm seeing the same issue, but on Ubuntu 24.04 with
2.0.5-1build1 (currently the latest version).
I've inspected the dpkg error messages and found the following:
```
Resolving ftp.wwpdb.org (ftp.wwpdb.org)... failed: Name or service not known.
wget: unable to resolve host address ‘ftp.wwp
Public bug reported:
After performing an autoinstall with Ubuntu Server ISO and rebooting,
trying to automate the installation of ubuntu-desktop-minimal causes DNS
settings to be lost.
For our specific use-case, we are installing ubuntu server (fully automated),
then using Puppet to install desk
tput (journalctl -u systemd-resolved -b > resolved.log).
>
> ** Changed in: systemd (Ubuntu)
> Status: New => Incomplete
>
--
James McKenzie
Linux Support Officer
EMBL-EBI ITS ServiceDesk Team, Thornton Building, AC265
European Bioinformatics Institute (EMBL-EBI)
Wellcome
Yeh it's maybe a bit of a niche deployment. If it helps, the goal here is to
fully automate the deployment of Ubuntu desktop and automatically enroll with
our Puppet management system.
We've had this working in production for a couple of years now.
To answer your questions:
1. No, we only want N
** Attachment added: "resolvectl before the issue occurs"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097769/+attachment/5856470/+files/resolvectl_before.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Attachment added: "resolvectl after the issue occurs"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097769/+attachment/5856471/+files/resolvectl_after.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Attachment added: "systemd-resolved log for the entire duration"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097769/+attachment/5856472/+files/resolved.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
These are just a few other commands I ran after the issue occurs.
By this point in the deployment we have written our own netplan config,
but it isn't applied until the reboot.
systemd-networkd and NetworkManager are both running at this point, but
networkd has control of the ethernet interface
Thanks Manuel,
Yeh I noticed this change as well. Although the netplan file on its own
shouldn't change anything until "netplan apply" is run.
So I guess "netplan apply" is being executed as part of ubuntu-desktop-
minimal or one of its dependencies?
Installing network-manager on its own doesn't
Yes you're right about the Desktop ISO. When last I checked, it only
supported partial autoinstall support. I might use that in future.
But I do still think there could be something wrong here.
The main issue is quite reproducable and the behaviour is different
between 22.04 and 24.04.
On a fres
Public bug reported:
Audio is working fine on kernel 6.8.0-49 or lower. But after upgrading, I am
getting constant crackling or distortion in any audio source on my computer.
I have confirmed the issue by rolling back to a previous kernel version.
It's the same for any music/video file I play, a
I've attached the output of `journalctl -u systemd-networkd -u
NetworkManager -b`
Just FYI, this is taken from a fresh VM with a basically default Ubuntu Server
24.04 installation after installing ubuntu-desktop-minimal.
I had to push some workarounds in our production deployment and I encountere
16 matches
Mail list logo
