Great!
I was hoping that 42.0 would fix some of the grab-related bugs.
** Changed in: gnome-shell (Ubuntu Jammy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
In my case Gnome Extensions works under Wayland but it crashes under
Xorg.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1966502
Title:
gjs-console crashed with SIGSEGV
To manage
Hi Daniel,
I installed gnome-shell 42.0-1ubuntu1 from -proposed, along with mutter
and others this morning and rebooted. I am no longer able to reproduce
this issue, I can move the mouse as the screen is fading, and I can
click things and enter text as normal.
I will close the bug in a couple of
Thanks for the clarification on their tight coupling! I really hope the
crash i saw was some sort of corner case that rarely appears. If I do
see it again, I'll let you know.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
Seems like killing your Xwayland process is an easy way to reproduce
this crash.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1949200
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Turns out both statements are true: gnome-shell is designed to survive
Xwayland crashing, and gnome-shell might crash when Xwayland crashes.
In my case:
Mar 29 11:44:48 nine gnome-shell[3392]: Connection to xwayland lost
Mar 29 11:44:48 nine gnome-shell[3392]: Xwayland just died, attempting to
I really thought gnome-shell surviving Xwayland crashes was something
that was fixed (or scheduled to be fixed) upstream some time ago. But
occasionally there are hints in bug reports that it still doesn't
recover. Also I just tried it and killing Xwayland does kill gnome-shell
too :(
--
You
*** This bug is a duplicate of bug 1965897 ***
https://bugs.launchpad.net/bugs/1965897
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1965897, so is being marked as such.
Ok it wasn't clear to me if the fault was gnome-shell or xwayland.
Following the instructional link, I do see https://errors.ubuntu.com/user/ID
items, but none around this time. The workaround in bug 994921 is outdated and
the line it says to comment is no longer in the file... so I'll just see
The output of "dpkg -l" as capture video in #2.
** Attachment added: "dpkg-l"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1966635/+attachment/5574005/+files/dpkg-l
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
video captured as running jammy, updated @ 2022/03/29, x11 mode. (can't
drag and drop the file to move it around in Wayland mode)
To move a file by drag and drop, need to move fast. If you check the
video, if the finger moves too slow, it will show the context menu, and
no longer be able to move
Also if there are any "crashes" then please follow these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Sounds like the main issue is in the radeon driver as logged by mutter
through the gnome-shell process:
[ 41.402230] perseverance gnome-shell[1980]: Running GNOME Shell (using
mutter 42.beta) as a Wayland display server
[ 41.541617] perseverance gnome-shell[1980]: Device '/dev/dri/card0'
If the main issue is:
gnome-shell[15153]: Connection to xwayland lost
then that suggests the problem was Xwayland crashing so please follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
The "invalid memory" messages are unrelated (bug 1965673).
Timo, was it bug 1966221 that you meant to assign to mesa?
Regardless, I think we should keep a gnome-shell task here just to make
the bug easier to find, and avoid duplicates.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Yes the yelp->gtk->opengl backend has probably changed over the past
year.
** Tags removed: hirsute
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/1924251
Title:
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** Tags added: crocus
--
You received this bug notification because you are a member of Ubuntu
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
** Changed in: nautilus (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to
This still seems to be an issue on the current Ubuntu Pi Jammy images
although it presents in a different manner: instead of an incorrect-
stride corruption, the embedded browser (in the same places: help
windows, or the login entries for online accounts) simply appears blank
white.
However, if
This bug was fixed in the package libfprint -
1:1.90.7+git20210222+tod1-0ubuntu4~21.10.3
---
libfprint (1:1.90.7+git20210222+tod1-0ubuntu4~21.10.3) impish; urgency=medium
* debian/patches: Add support for new synaptics ID. (LP: #1962277)
-- Andy Chi Fri, 25 Feb 2022 13:44:51
This bug was fixed in the package libfprint -
1:1.90.2+tod1-0ubuntu1~20.04.7
---
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.7) focal; urgency=medium
* debian/patches: Add support for new synaptics ID. (LP: #1962277)
-- Andy Chi Tue, 22 Feb 2022 19:29:31 +0800
** Changed in:
This bug was fixed in the package ubuntu-drivers-common -
1:0.9.2.4~0.21.10.1
---
ubuntu-drivers-common (1:0.9.2.4~0.21.10.1) impish; urgency=medium
[ Jeremy Szu ]
* 71-u-d-c-gpu-detection.rules,
gpu-manager.c:
- Wait for the nvidia-drm module to be loaded. This works
The verification of the Stable Release Update for ubuntu-drivers-common
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 ubuntu-drivers-common -
1:0.9.0~0.20.04.6
---
ubuntu-drivers-common (1:0.9.0~0.20.04.6) focal; urgency=medium
[ Jeremy Szu ]
* 71-u-d-c-gpu-detection.rules,
gpu-manager.c:
- Wait for the nvidia-drm module to be loaded. This works around
** Package changed: ubuntu => gdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1966795
Title:
First boot with fingerprint auth enabled, gdm doesn't prompt to enter
You have been subscribed to a public bug:
Steps:
- Enroll fingerprints
- Run `pam-auth-update`
- Enable "Fingerprint authentication"
- Restart
Outcome:
Fingerprint authentication will work correctly but the textbox to enter
a password manually will be disabled. If fingerprint verification
This bug was fixed in the package gnome-control-center - 1:41.4-1ubuntu9
---
gnome-control-center (1:41.4-1ubuntu9) jammy; urgency=medium
* debian/patches: Refresh (and drop removed ones)
* ubuntu-panel: Update color assets to match tuned yaru colors
* ubuntu-panel:
Public bug reported:
Wayland started crashing for me on upgrade to Jammy, which I'm aware is
currently in alpha.
gdm was crashing, and changing to lightdm addressed this issue. If I
select 'Ubuntu on Xorg' - I can login without problems.
If I select Wayland instead, I just get a black screen,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Hello Christian, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Christian, or anyone else affected,
Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1966796/+attachment/5573879/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1966796/+attachment/5573880/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1966796/+attachment/5573878/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1966796/+attachment/5573877/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1966796/+attachment/5573876/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
On an up2date Jammy, running gnome-shell from proposed, and gnome-shell
randomly lost my connection to wayland. There was no crash logged in
/var/crash.
Journalctl shows that after many of these internal errors, gnome-shell
experienced a loss of connection with wayland:
Mar
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1966084
Title:
Nautilus file/folder highlight color
Update: my resolution didn't resolve it. If I attempt to play a file, it
crashes with the same message as above.
** Summary changed:
- Totem crashes on launch
+ Totem crashes on launch or when attempting to play video with a Wayland flush
error
--
You received this bug notification because
Public bug reported:
If I launch totem, it crashes pretty much immediately. I resolved this
by deleting .config/totem. I had moved some video files that had been
previously opened within it recently, so possibly it was trying to
reference them (for thumbnails or whatever) and that broke it.
Public bug reported:
The login screen is shown twice and I have to supply the password twice.
The system works normally afterwards. When I select auto-login in the
settings still one login screen is shown.
gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service;
I can reproduce on intel haswell, with the gallium based 'crocus'
driver, but not when the app is run like:
MESA_LOADER_DRIVER_OVERRIDE=i965 gnome-extensions-app
though 'libgl1-amber-dri' needs to be installed first, it ships classic
dri drivers now
--
You received this bug notification
*** This bug is a duplicate of bug 1966502 ***
https://bugs.launchpad.net/bugs/1966502
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1966502, so is being marked as such.
** Attachment added: "journalctl -e"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966781/+attachment/5573823/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Public bug reported:
For 2 weeks now, my test machine for ubuntu next boot to black screen
with only the white cursor in top left corner.
journalctl -e show many gnome-shell error complaining about : /dev/dri/card0
error, the computer run with an AMD FirePro W5000 (Pitcairn LE GL)
I found some
See also https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1966777
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966221
Title:
gnome-extensions-app crashes with
Public bug reported:
I think it's related to https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1966221
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1965563
Title:
gnome-extensions-app fails to start (Protocol error)
So, I've checked with the latest kernel, but the KMS properties aren't
either showing:
proptest | grep privacy -A3
98 privacy-screen sw-state:
flags: enum
enums: Disabled=0 Enabled=1
value: 0
99 privacy-screen hw-state:
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1966502/+attachment/5573769/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1966502/+attachment/5572968/+files/CoreDump.gz
** Changed in: gjs (Ubuntu)
Stacktrace:
#0 0x7f312f6ecfeb in use_surface.constprop.0 (ice=,
batch=0x1, p_surf=0x54, writeable=, aux_usage=32561,
access=IRIS_DOMAIN_RENDER_WRITE, is_read_surface=) at
../src/gallium/drivers/iris/iris_state.c:4825
surf = 0x54
res = 0x5630ecaafa00
offset = 0
Public bug reported:
Under normal circumstances, he should display it like this
https://sm.ms/image/ijNDvxRWoZ2qrea
-
But when I scroll in the Dock, he displays it like this
https://sm.ms/image/Eq2sNvKAOhxu8Si
-
Obviously, this doesn't show which virtual desktop I'm currently on.
ProblemType:
Yes they are Reminders from the Calendar app. For a Google account.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1966614
Title:
I am getting calendar notification pop-ups
Launchpad has imported 13 comments from the remote bug at
https://bugs.webkit.org/show_bug.cgi?id=238244.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1966178
Title:
Screen-privacy couldn't
Sadly, fixing this in ubuntu is not something trivial at the moment, as
it would imply switching to the gnome-bluetooth side that depends on
gtk4 and so we'd need to bump also g-c-c.
It's probably still possible to backport the relevant bits.
--
You received this bug notification because you
I guess mutter side can be closed, since we've already beta in archive.
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966221
Title:
Thank you for your bug report. Are those notifications calendar event
reminders? For which sort of account?
** Changed in: gnome-calendar (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
There is a similar discussion upstream on
https://bugs.webkit.org/show_bug.cgi?id=238244
** Bug watch added: bugs.webkit.org/ #238244
https://bugs.webkit.org/show_bug.cgi?id=238244
** Also affects: webkit via
https://bugs.webkit.org/show_bug.cgi?id=238244
Importance: Unknown
On further digging, I've found that this issue is due to an AppArmor
rule, which for some reason was treating localhost differently (as IPv6)
than a regular network address (IPv4). Closing.
** Changed in: xrdp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because
Thank you for your bug report, could you add a screenshot showing the
issue?
** Package changed: xdg-desktop-portal (Ubuntu) => firefox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu.
It's been a few years now and we still haven't landed a fix. I would
like to attempt a fix specifically in desktop-icons-ng in future, but
either way this bug can drop severity...
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Importance: Medium => Low
** Changed in:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gjs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1966502
*** This bug is a duplicate of bug 1966502 ***
https://bugs.launchpad.net/bugs/1966502
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1966502, so is being marked as such.
*** This bug is a duplicate of bug 1966502 ***
https://bugs.launchpad.net/bugs/1966502
** This bug has been marked a duplicate of bug 1966502
gjs-console crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs
Let's move to more specific bug reports or else this will stay open
forever. Let's also focus on Ubuntu 22.04 performance only...
Starting with bug 1966659.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
Thank you for working with us to try and get a test plan for Ubuntu
together.
How about this:
1) I'll accept the package (1.44.1-1ubuntu1.1) into focal-proposed.
2) You test using your Ubuntu VM as best as you can to ensure that the package
hasn't regressed for Ubuntu users.
3) You verify the
*** This bug is a duplicate of bug 1966502 ***
https://bugs.launchpad.net/bugs/1966502
Public bug reported:
I get this crash when trying to execute gnome-extensions-app.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem
Public bug reported:
In Ubuntu 22.04 with the new color theme in Appearance setting,
Firefox (snap version) does not use the color theme in its URL / Address
bar.
Google Chrome and the previous Deb package-based Firefox is using the
color theme (IIRC, was just brief moment before it got
** Tags added: 2-in-1 oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Public bug reported:
My log is occasionally flooded with a burst of:
../clutter/clutter/clutter-actor.c:12417):clutter_actor_event: runtime
check failed: (retval == CLUTTER_EVENT_PROPAGATE)
when I am interacting with the icon grid.
** Affects: mutter
Importance: Unknown
Status:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Thanks for the quick reply.
The problem here is that kernel 5.13 and the free graphics driver it
includes is too old to support your Nvidia RTX 3060 Ti chip.
Please use the 'Additional Drivers' app to install the official Nvidia
driver.
** Summary changed:
- ubuntu on wayland works very slow
*** This bug is a duplicate of bug 1965648 ***
https://bugs.launchpad.net/bugs/1965648
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 1965648, so it is being marked as such. Please
This bug is about Xorg fractional scaling AFAICS.
Starting in Ubuntu 22.04 at least, everyone should be able to use
Wayland fractional scaling. If anyone here is using Wayland already then
please open a new bug for that.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
For a 2-in-1 machine, as we flip more than 180 degrees between monitor
and keyboard, then it goes to tablet mode.
In table mode, if the orientation sensor is there, the monitor
orientation will automatically rotate as we rotate the machine.
As we flip the machine back to
Yes, I think it's fixed in jammy, update status as is.
** Changed in: oem-priority
Status: New => Fix Released
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: liferea (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: epiphany-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
** Summary changed:
- swipe up from the bottom of the touch monitor
+ swipe up from the bottom of the touch monitor won't bring the OSK
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I use 125% Fractional scaling, and if I try to take a screen shot using
the app `Shutter`, if the region is almost the full screen, the screen
goes wonky and keeps switching resolutions, its impossible to screenshot
the area I require. Also VLC can't switch to full screen. Only Chrome
successfully
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1831039
Title:
When using Wayland, the onscreen
Yes, typo updated
** Summary changed:
- swipe up from the button of the touch monitor
+ swipe up from the buttom of the touch monitor
** Description changed:
OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard
enable.
Steps:
1. touch gnome-terminal and see OSK
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966631/+attachment/5573660/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966631/+attachment/5573661/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "allpackages.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966631/+attachment/5573659/+files/allpackages.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Also in progress in
https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/203
** Also affects: wayland (Ubuntu)
Importance: Undecided
Status: New
** Changed in: wayland (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member
Can also confirm that the same bug above is happening to me as well,
triggered after being in a Discord voice channel for a long duration of
time. Alt + F2 and then r is a workaround I found that fixes the problem
temporarily until it happens again.
--
You received this bug notification because
Per test on jammy, update on 2022/03/28, can also reproduce this issue
in Wayland mode.
Well, hard to say if this is good or bad behavior.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Thanks for the bug report. It looks like the system can't find a working
graphics driver and so it's using slow software rendering.
Please run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
dpkg -l > allpackages.txt
and attach the resulting text files here.
** Changed in: gnome-shell
Do you mean swipe up from the "bottom" of the touch monitor?
** Tags added: touch touchscreen
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1966629
Title:
swipe up from the
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1910938
Title:
Text is missing from shell panel and menus
To manage notifications about
Public bug reported:
Can't move file/directory by drag and drop by using a touch monitor
OS: 22.04, up to date @ Mar 28, 2022.
nautilus: 1:42~rc-1-ubuntu1
mode: wayland
** Affects: oem-priority
Importance: Wishlist
Status: New
** Affects: nautilus (Ubuntu)
Importance:
*** This bug is a duplicate of bug 1910938 ***
https://bugs.launchpad.net/bugs/1910938
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 1910938, so it is being marked as such. Please
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
You have been subscribed to a public bug:
After the most recent updates to the system, a new problem emerged where
after the system is running for a long period of time, text from the
system will slowly start to disappear and reduce usability of the system
overtime. It affects the top bar of the
1 - 100 of 109 matches
Mail list logo
