** Changed in: hwe-next
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043786
Title:
RTL8111EPP: Fix the network lost after resume with DASH
To manage
Public bug reported:
Hi,
Ubuntu 24.04
Gimp from repositories, installed as a .deb ( not snap ).
It crashed when I save as
Fortunately enough, the .png image has been saved and on next Gimp
launch it offered to restore the work in progress ( I did not know Gimp
can do that ! )
```
GNU Image
** Changed in: hwe-next
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047389
Title:
Fix AMDGPU crash on 6.5 kernel
To manage notifications about this
Public bug reported:
Ubuntu Noble Numbat (development branch) x86_64
The problem is this: there is an error with the Wi-Fi driver MT7921
[ 825.412953] mt7921e :04:00.0: Message 00020007 (seq 8) timeout
[ 825.413273] mt7921e :04:00.0: PM: dpm_run_callback():
pci_pm_resume+0x0/0x110
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059738
Title:
It also concerns « regular » Ubuntu 24.04
The reboot or shutdown hangs on for minutes ( ~5 min ) on ( maybe )
unmounting some snap :
Job run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount/stop running
(4min / 4min 33s)
I can also see this kind of warnings :
evict_inodes inode
Well this error appears after suspend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059744
Title:
kernel bug 6.8.0-11 Ubuntu 24.04 with MT7921
To manage notifications about this bug go to:
before the patch log
** Attachment added: "beforePatchLog.txt"
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744/+attachment/5760398/+files/beforePatchLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059738
Title:
It's been a while. Is this still an issue?
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768961
Title:
xdg
Seems Nautilus in 24.04 still has the same behavior :
no bookmarks shown when right clicking its icon in dash
unless
nautilus is already running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi,
Ubuntu 24.04
For years now, it's very uncomfortable to (try) to use gdebi because the
« details » window can't be resized.
Attached is a funny example where there 480 packages to remove,
but the « details » can only 2 lines of the list…
ProblemType: Bug
DistroRelease:
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to
Creo, Adolfo Jayme que no es la forma correcta de cerrar este bug. Yo
también lo estoy sufriendo ahora mismo y si se le hubiera dedicado un
poco mas de tiempo usuarios de la comunidad habrían encontrado ayuda
aunque hayan pasado varios años.
--
You received this bug notification because you are
** Changed in: unity-scope-home (Ubuntu)
Status: New => In Progress
** Changed in: unity-lens-music (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: unity-lens-files (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: unity-lens-applications (Ubuntu)
Before the report sends, it certainly does say that it will open the
report in the web browser. If one's paying attention, one should realize
they don't have one. It actually tells you this twice. If you go all the
way through, you do get xdg-open's usual "no method" complaint.
For that matter,
The p7zip dependency was Debian-only so there is nothing at all to fix
on the Ubuntu side. Therefore, I am closing this bug.
** Changed in: file-roller (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
unity-lens-video is building just fine, marked as invalid. The other
four are suffering from Vala incompatibilities and I'm working through
them now.
** Changed in: unity-lens-applications (Ubuntu)
Status: New => Fix Committed
** Changed in: unity-lens-files (Ubuntu)
Status: New =>
Public bug reported:
Recent changes to the dhcpd hook shipped with dhcpdinitramfs-tools
0.142ubuntu23 (noble-dev) copy the host /etc/passwd into the initramfs-image:
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
Last observed on Lubuntu Noble Numbat 24.04 Daily Build noble-desktop-
amd64.iso 2024-03-28 both in the Live USB boot and installed to SSD
(eMMC).
For some reason this build wont let me generated ubuntu-bug files as it
reports
*** Collecting problem information
The collected information can be
Patch for updating the changelog to cover the added function as well as
the new apparmor directory
** Patch added: "LP2059730.patch"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+attachment/5760382/+files/LP2059730.patch
--
You received this bug notification because
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
All autopkgtests for the newly accepted linux-meta-azure-6.5
(6.5.0.1018.19~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-azure-6.5/unknown (arm64)
Please visit the excuses page listed below and investigate the
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
Patch for updating the changelog to cover the added function as well as
the new apparmor directory
** Patch added: "LP2059730.patch"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+attachment/5760381/+files/LP2059730.patch
--
You received this bug notification because
Public bug reported:
[Overview]
I have been testing installations of a number of Lubuntu and Xubuntu Noble
Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more
latterly focused on Lubuntu.
It would appear that since introduction of Kernel 6.8 into the daily
builds,
Public bug reported:
wont let me upgrade from 22.04-23.10
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Ubuntu 24.04 installed today.
Firefox autonomous archive downloaded from
https://www.mozilla.org/fr/firefox/all/#product-desktop-release
And « ooops… » in any tab,
terminal says :
[Parent 5931, IPC I/O Parent] WARNING: process 6020 exited on signal 11: file
Public bug reported:
Hello,
Via apt, I installed ganglia-monitor on a machine running Ubuntu 22.
ganglia-monitor contains a gmond service. Normally(?) install puts a
config file for gmond in /etc. Details online
https://github.com/ganglia/monitor-core/wiki/Ganglia-Quick-Start
So far as I can
** Description changed:
When running Ubuntu Noble in an arm32 Docker container, on certain hosts
(Azure VM CI agents), tar fails to extract certain archives that include
folders with specific permissions set.
Here's a concise repro. The error occurs in when building the
Dockerfile. I
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059346
Title:
convert autostart applications to LXQt modules
To manage
Oops sorry about that. We don't really have anyone on the team who's
really a graphic design expert. Heck, I had to look up what WCAG was.
This is a reasonable change, I think.
now that you've shown yourself to be a mindful graphic designer and one
capable of creating a patch, no less, you want
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046383
Title:
lubuntu - minimal install ; no browser means
I'm going to mark lubuntu-default-settings as incomplete here. I'm not
sure I entirely see how it's relevant. It's not clear to me that LXQt is
to blame, either, as those upstream issues are now closed/fixed. The
Openbox bug upstream is untouched, though. I'm guessing that's where the
problem
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876714
Title:
xscreensaver unlock screen has too low contrast
To
I have uploaded c2esp 27-11ubuntu4 now.
In the code of c2esp I have found some logging statements which cast
pointer addresses to long int. Probably this works only on 64-bit and
not on 32-bit and so caused the crashes in the autopkgtest. I could not
test whether it is really the fix, I am simply
AFAIK the default behavior when starting X is to read .xsessionrc and
then start the session. That ALWAYS means that anything in the session
environment (as is this case) that conflicts with .xsessionrc is going
to take precedence. This is true in Debian as much as it is in Ubuntu
and I'm sure
This bug was fixed in the package jruby - 9.4.6.0+ds-1ubuntu3
---
jruby (9.4.6.0+ds-1ubuntu3) noble; urgency=medium
* Update libfixposix dependency to time64_t variant
-- Gianfranco Costamagna Wed, 20 Mar 2024
07:56:30 +0100
** Changed in: jruby (Ubuntu)
Status: Triaged
This bug was fixed in the package google-android-installers -
1707406511ubuntu3
---
google-android-installers (1707406511ubuntu3) noble; urgency=medium
* d/scripts/run_after_dh_prep.sh: fix version constraint on
Conflicts/Provides to not block upgrades (LP: #2056080)
*
Rudra, you are correct. The version installed for me is still from Mint
PPA. It shows as "local install" in Synaptic as I had already removed
the Mint PPA some time ago. Clearly it never got updated from Ubuntu
repo since it was replace by Mint package. Thanks for looking into this
and alert
We stopped using biwidth fonts in Noble:
https://git.lubuntu.me/Lubuntu/lubuntu-default-settings/commit/7e2b7a49ee874897b8c8f1156ef8893cd6b1e43a
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
It certainly was the case that the old configuration didn't work for the
Firefox snap and it just sorted of failed silently meaning that it read the
configuration, didn't find the path specified, and simply just did not include
the icon rather than warning about the problem. It went unnoticed
These shortcuts that can be defined in lxqt-runner and lxqt-panel aren't
immediately obvious to me. If this is still an issue, can you elaborate
with some clear examples so we have clear steps to reproduce the issue?
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New =>
** Also affects: fwbuilder (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: fwbuilder (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: fwbuilder (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960823
Title:
After upgrade from Lubuntu Impish 21.10 to Lubuntu
Problem seems to be rather the broken cups.pc file from Debian in the
cups package, which is fixed in 2.4.7-1.2ubuntu2, as after this cups
release the tests of said packages have passed.
** Package changed: libcupsfilters (Ubuntu) => cups (Ubuntu)
** Changed in: cups (Ubuntu)
Status:
** Also affects: pathological (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976312
Title:
[ubuntu 22.04LTS jammy] Pathological wont
I'm going to assume this is no longer an issue in Lubuntu, but feel free
to respond with the affected version if I'm incorrect.
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Lubuntu no longer uses LXDE so I'm going to drop lubuntu-default-
settings.
** Changed in: lubuntu-default-settings (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: fwbuilder (Ubuntu)
Status: Confirmed => In Progress
** Changed in: fwbuilder (Ubuntu)
Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963672
Title:
Firefox web browser listed twice on
** Changed in: pathological (Ubuntu)
Status: Confirmed => In Progress
** Changed in: pathological (Ubuntu)
Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2036098
Title:
[mantic] xdg-desktop-portals no longer
Public bug reported:
When running Ubuntu Noble in an arm32 Docker container, on certain hosts
(Azure VM CI agents), tar fails to extract certain archives that include
folders with specific permissions set.
Here's a concise repro. The error occurs in when building the
Dockerfile. I can only get
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045384
Title:
AppArmor patch for mq-posix interface is missing in jammy
To manage
1. Yes. The backport was for 5.15 jammy kernels including HWE
derivatives. The user space SRU was done in bug
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146
which included Focal. The intent being Focal will only support mqueue if
it is using and HWE kernel.
2. Yes that makes
** Changed in: lubuntu-default-settings (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843831
Title:
kubuntu-settings-desktop and some other
This bug was fixed in the package python-pysaml2 - 7.1.0-0ubuntu3
---
python-pysaml2 (7.1.0-0ubuntu3) noble; urgency=medium
* Drop build-dependency on python3-future, no longer needed
(LP: #2051564)
-- Graham Inggs Sat, 23 Mar 2024 16:47:15 +
** Changed in:
I can reproduce the error on Focal, Jammy and Mantic. Could not test on
Noble as its uninstallable until time_t transition is over.
** Changed in: fwbuilder (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu-mate-settings (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058659
Title:
[UIFe] Ubuntu MATE bootstrap slideshow incomplete
This bug was fixed in the package black - 24.2.0-1ubuntu1
---
black (24.2.0-1ubuntu1) noble; urgency=medium
* d/test/control: drop unused dependency on python3-typed-ast, which was
dropped from the archive. (LP: #2058692)
-- Olivier Gayot Thu, 21 Mar 2024
23:05:19 +0100
**
This issue is still present upstream, so I reported it to the original
committer of the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058557
Title:
Kernel panic during checkbox
It's reverted in Debian
https://tracker.debian.org/news/1515519/accepted-xz-
utils-561really545-1-source-into-unstable/
Though from the changelog I didn't see the reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: pngphoon (Debian)
Importance: Undecided => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059140
Title:
pngphoon: FTBFS on arm{el,hf}: tws.c:40:13: error: conflicting
Public bug reported:
Please sync gopacket 1.1.19-6 (universe) from Debian unstable (main)
Changelog entries since current noble version 1.1.19-4build1:
gopacket (1.1.19-6) unstable; urgency=medium
* Fix missing endif
-- Shengjing Zhu Thu, 28 Mar 2024 16:51:11 +0800
gopacket (1.1.19-5)
This bug was fixed in the package boxer - 1.4.3-1ubuntu1
---
boxer (1.4.3-1ubuntu1) noble; urgency=medium
* d/control: remove boxer-data from Recommends: it is not present in
Ubuntu (LP: #2058853).
-- Vladimir Petko Mon, 25 Mar 2024
08:25:26 +1300
** Changed in: boxer
Thanks, I hope to have some time in April to check it out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682927
Title:
lubuntu-rc.xml config breaks focusNew config
To manage notifications about
Anyone looking into this? I get this a few times a week especially with
multiple chromium based applications open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057155
Title:
amdgpu driver crashes
In foundations leadership sync on this today. I believe we determined
that the best course of action we should take at the moment is to pursue
an Ubuntu downstream needrestart patch to register cloud-init system
services as skipped during automatic restarts when apt commands are run
in
1 - 100 of 422 matches
Mail list logo
