This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1008.8~22.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-jammy-linux-
nvidia-6.8' to
** Merge proposal linked:
https://code.launchpad.net/~adrien/ubuntu/+source/therion/+git/therion/+merge/467694
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069714
Title:
therion:
Public bug reported:
Copy and paste it anywhere on the system.
Notice that the new item does not appear until you press the F5 button.
Expected behavior: The new file or directory should appear immediately after
creation or pasting.
Actual behavior: The new file or directory only appears after
** Changed in: git (Ubuntu)
Status: New => 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/2069293
Title:
Autopkgtests failing due to new git 2.45
To manage notifications about
** Bug watch added: Debian Bug tracker #1072828
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072828
** Also affects: texlive-bin (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072828
Importance: Unknown
Status: Unknown
** Summary changed:
- therion:
** Changed in: git (Ubuntu)
Status: New => 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/2069304
Title:
Autopkgtests failing due to new git 2.45
To manage notifications about
Public bug reported:
Steps to reproduce:
Right-click on an item on the desktop and select "Rename".
After renaming, click the left or right mouse button.
Notice that clicking left performs an "Enter" action, and clicking right moves
the cursor left or right.
Expected behavior: Clicking left or
Hi Gabriel,
Thanks for your proposed solution. While this may be fine for end users to do
so, let me highlight some things people should know if they read this:
* This is a manual solution that could be applied to a system, but please take
good care in checking that removing `firefox` doesn't
Do you have some custom config maybe in ~/.gnupg? Does it behave
differently with a new user account on the same machine.
scdaemon is used for smartcard authentification, it shouldn't be needed
in a standard setup
Note that scdaemon is in universe so we would need to get it promoted to
main
Public bug reported:
During upgrade using `sudo do-realease-upgrade`
Upgrade failed and system became unbootable.
Booting into recovery mode discovered that kernel make fails (linux-
image-6.8.0-35-generic) for module evdi which is the Dell DisplayLink
Driver
Solution:
1) Boot into recovery
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/2069715
[Impact]
Install Focal with FIPS enabled on AMD EPYC 7262 8-Core Processor, kernel panic
happens during boot:
[3.430477] ima: Allocated hash algorithm: sha1
[3.433358] ima: No architecture policies found
[
I am also seeing this on two separate systems, while upgrading from
22.04 to 24.04. On the first system, with less packages installed the
process took about 2 hours. On the second system, based on the current
progress I estimate that it will take around 14 hours.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The therion package fails to builds. It might be related to vtk9 9.3
since it started with this transition but the issue is a missing font
file (logo10 at 600dpi) for latex which is not completely consistent
with that. Since this file is required only if other font files are
Hi Mitchell,
if you are not using the "nfs_shared_infodir" parameter, removing the
init script is sufficent.
However, if the parameter is used an a custom place is provided
do_unbind will make an uncecked umount of /var/lib/nfs. Any issues there
will not return an error. This is independent of
Updated branch links to have correct (new) naming scheme.
Thanks Dave for triggering autopkgtests. Back in January 2024 I was
still able to do it myself
(https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2045452/comments/18),
I wonder what changed.
I now checked
The verification of the Stable Release Update for linux-firmware-xilinx-
ap1302 has completed successfully and the package is now being released
to -updates. Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the
This bug was fixed in the package linux-firmware-xilinx-ap1302 -
1:2.0-0ubuntu1~22.04.1
---
linux-firmware-xilinx-ap1302 (1:2.0-0ubuntu1~22.04.1) jammy; urgency=medium
* Backport 1:2.0-0ubuntu1 to jammy (tag v2.0) (LP: #2052575)
-- Pallav Joshi Thu, 07 Mar 2024 13:46:23 -0800
This bug was fixed in the package linux-firmware-xilinx-ap1302 -
1:2.0-0ubuntu1~23.10.1
---
linux-firmware-xilinx-ap1302 (1:2.0-0ubuntu1~23.10.1) mantic; urgency=medium
* Backport 1:2.0-0ubuntu1 to mantic (tag v2.0) (LP: #2052575)
-- Pallav Joshi Tue, 09 Apr 2024 14:58:58 -0700
I have confirmed with the uploaders that the package has been verified.
Releasing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052575
Title:
[SRU] Update firmware to support autofocus
To manage
I did set up two (clean installation, fully updated) 24.04 VMs: one with
noble-proposed disabled and the other one with noble-proposed enabled.
Installed latest torbrowser-launcher on both of them.
- On the VM without noble-proposed enabled and using torbrowser-launcher
version 0.3.7-1build2,
** Changed in: dash-to-dock
Status: Unknown => 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/2069559
Title:
gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow()
Public bug reported:
OS: ubuntu 22.04, with both Hebrew and English installed. Currently
English is selected.
In Pycharm editor:
When pressing "CTRL /", the "/" key is interpreted as it was in Hebrew: "."
I opened a bug in Jetbrain and we followed it until deciding it is an OS
bug. see the
From the responses on the systemd-devel list my take is: Do not set
osVersion. The osVersion does not reflect the version of the Ubuntu
release that package is shipped by, because it can be part of multiple
releases without rebuild.
--
You received this bug notification because you are a member
Public bug reported:
[Impact]
/var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1677:9: error: implicit
declaration of function ‘strlcpy’; did you mean ‘strscpy’?
[-Werror=implicit-function-declaration]
1677 | strlcpy(info->type, (outer_addr == DDCCI_DEFAULT_DEVICE_ADDR) ?
"ddcci" :
Almost a year later - same issue. Would be nice to fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924261
Title:
Krusader: missing icons
To manage notifications about this bug go to:
Installing the scdaemon package solves the issue.
scdaemon seems to be a mandatory dependency of gpg-agent, it should be
added to the dependency chain
** Changed in: seahorse (Ubuntu)
Status: New => Triaged
** Changed in: seahorse (Ubuntu)
Assignee: (unassigned) => Alessandro Astone
Public bug reported:
In order to add OpenPGP keys to launchpad, the website guides you
through synchronizing your key with the Ubuntu key server first by using
Seahorse ("Passwords and Keys").
You can manually trigger a sync from the hamburger menu > Sync and
publish keys > Sync.
However in my
** Changed in: grub2 (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679429
Title:
UEFI tftp configuration lookup
To manage notifications about this bug go
All kernels boot fine under SB on modern Ubuntu. I don't think major
changes will be made to Xenial at this point.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu Xenial)
** Changed in: mutter (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967707
Title:
Nvidia Wayland sessions sometimes flood the log with
Thanks Joris, that worked for me to.
Best,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about this bug go to:
** Also affects: mutter (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Oracular)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Committed
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Daniel van
** Also affects: dmz-cursor-theme (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: dmz-cursor-theme (Ubuntu Oracular)
Importance: Undecided
Status: Won't Fix
** Also affects:
** Bug watch added: github.com/micheleg/dash-to-dock/issues #2179
https://github.com/micheleg/dash-to-dock/issues/2179
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/2179
Importance: Unknown
Status: Unknown
--
You received this bug notification
Just one more comment: if I connect to my Jabra via bluetooth, then
everything works fine (audio profile is "Headset Head Unit"). Connected
via usb I have audio problems (profile is "analog stereo input + mono
output"). Not sure how to debug further.
--
You received this bug notification because
Public bug reported:
[Impact]
This release sports mostly bug-fixes and we would like to make sure all of our
users have access to these improvements.
The update contains the following package updates:
* cinder 23.1.0
* ironic 23.0.1
* magnum 17.0.2
* manila 17.2.0
* nova 28.1.0
[Test Case]
** Merge proposal linked:
https://code.launchpad.net/~nteodosio/update-manager/+git/update-manager/+merge/467674
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064211
Title:
/usr/bin/update-
A bunch of ways it can happen according to the crash reports:
---
kernel: INFO: task kworker/u65:1:1093 blocked for more than 491 seconds.
kernel: Tainted: G W 6.8.0-35-generic #35-Ubuntu
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
gnome-shell[2744]: Failed
** Tags added: open-2213
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069695
Title:
[SRU] OpenStack 2024.1 point release updates
To manage notifications about this bug go to:
I have discovered that my Android phone can access rhythmbox 3.4.6 via
daap.
Working daap from rhythmbox 3.4.6
** Attachment added: "good_rb_3.4.6_debug.log"
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2068843/+attachment/5790465/+files/good_rb_3.4.6_debug.log
--
You received
Not working daap from rhythmbox 3.4.7
** Attachment added: "bad_rb_3.4.7_debug.log"
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2068843/+attachment/5790466/+files/bad_rb_3.4.7_debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm currently trying out the Ubuntu 24.04 version and encountered an issue
where modifying the SSH port didn't take effect. Fortunately, I came across
this help and followed your suggestions to attempt the modifications. The port
modification is now working as expected.
sudo vim
While I do agree that this error message is indeed unfriendly, we
ideally shouldn't expose the end user to grub-probe output anyways, and
I don't feel we should carry a downstream patch for this.
You are free to report this upstream and/or contribute a patch upstream
that changes the error
NTFS is signed in the current grub2, although it is debatable whether or
not it should be.
** Changed in: grub2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Curtin overriding /etc/default/grub via /etc/default/grub.d might not be
desirable, but it is certainly not a but in grub2.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ubuntu 14.04 is in ESM support only, please report a new bug if you are
still experiencing similar issues on modern Ubuntu
** Changed in: grub2 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm this seems related to GRUB trying to find something on a NFS (or
other network mounted) disk.
However Ubuntu 16.04 is in ESM support only, please report a new bug if
you are still experiencing similar issues on modern Ubuntu
** Changed in: grub2 (Ubuntu)
Status: New => Won't Fix
--
> Booting from 4Kn drives is and will NEVER be supported by BIOS (AKA
legacy BIOS AKA LEGACY). The ONLY solution for 4Kn AF drives is to boot
via UEFI.
I think this is going to be the case for us too. Please use UEFI to boot
4Kn drives (512e ones still work fine on BIOS)
** Changed in: grub2
Ubuntu "Precise Pangolin" is no longer supported, and Ubuntu "Trusty
Tahr" only receives ESM fixes for security problems.
** Changed in: grub2 (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: xkeyboard-config
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/327963
Title:
Error activating XKB configuration with MacBook keyboard model
To manage
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567534
Title:
Placing grub.cfg in /boot/efi causes avoidable problems on EFI-based
Looks like a reasonable solution. But why not just move the file
instead, if that's the end goal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879466
Title:
Purging grub-pc package deletes
Chainloading signed (both db and Mok) EFI loaders works fine with the
current shim+GRUB+peimage combination.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems to be caused by your terminal not being able to display the
multibyte character "…", and not a bug in GRUB2.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This seems like the BIOS failing to write to disk when trying to write
the environment block and not an actual bug in GRUB2.
Perhaps trying UEFI mode might help on newer machines.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because
@jugmac00 this got resolved along the way - that same recipe is here
now, and passing.
https://launchpad.net/~mir-team/+snap/miriway-beta
So not a Launchpad issue any more.
** Changed in: launchpad
Status: Incomplete => Invalid
--
You received this bug notification because you are a
The legacy VGA BIOS on your machine doesn't seem to support the same colour
depth as UEFI GOP does.
There isn't anything GRUB2 can do about this, and the menu is still displayed
"correctly" with just less colour depth.
As BIOS support is getting worse and worse on new machines, it is
You can re-build the current GRUB2 package multiple times. Re-
bootstrapping does change tarball files indeed, but there is not much we
can do about that.
** Changed in: grub2 (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Two GRUBs taking control "back-and-forth" is unfortunately expected, and
there isn't much that can be done with this with the current ESP layout.
** Changed in: grub2 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
See https://salsa.debian.org/grub-team/grub/-/merge_requests/62
But ideally we should just move /etc/default/grub to grub-common
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879466
Title:
Please check this still happens on a supported Ubuntu release.
** Changed in: update-manager (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/990138
Title:
** Bug watch added:
gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #112
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/112
** Changed in: xkeyboard-config
Importance: Medium => Unknown
** Changed in: xkeyboard-config
Remote watch: freedesktop.org
> You can just run grub-install once by hand, and it will all update
correctly afterwards.
The package already has a good debconf-driven install process for GRUB
---requiring the user to do it manually not only discards the benefit of
that, it's a delicate and error-prone operation that most
I think you can mark this "Fix released", since the problem has been
fixed since I reported it over ten years ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271238
Title:
Typo in comment
To
Please check this still happens on a supported Ubuntu release.
** Changed in: xkeyboard-config (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/802589
Note this is blocked as we can't currently deploy on Noble pending
completion of charm enablement work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069695
Title:
[SRU] OpenStack 2024.1 point
Public bug reported:
[Impact]
This release sports mostly bug-fixes and we would like to make sure all of our
users have access to these improvements.
The update contains the following package updates:
* heat - 22.0.1
* manila - 18.0.1
* nova - 29.0.1
[Test Case]
The following SRU process was
Please check this still happens on a supported Ubuntu release.
** Changed in: xkeyboard-config (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/1248351
Title:
Please check this still happens on a supported Ubuntu release.
** Changed in: xkeyboard-config (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/1290002
Public bug reported:
Ubuntu 24.04 LTS with 2 monitor setup, NVIDIA 4070TI graphics card using
the 550 driver and Wayland.
Shutting down after the end of a session the machine hung reporting a
'Flip event timeout on head 1'
Let me know what additional logs would be useful for debugging this as I
Please check this still happens on a supported Ubuntu release.
** Changed in: xkb-data-legacy (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/64678
Please check this still happens on a supported Ubuntu release.
** Changed in: gnome-control-center (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/995622
Please check this still happens on a supported Ubuntu release with
supported NVIDIA drivers.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please check this still happens on a supported Ubuntu release.
** Changed in: xkeyboard-config (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/1561618
Title:
Please check this still happens on a currently supported Ubuntu release.
** Changed in: xkeyboard-config (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not found on Noble.
** Changed in: xkeyboard-config (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/1271238
Title:
Typo in comment
To manage
Hey dfoerster,
You filed this bug report against oneiric, but I see it's still open and
doesn't appear to have much activity recently. So, now that noble
is released, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved in the new release
Hi Otto,
I've uploaded yesterday the 3 updates to our security-proposed ppa:
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=mariadb_filter=published_filter=
I will take a look at the autopkgtests we have in that ppa and, if
everything is looking
I successfully reproduced the problem in a 2023.2 test env created by sunbeam -
https://postimg.cc/Tph65M29
and also sucessfully verified the fix as well - https://i.imgur.com/KkLqexo
** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic
--
You received this bug
Test build with the new 6.8 hwe kernel:
Building initial module for 6.8.0-35-lowlatency
...
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
Done.
dahdi_dummy.ko:
Running module version sanity check.
- Original module
- No original module exists
Hello, as far as I can see (and I just double checked at github.com/qemu) the
patch set
PATCH v2 - "target/ppc: vcpu hotplug failure handling fixes" (4 parts)
is still not upstream accepted - not in 9.0.1 (latest) nor in master (commit
list).
(But please, correct me if I'm wrong, in case the
801 - 900 of 6203816 matches
Mail list logo
