Public bug reported:
Description:Ubuntu 22.04.4 LTS
Release:22.04
PACKAGE VERSION
ubuntu-drivers-common:
Installed: 1:0.9.6.1
Candidate: 1:0.9.6.1
Version table:
*** 1:0.9.6.1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dp
Public bug reported:
When launching the game the game exit with ERROR CODE 134
This wasn't happening in ubuntu 24.04
Here is the bug report:
https://securelogger.net/files/628caa63-875a-42df-bf50-9385c70c66a5.txt
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: default-jre 2:1.21-76
ProcV
I think 101 should prevent the service to start automatically (for
example in a chroot) and 0 should do nothing (for example for nginx, let
the service start) as it was the behaviour in previous releases.
https://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt
http://jpetazzo.github
Public bug reported:
Hi,
We've got an issue with Nginx and policy-rc.d on Ubuntu 24.04. Nginx
can't install when we create an policy-rc.d file with an `exit 0` code.
Here is the steps to reproduce :
1. Install Ubuntu 24.04 Live Server from the ISO.
2. Connect to the machine via SSH.
3. Create a
Hey there Nick,
Just chiming in from the FIPS-side of things, you are correct that FIPS
isn't available for Noble yet. That's likely more than a year out still
(hopefully less, though). FIPS will never make it to Oracular however,
since FIPS is only for LTS releases.
--
You received this bug not
Public bug reported:
Hello!
I'm opening this LP to begin the discussion for consideration of
implementing the Python Plugin API (documented here[1]) into our sudo
package. We have received requests for this from some customers, and
other distros (RHEL[2], namely, apparently as of 9.x) have implem
Public bug reported:
I was working with raylib, and when i open task manager. the memory that
my program use was keep increasing, so i use libasan to check if there
is leak on my program, also using valgrind but non of them show where is
the leak. but both of them point to exact same "_XimOpenIM (
Hi Jeffrey, yes that workaround solves the problem. I should have
probably said that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 (Gen9 GPUs in 6t
lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Celeron
N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller
[8086:5a84] (rev 0b)
Subsystem: Acer Incorporated [ALI] Celeron N3350/Pentium N4200/Atom
E3900 Series Integrated Graphics Con
Installed 24.04 to a usb drive. Still flickering and with linux-
oem-6.11. Having a quick look at the patch I guess my device id is
missing. As noted in the comments above, this hits more than just
Skylake processors. I think mine is an Apollo lake.
** Tags removed: verification-needed-noble-li
I've corrected my previous message as I'm actually running 22.04. I've
tried the 6.8.0-44 kernel which still has the fault. I don't think
there are any higher packages than that in 22.04? So I manually
downloaded and installed the 6.11.0-1004-oem and 6.11.0-6 kernels from
24.04/24.10, but these
I believe I have this bug with my N4200 Acer swift laptop. I was
convinced it was a hardware problem. Screen flashing (the picture gets
stretched and repeated horizontally while flashing) when the mouse
pointer is at certain positions in the screen. It is easily repeatable
in Lubuntu 24.04 with
** Description changed:
After upgrading from Ubuntu 22.04 to Ubuntu 24.04, when I try to connect
to the L2TP/IPSec VPN configured earlier in Ubuntu 22.04 and which
worked, I get an error in the syslog: "pppd: peer does not want to
authenticate us with eap".
The remote L2TP/IPSec serve
L2TP/IPSec is still a very popular VPN use case scenario, so this issue
may affect many users who will decide to upgrade Ubuntu from 22.04 to
24.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/207852
The configuration change was necessary after the Ubuntu update from
version 22.04 to 24.04. Otherwise, the previous working configuration
will no longer work. So, some kind of configuration change mitigation
should be implemented in the Ubuntu update scripts.
--
You received this bug notification
Public bug reported:
After upgrading Ubuntu 22.4 to 24.04, you cannot upgrade or remove the
lazarus-src-2.2 package previously installed in Ubuntu 22.04:
$ sudo apt autoremove
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności... Gotowe
Odczyt informacji o stanie... Gotowe
Następujące p
I found the NetworkManager-l2tp bug report on github
(https://github.com/nm-l2tp/NetworkManager-l2tp/issues/230) that helped
me fix the problem. I disabled MPPE and only checked the MSCHAPV2
checkbox, now I can connect.
** Bug watch added: github.com/nm-l2tp/NetworkManager-l2tp/issues #230
http
Public bug reported:
After upgrading from Ubuntu 22.04 to Ubuntu 24.04, when I try to connect
to the L2TP/IPSec VPN configured earlier in Ubuntu 22.04 and which
worked, I get an error in the syslog: "pppd: peer does not want to
authenticate us with eap".
The remote L2TP/IPSec server (1.1.1.1) is
> I'll change unmkinitramfs to use 3cpio in case it is installed.
It does not solve the problem reported in this bug. How would one know
unmkinitramfs is dead slow because 3cpio is not installed? Mby you
should make initramfs-tools-core depend on rust-threecpio?
--
You received this bug notifica
For additional information, this is being configured in netplan. Here is the
relevant (obfuscated) section of that configuration:
---
auth:
key-management: 802.1x
method: tls
ca-certificate: /var/my_dir/net/certs/CA.pem
client-certificate: /var/my_dir/net/certs/Wo
Public bug reported:
Hello,
It would seem that wpa_supplicant, when used on a wired connection for 802.1x
authentication, does not operate correctly on a Jammy system when FIPS is
enabled (either fips or fips-updates). It's unclear what precisely is going on,
but based on the logs we've seen t
Public bug reported:
Hello! When one enables FIPS mode on a Jammy system and then attempts to
use paramiko in Python, the module crashes with the following output:
---
root@jipster:~# cat /proc/sys/crypto/fips_enabled
1
root@jipster:~# python3
Python 3.10.12 (main, Nov 20 2023, 1
Dmesg output attached.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2072643/+attachment/5795864/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Also a photo of camera app. Not only tests fail but it doesn't work in
real life.
** Attachment added: "Clipboard01.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2072643/+attachment/5795847/+files/Clipboard01.jpg
--
You received this bug notification because you ar
** Tags added: cert-sru regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072643
Title:
Embedded camera won't work.
To manage notifications about this bug go to:
https://bugs.launc
Public bug reported:
Description:Ubuntu 22.04.4 LTS
Release:22.04
linux-oem-22.04d 6.5.0.1026.28
com.canonical.certification::camera/camera-quality_video0 test fails:
[ WARN:0] global ./modules/videoio/src/cap_gstreamer.cpp (1100) open OpenCV |
GStreamer warning: Cannot query video
Hello, I see https://bugs.launchpad.net/bugs/2071747 was marked as a
duplicate of this bug. It has the same effect but I think it has a
separate cause. IIUC, this bug was related to netplan running udevadm,
whereas 2071747 is related to a recent CVE fix[1] in which netplan
itself tries to chown a f
Public bug reported:
A recent patch appears to chown networkd-related files to `root:systemd-
network`[1]. If nsswitch.conf is configured with `group: systemd files`,
this appears to create a circular dependency as systemd relies on
netplan via systemd-networkd. On the next `systemctl daemon-reloa
-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:adam 7309 F pipewire
/dev/snd/controlC0: adam 7313 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Jun 16 14:35:36 2024
After looking deeper into the repo history, I see the questionable
implementation of pgrep_exe() was introduced by this patch
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/comments/11
in attempt to adopt the debian code to the ubuntu environment. Aside for
other things, it ignores
Commenting on #2:
When building busybox, there is a number of config switches. For your binary to
support "ps -w" you need this in the config:
- CONFIG_DESKTOP is not set
- CONFIG_FEATURE_PS_WIDE=y
On my 22.04 systems I've got 2 busybox binaries: /usr/bin/busybox (2.1M)
from busybox-static packa
Coming here from my dup bug report 2060971. Can confirm that the newer
version of update-manager seems to fix the issue. And indeed, my
livepatch install is a little jankey on my system for some reason, but
instead of being greeted with a crash every morning, I'm now presented
with pending updates
Following up again. Disabling retries reduced the frequency of this bug,
but didn't eliminate it.
On the other hand, the patch I shared does seem to fix the bug. No
occurrences since we shipped it ~2 weeks ago. I encourage others to try
it out.
--
You received this bug notification because you a
Public bug reported:
nvme shows that power management is enabled and device is most of the
time in power state 4, but disk get hot (+50.9°C) and drains battery.
The same disk has much lower temperatures (about 35C, similar to
mainboard) when running Kubuntu 23.10
root@nevo:~# uname -a
Linux nevo
Hi Grant!
I keep my system updated regularly, but indeed I'm on slightly older:
---
:~$ dpkg -l|grep update-manager
ii python3-update-manager 1:22.04.19
all python 3.x module for update-manager
ii update-manager
FWIW, this is what we did in Fedora:
https://src.fedoraproject.org/rpms/fail2ban/c/24c973f252f6d1b4231ee49ee4d5efac785a2fe8?branch=rawhide
i.e., we depend on packages of the asynchat and asyncore libs that were
added to pypi for this kind of purpose -
https://pypi.org/project/pyasynchat/ and
https
Public bug reported:
the problem occurred during installation while trying to remove previous
package
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Li
OK, so I just tried this out on the same host I did my Fedora 40
testing, a Windows 11 23H2 system with Intel graphics (no NVIDIA) and
VMWare Player 17.
I grabbed the Ubuntu 24.04 beta desktop image - ubuntu-24.04-beta-
desktop-amd64.iso - and booted it. From that environment I could
reproduce the
FWIW, I did my testing - which found this is broken for a Fedora 40
guest with mesa 24.0.4, but fixed with 24.0.5 - on a Windows 11 (23H2)
host. No idea what's different for Oliver, sorry :(
I guess I could try with an Ubuntu guest on my test setup, I've got a
bit of spare time today.
--
You rec
@mdeslaur did you mean to set this bug invalid? It looked like you
intended to set bug #2060968 instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060906
Title:
attempt to add opensc using modu
I'm on 22.04.4, I have an i3-8100 processor (does not support turbo),
and I was previously running into this issue. After installing the
updated ppd from your PPA, I am no longer seeing this, and I am able to
switch to performance mode. Thank you for the fix!
--
You received this bug notification
> I have implemented the listing of uncompressed cpio archives (roughly
120 lines of code). Now I have to add the decompression support
Finding offsets of the embedded archives is the only time consuming part
of the whole script. Mby it is better to create a separate tool, say
"scaninitramfs", to
> isn't really an intended use-case
But there is /boot/grub/loopback.cfg since at least 14.04!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060168
Title:
Prebuilt signed grub images should includ
> any practical utility
Recent ubuntu desktop iso images are way over 4Gb in size, which is the
max file size for fat32. Fat32 for long time was the obvious choice to
keep iso images on.
Exfat is of interest for those who still need compatibility with
w/ndows, like it was with fat32.
F2fs is of
Public bug reported:
I guess this is the correct source package to send a feature request for
debian/build-efi-images script.
Here is what I ask for:
--- build-efi-images
+++ build-efi-images.new
@@ -101,7 +101,9 @@
echo
efifwsetup
efinet
+ exfat
ext2
+
The script from the post is deprecated now, I converted it into a
generic "make casper aware of fs X, add kernel modules Y to the initrd"
one.
You can get it here https://github.com/slowpeek/ubuntu-remaster-bbb and
make 14.04+ images bootable from f2fs like this:
ubuntu-remaster-f2fs input.iso
Previously I created a script to make ubuntu iso images bootable from
f2fs partitions. After discovering this bug, I converted it into a
generic "make casper aware of fs X, add kernel modules Y to the initrd"
one.
You can get it here https://github.com/slowpeek/ubuntu-remaster-bbb and
make 20.04+
Public bug reported:
Since 23.10 the initrd consists of 4 embedded cpio:
- amd microcode
- intel microcode
- firmware + kernel modules
- rest (compressed)
Previously it was:
- amd microcode
- intel microcode
- rest (compressed)
There is no archive size header for cpio, so unmkinitramfs has to pa
Public bug reported:
Crash on install - See logs
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.20
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: a
Following up, `Acquire::Retries=0` seems to be avoiding the bug in prod,
which strengthens my suspicion that it's related to retries.
As for the actual bug, when apt is hanging, I notice that the work queue
has items in it, but they have not been delegated to a worker. There is
a condition that is
@Adrian Feliks (mexit)
I've just filed a similar bug about f2fs. The module is in initrd since
20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038694
Title:
Now that exfat filesystem is in the
** Description changed:
Ubuntu iso images bundle the f2fs driver in initrd since 20.04, but
casper does not recognize f2fs as a supported fs even in 24.04. Hence,
the images cant loop-boot from f2fs partitions.
A 2-lines change is all that's required since 20.04 (casper-helpers
since
@Adrian Feliks (mexit)
How is it supposed to work with just that? Looking into initrd of 24.04
daily unpacked with unmkinitramfs. According to
main/lib/modules/6.8.0-11-generic/modules.builtin, exfat is not a
builtin module. And there is no exfat in
early3/usr/lib/modules/6.8.0-11-generic/kernel/f
Public bug reported:
Ubuntu iso images bundle the f2fs driver in initrd since 20.04, but
casper does not recognize f2fs as a supported fs even in 24.04. Hence,
the images cant loop-boot from f2fs partitions.
A 2-lines change is all that's required since 20.04 (casper-helpers
since 22.04, previous
Public bug reported:
Crash during install attempt. Crashed after names selection and writing
to disks. No clear error reason. See logs. No odd options selected
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.20
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Un
Hello, also affected by this.
I'm able to reproduce the bug using Walter's mock server. I suspect it
may be related to the retry code that kicks in when a transient error is
encountered (like a 503). Retries are enabled by default since apt
2.3.2, which seems to fit the regression window people ha
Public bug reported:
Hi,
We found an issue in `initramfs-tools-core` (noble,now 0.142ubuntu20
all) related to this change :
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024164
(dhclient replaced by dhcpcd).
dhclient was faster to give an IP. In the `initramfs-tools-core`
scrip
** Description changed:
Howdy!
- I have a customer in case 00381750 requesting a time frame for when
- Octavia 10.1.1 can be SRUed, as they mentioned they are interested in
- some fixes included in that version for issues they are experiencing.
- I'm having trouble finding when that version w
This bug also prevents an ubuntu-server noble autoinstall installation
with NVMe disks attached via PCIe. Noble 20230223.
My configuration was a simple storage: direct, with a disk: match
specifying 'smallest' and 'ssd: true' (I have 3 NVMe drives, one 128 GB
for OS, two 3.6TB for data.).
Mine is
Public bug reported:
Ubuntu 22.04.4 LTS
NVIDIA driver metapackage from nvdia-driver-470 (proprietary,tested)
crashes regurarly (static image )
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-515 (not installed)
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
U
https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/92
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055055
Title:
unmkinitramfs: wrong and unneeded count= in a dd call
To manage
> The count_bytes solution looks better to me
The updated patch is attached.
I've just checked: all the *_bytes flags were introduced to dd in the
same commit
https://github.com/coreutils/coreutils/commit/140eca15c4a3d3213629a048cc307fde0d094738,
so it is safe to throw in count_bytes in the mix.
Just found out, aside for skip_bytes iflag, there is also count_bytes
one. So another fix count be:
113: dd < "$initramfs" skip=$start count=$((end - start))
iflag=skip_bytes,count_bytes 2> /dev/null |
** Description changed:
Speaking about this line in unmkinitramfs:
- 113: dd < "$
Public bug reported:
Speaking about this line in unmkinitramfs:
113: dd < "$initramfs" skip=$start count=$((end - start))
iflag=skip_bytes 2> /dev/null |
dd's block size is 512 by default. iflag=skip_bytes does not change that. Both
$end and $start are byte-offsets. Hence the count is ($en
@ddstreet: no, I failed to get a sponsor, despite subscribing the bug to
~ubuntu-sponsors. I may be doing something wrong as I haven't ever done
such a sponsored upload to Ubuntu directly.
The code works on Focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Ok, don't know which package produce that value in debconf passwd/user-
password-crypted but when I reset it using debconf-communicate,
installation was completed. Unfortunately system not booted
successfully, so I will dig deeper in the future. Maybe it's not a bug
then, but maybe some validation
Check once again. I can install jammy on that VM without touching
anything in the VM settings. Just boot, proceed all unnecessary for
normal Ubuntu steps from my case, and start ubiquity the same way.
Installation was successful but in logs there are all that access denied
messages. I can upload th
Once again, steps that I performed:
1.) boot VM from skywavelinux-4.3.0-flashback.iso
2.) setup internet connection manually
3.) sudo apt-get update
4.) sudo apt-get install ubiquity ubiquity-frontend-gtk
ubiquity-frontend-gtk-panel ubiquity-slideshow-ubuntu ubiquity-casper
5.) sudo mount /dev/lo
This is a virtual drive. And I was able to install focal and jammy on
the same setup normally.
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Incomplete
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Ne
Ok, I read the logs once more. The error string for usermod was in fact
"10 passwd/user-password-crypted-casper-backup doesn't exist" so it is
the other field that I provide from frontend which was "passwd/user-
password". So the filed is in fact missing? But error handling here
still can be handy.
I know that it is the problem with other Ubuntu based OS, but thing I
address is bug with error handling in ubiquity itself. I think it should
throw and error at the beginning when it got error when trying to
preseed (I guess) the 'passwd/user-fullname' or in best case use
password I chose in front
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/1976177/+attachment/5593616/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197
apport information
** Attachment added: "UbiquityPartman.txt"
https://bugs.launchpad.net/bugs/1976177/+attachment/5593615/+files/UbiquityPartman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "UbiquityDebug.txt"
https://bugs.launchpad.net/bugs/1976177/+attachment/5593614/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19761
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1976177/+attachment/5593613/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Tags added: apport-collected third-party-packages
** Description changed:
System: Skywave Linux Flashback Release: 4.3.0 - this is a Focal Remix
live-cd based on Ubuntu 20.04.4 (https://skywavelinux.com/)
Ubiquity Version: 20.04.15.19
I want to install this li
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1976177/+attachment/5593612/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976177
Public bug reported:
System: Skywave Linux Flashback Release: 4.3.0 - this is a Focal Remix
live-cd based on Ubuntu 20.04.4 (https://skywavelinux.com/)
Ubiquity Version: 20.04.15.19
I want to install this live distro on VM (standalone HVM on Qubes OS -
but I think this not make any difference).
Should these updates appear automatically at one point or do I have to
activate some repos or so?
I'm still having the same issues like others as well:
https://stackoverflow.com/questions/71987581/openssl-3-0-error-when-
booting-vagrantbox
--
You received this bug notification because you are a
** Changed in: maas
Status: Triaged => Fix Released
** Changed in: maas
Milestone: None => 3.0.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890803
Title:
Groovy amd64 / arm64 / Power
Finally got the crashdump uploaded but had to add all the details to a
new ticket: LP#1973615
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972812
Title:
gnome-shell (X11, nvidia-390) crashes with
Still having upload trouble, i'll find a way to get a crash-report
through another means
** Attachment added: "upload failure crash report"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+attachment/5589244/+files/Screenshot%20from%202022-05-12%2008-47-13.png
--
You recei
I removed one of the extensions i was using, but still am running into
the issue.
1) I've got a crash report that still fails to upload.
```
-rw-r- 1 addyess whoopsie 94220558 May 12 08:03
_usr_bin_gnome-shell.1000.crash
-rw-rw-r-- 1 addyess whoopsie0 May 12 08:03
_usr_bin_gnome-
I'll attach mine since it was asked. However mine is a very old original
installation and I can't remember the complete history of what I've done
with snap.
** Attachment added: "upgrade log from an old installation"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/197198
I have a crash report for gnome-shell as well -- but i can't seem to get
it uploaded to launchpad at the moment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972812
Title:
The operating system does
Another "side-effect" of this event is that the screen will instantly go
black after 30 idle seconds (it doesn't dim to black or use my normal
screen blank at 3 min inactivity setting). This "side-effect" goes away
if I log-out of the gnome session and then back in again.
--
You received this bu
This happens to me as well. These are the loaded extensions.
~/.local/share/gnome-shell/extensions
❯ /usr/bin/cat **/metadata.json
{
"_generated": "Generated by SweetTooth, do not edit",
"description": "A human-readable clock for the gnome-shell panel",
"name": "Fuzzy Clock",
"shell-versi
** Description changed:
I'm in Brussels, setting up a fresh new Xubuntu 22.04 LTS system that
otherwise so far respects my settings of en-GB (with a UK keyboard)
Panel clock for some reason provides a date in Dutch. (mandaag 09 mei
2022) and it is not obvious how to persuade it to do ot
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04
$ apt-cache policy imv
imv:
Installed: 4.3.0-1build1
Candidate: 4.3.0-1build1
Version table:
*** 4.3.0-1build1 500
500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
This is apparently an issue with misconfigured locale. I'm not sure if
this was set automatically (making it an Xubuntu installer bug) or if I
inadvertently clicked OK on some "helpful" suggestions (though given I'd
specified that I was asking the system to be in English it seems a
slightly odd def
OK, on looking more closely at the whois for my IP address, there are
two addresses in Wallonia (Liege and Charleroi, both francophone) and
one in Brussels-capital-region. Point stands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
I'm in Brussels, setting up a fresh new Xubuntu 22.04 LTS system that
otherwise so far respects my settings of en-GB (with a UK keyboard)
Panel clock for some reason provides a date in Dutch. (mandaag 09 mei
2022) and it is not obvious how to persuade it to do otherwise.
I n
Sorry, I have changed it from Fix Commited to Fix Released by mistake
but I cannot change it back. Sorry!
** Changed in: xl2tpd (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: maas
Status: Expired => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage notifications
Hi! Same problem here. Clean install, Nvidia-510 + new updates. GTX 960M
Still cannot login Wayland sessions on 22.04 after the updates. Missing Wayland
login option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Hi! Same problem here. Clean install, Nvidia-510 + new updates. GTX 960M
Still cannot login Wayland sessions on 22.04 after the updates. Missing Wayland
login option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 1968929 ***
https://bugs.launchpad.net/bugs/1968929
Hi! Same problem here. Clean install, Nvidia-510 + new updates. GTX 960M
Still cannot login Wayland sessions on 22.04 after the updates. Missing Wayland
login option.
--
You received this bug notification
Public bug reported:
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010059. Affects
Jammy and Bookworm as far as I can tell.
echo | sudo whiptail --msgbox test 20 20 #Can't select 'Ok'
echo | whiptail --msgbox test 20 20 #Can select 'Ok'
Tested on Ubuntu 22.04 LTS
** Affects: newt (Ubu
+1 to this until (at minimum) the below issues are resolved:
=> https://bugs.launchpad.net/snapd/+bug/1575053
=> https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706
Seeing these issues open for so long is worrying to me, considering a
growing number of critical packages such as Firefox a
Still affects Ubuntu Server 22.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674492
Title:
cron: /etc/default/cron should not actually be deprecated
To manage notifications about this bug g
1 - 100 of 24170 matches
Mail list logo
