I created a PPA with a Bluez backport to be used until the issue is
fixed https://launchpad.net/~giner/+archive/ubuntu/bluez
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/207
To #10, thanks for feedback.
But the issue you mentioned it's phenomenon is different with this one.
In lp:2063005, the touchscreen is responsive when touch it, and we have
KB article on Ubuntu wiki to address it, so it is not shipping blocker.
But this issue is touch screen totally not respond
** Description changed:
Impact
==
-
- Ubuntu has included Google's color emoji font by default for years.
- Annually, the Unicode Consortium releases a new Unicode standard with
- new emoji. Internet communication platforms quickly adopt the new emoji
- and it's important that those emoji
Public bug reported:
I recently upgraded from Ubuntu 22.04 to Ubuntu 24.04. Now whenever I
log in, sometimes I'll get a blank screen. It will only show the mouse
cursor as an X.
The problem seems to be intermittent. So far it's only happened to me
using X11.
My current workaround:
1. Open anoth
** Changed in: librsvg (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/2089563
Title:
[SRU] librsvg 2.59.2
To manage notificati
** Changed in: gimp (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2089343
Title:
gimp fails to build from source against libheif 1.1
This only affected Focal, the later releases include the second commit
already.
** Changed in: mpg123 (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: mpg123 (Ubuntu Noble)
Status: New => Fix Released
** Changed in: mpg123 (Ubuntu Oracular)
Status: New => Fix Releas
** Description changed:
Impact
--
Contains several bug fixes:
https://gitlab.gnome.org/GNOME/librsvg/-/raw/2.59.2/NEWS.
Test plan
-
+ https://wiki.ubuntu.com/Process/Merges/TestPlans/librsvg?
+
Regression potential
+
+ Code paths processi
Fix landed upstream, should we re-target oracular again too?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2077216
Title:
Wayland session gets immediately SIGKILLed: No option to s
** Tags removed: desktop-needs-sru
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2080602
Title:
[regression] GNOME 46/47 dropped support for Xilinx Mali graphics
To manage notific
*** This bug is a security vulnerability ***
Public security bug reported:
The fix for CVE-2024-10573 is insufficient in certain releases, pending
investigation. This is the tracking bug.
** Affects: mpg123 (Ubuntu)
Importance: Undecided
Assignee: Marc Deslauriers (mdeslaur)
S
Discussed in IRC and this seems to be the correct version number.
GVFS 1.56.1-1 is in devel, I want to SRU it to Oracular which has
1.56.0-2, so I need to first update devel's version to 1.56.1-1ubuntu0.25.04.1
and only then request the SRU to Oracular with 1.56.1-1ubuntu0.24.10.1?
why not jus
** Summary changed:
- [SRU] Backport 1.56.1
+ [SRU] Backport gvfs 1.56.1
** Description changed:
Impact
--
From https://gitlab.gnome.org/GNOME/gvfs/-/raw/1.56.1/NEWS:
* udisks2: Increasing reference count when updating volume to fix crashes
(Ondrej Holy)
* onedrive: Use nam
SRUs need to follow https://wiki.ubuntu.com/StableReleaseUpdates
process; Marking as won't fix as Bionic is already past support.
** Changed in: gvfs (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribe
Public bug reported:
Ubuntu 22.04.
Old hardware: Intel H67 chipset, intel xeon 1240 v2, ddr3 8 GB summary.
Sometimes GIMP crushes or stop working on some filters, in that time I need to
kill GIMP manually.
Today GIMP works normal, but crushed on exit and suggests to send bug report.
So bug repo
Isn't touchscreen on xorg already blocked by
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005
https://gitlab.gnome.org/GNOME/mutter/-/issues/3484
?
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3484
https://gitlab.gnome.org/GNOME/mutter/-/issues/3484
--
You received
Public bug reported:
Description
When launching Nautilus (file manager) from the terminal embedded in
Visual Studio Code using the command `nautilus .`, closing Nautilus
causes it to fail to reopen via normal means (e.g., launcher or
terminal). A system restart is required to restore functionalit
17 matches
Mail list logo