Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Sometime when unlocking the session and there is external monitor connected,
the internal monitor doesn't turn on, only the external one.
Unplugging the external monitor solves the issue.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.1-0ubuntu0.1
If and when the freeze happens again, please:
1. Check to see if gnome-shell's CPU usage is high or low.
2. Turn the freeze into a crash report so we can analyse the thread
stack traces: kill -ABRT PID
3. Report the crash formally, like in
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1973638
Title:
gnome-shell 42 leaks tens of megabytes with every screenshot
Status in GNOME Shell:
Set the DUT back to X, plug external 4K monitor. I won't see the screen
freeze.
[DUT]
XPS 9310
[Monitor]
ASUS PA279CV
[kernel]
5.15.0-35-generic
[BIOS]
3.4.0
** Attachment added: "dpkg.txt"
I believe that totem now uses gstreamer1.0-gl for rendering, starting in
Ubuntu 22.04. So that should be tracked too.
** Summary changed:
- Screencast video plays back as gray and compressed on left
+ Video plays back as grayscale and compressed on left
** Changed in: totem (Ubuntu)
[Expired for ibus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ibus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
problem also with any webm video created by cheese
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1978153
Title:
Screencast video plays back as gray and compressed on left
Status in
same problem on ubuntu 22.10 with totem: Installed: 42.0-1ubuntu2
corrado@corrado-n3-kk-0601:~$ inxi -SCGx
System:
Host: corrado-n3-kk-0601 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64
compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.2
Distro: Ubuntu 22.10 (Kinetic Kudu)
CPU:
Info:
attaching screeshot
** Attachment added: "Screenshot from 2022-06-10 05-51-07.png"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1978153/+attachment/5596172/+files/Screenshot%20from%202022-06-10%2005-51-07.png
--
You received this bug notification because you are a member of Desktop
Thanks for the bug report. You appear to be using the 'oibaf' PPA for
your graphics packages, which is unsupported and is known to cause bugs.
Please remove it from the system and then open new bugs for any problems
you find.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
What is the problem you would like to report?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1975379 ***
https://bugs.launchpad.net/bugs/1975379
** This bug has been marked a duplicate of bug 1975379
Xorg crash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
kmsdebug.txt ends with the screen drawing normally and successfully. Did
you see anything on screen or did it appear to be off?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
That video is playing correctly in totem on both 22.04 and 20.04 here.
Can you provide a screenshot of when the bug is happening?
** Package changed: gnome-shell (Ubuntu) => totem (Ubuntu)
** Changed in: totem (Ubuntu)
Status: New => Incomplete
** Summary changed:
- screencast video are
Those are two unrelated bugs so please pick one only:
* When I record the screen with Kazam the resulting video shows only the
pointer, the rest of the screen is black.
Unless it's been ported to use PipeWire, such legacy screencasting apps
for X11 won't work in Wayland sessions. A black screen
Although now I've said that, the bug has stopped happening.
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Broken keyboard navigation in the power off dialog in 22.04
+ Broken keyboard navigation in the Power Off
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Seems to be the Desktop Icons NG extension stealing focus. The bug goes
away with that extension disabled. Same as bug 1969598.
** Tags added: jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
> My understanding from what I have read about this topic was
> that users with hybrid systems (which I take to mean those
> with both an NVIDIA graphics card and a second non-NVIDIA
> graphics card in this context) are expected to see the gear,
> but I may be mistaken.
Technically, yes. Our
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
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 it any more.
@seb128,
Thanks for your feedback, I prefer to update to 1.18 than this fix, and
as I know Stephane.Verdy has pushed 1.18 for long time to support more
modem devices, so let's wait for the 1.18.
IF the 1.18 was dropped in proposed, we could reconsider this fix.
Thanks!
--
You received this
It's not a problem to be resolved in the different applications that are
loading thumbnails, snapd should resolve that usecase by making those
write to a location used by the system
I totally agree with you.
Any progress made since ?
--
You received this bug notification because you are a
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
The isc-dhcp-client dependency exists to ensure support for network
configuration from within an initramfs, for which systemd-networkd is
not currently a replacement since we don't run systemd in the initramfs.
See also https://lists.ubuntu.com/archives/ubuntu-
devel/2022-May/042080.html ff
ubuntu-meta (1.468) hirsute; urgency=medium
* Refreshed dependencies
* Added media-types to standard
* Removed mime-support from standard
-- Steve Langasek Fri, 16 Apr 2021
21:52:27 +
This dependency was removed a year before this bug report was filed?
** Changed in: ubuntu-meta
I was looking to run cairo on wayland. A web search led me to the EGL
device. I'm guessing by buffer you mean IMAGE surface (after digging in
the headers a bit). I am happy to try that. But I'm guessing at some
point in the future peeps will want it. Thanks for digging in.
--
You received
Reflecting on my original issue from the perspective of a lay user,
crashing the windowing system because a custom configuration file
couldn't be parsed seems like a bug in its own right. A lay user may
understandably react very strongly to seeing a black screen at startup.
If they have a more
No, it's not possible, we only have one proposed pocket. If we want to
do that we need to delete the 1.18 update, do the SRU with the fix only
and then restart the process again for 1.18. Is that the option you want
to go for now?
--
You received this bug notification because you are a member of
To clarify, I was defaulted into Wayland (which worked as far as I could
tell aside from the broken Night Light) upon upgrade from Ubuntu 21.04
to Ubuntu 22.04, so what was actually hidden from users not comfortable
manually editing /etc/gdm3/custom.conf in this case was instead X11. My
I don't understand the details of the behaviour it seems an issue with
power-profiles-daemon. And yes if the profile fails to change the
settings should display the error but it's not clear to me if the
service fails or if the action doesn't reflect as you expect. The
mentioned ticket seems to
** Attachment added: "kmsdebug.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5596083/+files/kmsdebug.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Sorry It was solved I don't remember how maybe an update.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1950828
Title:
ibus-daemon crashed with SIGABRT in g_mutex_clear().
Status in
kevin@arcadia:~$ apt info network-manager
Package: network-manager
Version: 1.36.6-0ubuntu2
kevin@arcadia:~$ apt info libnm0
Package: libnm0
Version: 1.36.6-0ubuntu2
I have installed network-manager and libnm0 version 1.36.6-0ubuntu2 from
jammy-proposed. After connecting to a network with both
Sorry, the video is wrongly played by totem, using MPV the video is ok.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1978153
Title:
screencast video are gray and compressed on
Public bug reported:
press 'printscreen' the window for screenshot/screencast open, start screencast
the video produced is gray and compressed on the left part of the screen.
see attachment
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.1-0ubuntu0.1
ProcVersionSignature:
Hello Kevin, or anyone else affected,
Accepted network-manager into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.36.6-0ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Public bug reported:
When I record the screen with Kazam the resulting video shows only the pointer,
the rest of the screen is black.
After I sleep and start my HP laptop, Cheese and Zoom do not detect the camera.
Hardware model: HP HP Pavilion Laptop 15-cw1xxx
Processor: AMD® Ryzen 7 3700u
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I have a thinkpad x1 extreme gen2.
I have a bit trouble to exactly understand what I could do with the
information from that URL - will try to read it again later with some
more time.
What I can confirm ist that thermald reports some kind of
incompatibility as far as I understand:
$ sudo
** Changed in: network-manager-applet (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1978007
Title:
@waveform
I think that the meaning of "basic" feature in an OS is something that
can't be stated universally because it depends of the usage done by each
set of users. In my opinion remote desktop is a "basic" feature because
I use the Raspberry Pi remotely. And for a Raspberry Pi that's nothing
> It is a pity Canonical is advertising super optimisations on
> Raspberry Pi 4 with 22.04 and this basic feature is totally broken
> as is: was never ever tested...
Graphical remote desktop is far from a "basic" feature, in my opinion
(an opinion bolstered by the fact it is only a recent
Thanks for the testing and for following up on the issue. I've uploaded
that patch to the SRU queue now
** Description changed:
+ * Impact
+ The recent SRU created a regression in IPv6 routing order
+
+ * Test Case
+
+ 1. Connect to a network where the router sends "A" and "M" bits in the
+
Happened again :(
** Attachment added: "System log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5595900/+files/prevboot.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Updated package
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1978017
Title:
Broken keyboard navigation in the power off
Public bug reported:
So you just installed Ubuntu 22.04 and you try to play an mp4 video.
Totem will complain about missing an H.264 decoder, as you can see in
the command line output:
Missing plugin: gstreamer|1.0|totem|decodificador H.264 (Main
Profile)|decoder-video/x-h264, level=(string)3,
You have been subscribed to a public bug:
The "power off" dialog in gnome shell does not have focus when launched
from the launcher ui (meta key + search) and it is therefore impossible
to select either "cancel" or "power off" using keyboard navigation.
If, on the other hand, the dialog is
Public bug reported:
There is a missing dependency that makes using GTK/GDK from Python a bit
brittle.
GTK/GDK uses cairo for drawing, so having GTK/GDK means that cairo is
available and can be used.
However, having the Python bindings for GTK/GDK currently doesn't
guarantee that the Python
Adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and disabling disable-wakeup-on-
lid-switch.service did the trick for me! Thanks!
> Out of curiosity, what package owns /etc/systemd/system/disable-
wakeup-on-lid-switch.service ?
It's a self-written service that blocks the laptop from waking up when
the
@seb128 yes, the following command line plays (for at least 20 seconds
-- I didn't watch the whole thing) happily under totem:
MESA_GL_VERSION_OVERRIDE=3.3 totem big_buck_bunny_720p_surround.mp4
So the issue is simply that the pi's GL driver only goes up to 2.1,
and/or that GTK doesn't accept
Thank you, this solution fixes the bug for me as well.
--
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/1977619
Title:
NetworkManager 1.36.6 no longer prefers DHCPv6 addresses
This seems to restore previous behaviour yes.
--
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/1977619
Title:
NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over
Hey Nathan, thanks for the work there. Sorry I've probably been unclear
but the changelog entry correctly describing the previous merge was the
1.18.0-1ubuntu1 one, and from that section
'- Add Ubuntu patches:
- lp341684_device_sensitive_disconnect_notify.patch
-
Upstream provided me a patch to try which I uploaded to a ppa now,
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/23833629
Could you install it and see if that fixes the issue?
** Changed in: network-manager (Ubuntu)
Status: Triaged => In Progress
--
You received this
Out of curiosity, what package owns /etc/systemd/system/disable-wakeup-
on-lid-switch.service ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked screen
Another possibility is that you have excessively deep sleep enabled on
too many devices (like if 'tlp' is installed) and some machines can't
wake up from that. Make sure you don't have tlp installed and also try
adding a USB mouse to wake the machine up with - you can also then see
if the mouse is
OK, the final thing to try is to replace the above environment variable
with:
MUTTER_DEBUG=kms
then reboot, reproduce the hang in a Wayland session, reboot again and
run:
journalctl -b-1 > kmsdebug.txt
and attach the resulting text file here.
That will tell us if gnome-shell is sending
If a bug is common to Xorg and Wayland sessions then that often means
it's in the kernel, or in the hardware. Let's assume that's not yet true
and please follow the instructions in comment #8.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
> Looks like you were only logged in for 2 seconds before the log ends.
Is that right, you just locked the screen immediately?
Yes, that's right.
> Also do you have any external monitors connected?
No.
> MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
> Any improvement?
Nothing changed.
** Attachment
** No longer affects: libreoffice (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1978053
Title:
lubuntu kinetic live - firefox can't open libreoffice help file
Status
I was wrong, disabling DPMS didn't fix the suspend issue. So these
problems are most likely unrelated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked
I was able to confirm the problem exists with snapd 2.56+22.10. I've
also confirmed that it works correctly with snapd from edge as some
fixes were landed in master already.
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a
Unclear what needs to happen in MAAS, and if there's an issue with the
current behavior.
** Changed in: maas
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
Thanks. Looks like you were only logged in for 2 seconds before the log
ends. Is that right, you just locked the screen immediately?
Also do you have any external monitors connected?
Next please try adding this to /etc/environment:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
and then reboot and log
Change the title to "Screen freeze" to avoid any confusion of "system
hang" or "system freeze".
Sure, I'll add the debug in the /etc/environment. Thanks.
** Summary changed:
- System freeze
+ Screen freeze
--
You received this bug notification because you are a member of Desktop
Packages,
The /var/crash folder is empty, there are no fresh logs at
https://errors.ubuntu.com/user/ID.
** Attachment added: "Wayland system log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5595815/+files/wayland_prevboot.txt
--
You received this bug notification
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2296
https://gitlab.gnome.org/GNOME/mutter/-/issues/2296
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2296
Importance: Unknown
Status: Unknown
--
You received this bug notification because
If your log still gets flooded with messages then there's a good chance
that's the reason why gnome-shell is not responding. Only the "stack
trace" info is usually irrelevant.
If you get a freeze without a flood of log messages then we should put
mutter in debug mode via /etc/environment:
The manifest (https://cdimage.ubuntu.com/lubuntu/daily-
live/current/kinetic-desktop-amd64.manifest) gives
snapd 2.56+22.10
snap:snapd stable 16010
(Note: I didn't reboot the ISO/media to verify; this is from manifest
but also matches the manifest downloaded when I performed zsync ..
Public bug reported:
1. Open Chromium
2. Press Ctrl+Shift+P
What happens: a print dialog pops up (presumably from xdg-desktop-
portal-gnome), and both the dialog and the main Chromium window become
non-responsive. After a few seconds GNOME Shell pops up a "this app is
unresponsive" dialog with
Sorry, connect type-c monitor directly without docking can also
reproduce this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1976204
Title:
System freeze
Status in OEM
Thanks. The Xorg session in comment #4 doesn't appear to have crashed.
Maybe it was just frozen.
Please repeat the above steps with a Wayland session and also remember
to follow
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug
I always assumed Cairo was for software rendering only. That's how
gnome-shell and others use it -- render to a software buffer and then
upload that to a GL texture.
I guess the advantage of building Cairo with native GL support is that
it all happens on the GPU with less CPU time wasted...
Also, disabling DPMS solved the issue for me where my laptop couldn't
properly suspend/resume.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977977
Title:
Blanked screen
** Changed in: mutter (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed
** Attachment added: "System log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5595797/+files/prevboot.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Also the flood of log messages seen in comment #2 is tracked in bug
1908429.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1976204
Title:
System freeze
Status in OEM Priority
Since you mention DA310 and WD19TB, I am reminded of bug 1960865 and bug
1970495.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1976204
Title:
System freeze
Status in OEM
The openGL option was disabled a long time ago in Debian, the rational isn't
really descriptive on the issue though
https://salsa.debian.org/gnome-team/cairo/-/commit/a4bad9f84
But we also disabled it around the time in Ubuntu due to bug #725434
with nvidia drivers, but comments from 2015
> The one remaining mystery to me is that the gear to switch
> between X11 and Wayland still doesn't show up at the login screen.
We intentionally hide Wayland when the Nvidia driver is present due to
unresolved bugs in the Nvidia Wayland implementation:
Since Javascript stack traces are hardly ever related to freezes, and
particularly if there are multiple of them, I've removed mention of the
stack traces.
** Summary changed:
- system freeze and gnome-shell reports multiple stack trace
+ System freeze
--
You received this bug notification
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Summary changed:
- Desktop resolution was set incorrectly until I booted up the PC AFTER turning
on the monitor
+ Desktop resolution was set
Thank you for your very quick and helpful guidance, Daniel. I will sleep
far easier in the future, my eyes now spared from blue light! The
contents of prevboot.txt contained the following pertinent excerpt:
/usr/libexec/gdm-x-session[1415]: Data incomplete in file
I encountered this bug today. Although the monitor was on, I could not
get a signal till I turned it off and on. Then I just got 1024x768.
Weirdly though, Wayland was in use with no Xorg server running.
Now that I try to reproduce the bug again, I can't. I just get Xorg as
described in bug
What is the version of snapd (both the deb and the snapd snap)? There
was a related fix in snapd introduced in
https://github.com/snapcore/snapd/commit/103c652f30089c81d69a89714fb5a076c94ed365
but it is available only in snapd 2.56 and later.
** Changed in: snapd (Ubuntu)
Status: New =>
Three people affected by this bug now. If you are one of them then
please:
1. sudo apt install gnome-shell-extension-prefs
2. Open the Extensions app and disable all extensions.
3. Log in again.
4. If the same bug persists even without any extensions enabled then
please report it at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1971126 ***
https://bugs.launchpad.net/bugs/1971126
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1971126, so it is being marked as such. Please
Thanks for the bug report.
Firstly please check for crashes by following these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
In a Wayland session it is only crashes of 'gnome-shell' that are
relevant here.
Secondly, next time the problem
You have been subscribed to a public bug:
After I lock my screen and let it blank, moving the mouse or pressing
any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't
help.
That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland).
ProblemType: Bug
DistroRelease: Ubuntu
I can confirm that /usr/share/applications/update-manager.desktop is
missing the Name[zh_CN] entry when installed. It should probably always
be there.
** Tags added: jammy
** Summary changed:
- Unable to display Chinese name on desktop
+ update-manager.desktop unable to display Chinese name
**
** Patch added: "udev-Match-WWAN-type-attribute-instead-of-device-nam.patch"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+attachment/5595791/+files/udev-Match-WWAN-type-attribute-instead-of-device-nam.patch
** Description changed:
[Impact]
On 20.04.4, with
Yes it appears Cairo has no linkage to GL libraries and the debian rules
use --disable-gl
** Summary changed:
- apport-bug thinks it's running on Xorg
+ No cairo GL support for wayland, 22.04
** Package changed: ubuntu => cairo (Ubuntu)
** Changed in: cairo (Ubuntu)
Status: Incomplete
98 matches
Mail list logo
