Incomplete because this feature request can never be actioned in Ubuntu
until the feature exists in upstream gnome-shell first.
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
This is probably a bug in mutter but before we can report it upstream it
would be best to try and reproduce the bug without having the
unsupported extension 'wint...@nowsci.com' installed. So please remove
that extension and check the bug still occurs.
** Changed in: gnome-shell (Ubuntu)
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing
Also reported in bug 2026120
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1525451
Title:
Ubuntu GNOME
Which Nvidia driver do you have installed?
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2026120
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2026120
When reporting bugs in the future please use apport by using 'ubuntu-
You mention snap update in the title. What specific snap are you
referring to, Chromium, Cups or Snapd? The output of "snap changes"
could be useful. If you roll it back with "snap revert ",
does it work again?
> Launching chrome from menu shortcut that is managed by the snap works
> and it
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1922414
Title:
ssh-agent fails to start (has_option: command
Confirmed multiple reports of the crash still happening in GNOME 44 so
we don't have a reliable fix coming.
** Changed in: mutter (Ubuntu Kinetic)
Status: Fix Committed => Won't Fix
** Changed in: mutter (Ubuntu Jammy)
Status: Fix Committed => Incomplete
** Changed in: mutter
*** This bug is a duplicate of bug 1933186 ***
https://bugs.launchpad.net/bugs/1933186
** This bug has been marked a duplicate of bug 1933186
gnome-shell crashed with SIGSEGV in meta_window_place() from
place_window_if_needed() from meta_window_constrain() from
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2026230
Title:
error when setting up after upgrading
Status in network-manager package in
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2026230
Title:
error when setting up after upgrading
Status in
Public bug reported:
[Impact]
gnome-control-center crashed when switching to mirror mode and monitors don't
have matched resolution
[Test case]
1. Connected monitors to system which don't have same resolution.
2. Switch to mirror mode through gnome-control-center
3. gnome-control-center won't
I tried on mantic:
* Refreshed gnome-42-2204 to latest/candidate
* Opened FF
But that didn't recreate
~/snap/firefox/current/.config/fontconfig/fonts.conf . Is a later
release of the FF snap needed too?
--
You received this bug notification because you are a member of Desktop
Packages, which
This bug was fixed in the package raptor2 - 2.0.16-2
---
raptor2 (2.0.16-2) unstable; urgency=medium
* QA upload.
* Move from experimental to unstable.
* Add libcurl-ssl-dev as alternative to libcurl4-gnutls-dev. LP: #1899809
* Add libicu-dev as BD.
* Enable all tests but
There is a new build of gnome-42-2204 in the candidate channel now if
someone wants to give it a try and confirm if it indeed fixes the issue
(if you try on firefox you need a core22 based version, which is the
default in lunar)
--
You received this bug notification because you are a member of
** Changed in: mesa (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2025982
Title:
Warning 'failed to get driver name for fd 0' fails
Public bug reported:
Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
updated.
Issue appears to only impact 20.04.
chrome snap version 2529
Launching chrome from menu shortcut that is managed by the snap works
and it using this location /snap/bin/chromium
Launching chrome
** Summary changed:
- Update gnome-remote-desktop to 42.8
+ Update gnome-remote-desktop to 42.9
** Description changed:
Impact
--
This is a new stable release in the GNOME 42 series
It backports fixes for some crashes reported to errors.ubuntu.com
Changes since the current
Public bug reported:
Impact
--
mozjs102 is the SpiderMonkey JavaScript engine from Firefox ESR. It is used by
gjs to power GNOME Shell and some GNOME apps.
There are new Firefox 102 ESR releases monthly until the end of August.
https://whattrainisitnow.com/calendar/
Security Impact
also FYI: solaar detects my mouse properly
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2025980
Title:
can not configure keyboard and mouse separately
Status in upower package in
Sliders are properly rendered also when hovered.
❯ apt-cache policy yaru-theme-gtk
yaru-theme-gtk:
Installed: 22.04.5
Candidate: 22.04.5
Version table:
*** 22.04.5 400
400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
400
Sadly this new version has a new crash:
Core was generated by `/usr/libexec/gnome-remote-desktop-daemon'.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140478263563840)
at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill.c: No
marco-ThinkPad-X1-Carbon-7th ~ 5s
18:22:50
❯ apt-cache policy gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.2.1
Candidate:
** Description changed:
- I have Logitech wireless keyboard and wireless mouse, coonnected to the same
Unifying receiver.
- battery level of these devices is reported correctly, but both are listed in
power settings as a keyboard, making me a bit confusing, which device is run
out of power,
As mentioned in OP, here is the screenshot showing context of entire
desktop, with bright green hiding personal information.
** Attachment added: "Screenshot showing context of entire desktop"
Public bug reported:
Initially I thought this was an issue with IntelliJ and filed a bug there:
https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind
But when I had the same issue with GIMP, I
I see that this looks like a kernel problem. One of my computers was
without sound in the last 5 months, so I had to use a small screen
laptop to watch movies or listen audio, but I lost patience in the
process. Is there any GUI centric Linux distro, which fixes this
problem?
--
You received
could you check if the backport from lunar in jammy-proposed fixes this?
** Also affects: mesa (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu Jammy)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Description changed:
[Impact]
The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3
mesa
- new major release (23.0.4)
+ mesa-amber
+ - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no
+ changes to the classic dri drivers
+ -
probably it's due to the single path for both devices?..
udevadm info /dev/input/event3
P:
/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3
M: event3
R: 3
U: input
D: c 13:67
N: input/event3
L: 0
S:
** Also affects: mesa-amber (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2019212
Title:
Backport packages for 22.04.3 HWE stack
I've tested Focal and it works well with adsys from -proposed:
https://pastebin.ubuntu.com/p/6RBcBpZq2T/
And also does Jammy:
https://pastebin.ubuntu.com/p/pqvgSkkmcQ/
I'm having issues with Kinetic. When I install adsys, I'm no longer able
to login to the instance, I'm getting the following
@Federico: Thanks for testing and reporting that observation!
I can't reproduce it (on mantic), though. Dead keys work as expected for
me, also with the keyboard layout you mentioned.
Are you sure that the issue is related to the proposed ibus version?
Does the issue go away if you downgrade to
** Changed in: mesa (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2025982
Title:
Warning 'failed to get driver name for fd 0' fails gtk tests
device models are listed in the log above:
model: K800 (this is keyboard)
model: Performance MX (mouse)
their product codes are 046D:2010 and 046D:101A
it really seems similar to the issue #215, but that fix didn't help me.
I cloned git version of upower, compiled and installed.
now I see:
** Changed in: mesa
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2025982
Title:
Warning 'failed to get driver name for fd 0' fails gtk tests
Status in
The verification of the Stable Release Update for gnome-remote-desktop
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 event that
This bug was fixed in the package gnome-remote-desktop - 44.2-0ubuntu1
---
gnome-remote-desktop (44.2-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2024197)
* debian/upstream/metadata: trivial fix for format error
-- Jeremy Bícha Fri, 16 Jun 2023 09:58:47 -0400
Public bug reported:
On every reboot the following messages are shown in the journal:
/usr/libexec/gdm-x-session[14875]: (II) NVIDIA(GPU-0): Deleting GPU-0
/usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: KDSETMODE failed:
Input/output error
/usr/libexec/gdm-x-session[14875]: (WW)
No. As I wrote, since this is my main laptop, I didn't do anything. I
don't know anything about snap nor snapd. I had no 'intention'.
I do a
apt update && apt upgrade && snap refresh
(One after the other!) on a daily base. That's all.
grep "remove " /var/log/dpkg.log
shows nothing. The file
** Changed in: gsettings-desktop-schemas
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1983778
Title:
Major security issue in Ubuntu
Public bug reported:
I have Ubuntu 22.04 clean install + updates (installed yesterday). I
have used super + alt + s to get screen reader working on this article:
https://snapcraft.io/blog/snaps-how-we-got-here
At the time I was either in Firefox or in Edge browser installed through
deb
> The dangerously misleading "All snaps up to date." message is still
printed on "snap refresh".
I can confirm that. Today, `sudo snap refresh` wrote "All snaps up to
date." but `sudo snap refresh firefox` wrote "error: cannot refresh
"firefox": snap "firefox" has running apps (firefox) [...]"
On 04/07/23 08:23, Gunnar Hjalmarsson wrote:
> My first upload to the PPA proved to not be complete. Corrected now.
> (Wait for the builds to finish and the packages to be published before
> updating).
I have installed the new proposed version, but I have a regression with
deadkeys: pressing
The fix has been merged, we will need a rebuild of the gnome-42-2204
snap next to have it working
** Changed in: language-selector (Ubuntu)
Status: New => Invalid
** Changed in: snappy
Status: In Progress => Fix Committed
--
You received this bug notification because you are a
Do we need evince to be reuploaded for jammy there since the previous
upload was rejected by Steve?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink
Thanks, it could be solved with the same fix than bug #1794064 which is
pending review for 22.04 but the apparmor denial message is different in
your log so maybe not, we will have to check once the fix for the other
issue is available
** Changed in: evince (Ubuntu)
Status: Incomplete =>
And also the bug was reported against 'evince' which is a pdf reader but
the description doesn't seem to have anything to do with pdf...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it. We understand the
difficulties you are facing, but it is better to raise problems you are
having in the
Thank you for your bug report. I'm pretty sure I've read that description
before, did you also post about that issue and where?
Also could you report the problem directly to upstream on
https://github.com/storaged-project/udisks/issues ?
--
You received this bug notification because you are a
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it. We understand the
difficulties you are facing, but it is better to raise problems you are
having in the
it won't be fixed
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-software (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in
Thank you for your bug report. Which mouse model do you have? It looks
similar to https://gitlab.freedesktop.org/upower/upower/-/issues/215
** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #215
https://gitlab.freedesktop.org/upower/upower/-/issues/215
** Changed in: upower
Public bug reported:
The new version displays that warning which makes the gtk autopkgtest
red
Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199
Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922
** Affects: mesa
Importance: Unknown
Status: Unknown
**
Public bug reported:
I have Logitech wireless keyboard and wireless mouse, coonnected to the same
Unifying receiver.
battery level of these devices is reported correctly, but both are listed in
power settings as a keyboard, making me a bit confusing, which device is run
out of power, when I
Is this still a problem? If yes, does the --disable-gpu flag help?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1563184
Title:
Chromium-browser armhf crashes with
I think you had removed the gnome-42-2204 and this caused the interface
not to connect.
> sudo apt install snap --reinstall
> sudo apt install snap --reinstall chromium
You conflated snap[1] and snapd[2] in those instances. If your intention
was to reinstall Chromium (and not snapd), then you
I think that anyone capable of using a computer has the right to write to a USB
key regardless of its formatting.
You don't have to be a genius with superpowers!
enfants@p:/media/enfants$ ls -als
total 127
4 drwxr-x---+ 25 rootroot 4096 juil. 5 09:11 .
4 drwxr-xr-x 11 rootroot
This bug was fixed in the package libinput - 1.22.1-1ubuntu0.1
---
libinput (1.22.1-1ubuntu0.1) lunar; urgency=medium
* Disable pressure for Precision5680 2nd source touchpad (LP: #2023623)
- d/p/0001-quirks-Dell-Mayabay-Pressure-Pad.patch
-- Kai-Chuan Hsieh Thu, 15 Jun
Good! Marking it as fixed then, thank you again for reporting back.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This bug was fixed in the package libinput - 1.20.0-1ubuntu0.3
---
libinput (1.20.0-1ubuntu0.3) jammy; urgency=medium
* Disable pressure for Precision5680 2nd source touchpad (LP: #2023623)
- d/p/0001-quirks-Dell-Mayabay-Pressure-Pad.patch
-- Kai-Chuan Hsieh Tue, 13 Jun
The verification of the Stable Release Update for ubuntu-meta 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 event that you
This bug was fixed in the package ubuntu-meta - 1.481.1
---
ubuntu-meta (1.481.1) jammy; urgency=medium
* Refreshed dependencies
* Added firefox to desktop-minimal-recommends [amd64 arm64 armhf],
desktop-recommends [amd64 arm64 armhf] as it provides dpkg alternatives
for
Khaled Hosny committed a patch related to this issue.
It has been pushed to "libreoffice-7-5":
https://git.libreoffice.org/core/commit/1f9087b8da6588239a4b655f2dc94d48817569a5
tdf#48707: Explicitly set overline color in PDF export
It will be available in 7.5.6.
The patch should be included in
66 matches
Mail list logo
