Maybe start by removing the package 'sabily-gdm-themes'
--
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/1972080
Title:
GNOME (non-Ubuntu) login screen mouse cursor is a
The photos in comments #12 and #13 show the Ubuntu Yaru theme is not
being used (missing the logo aside from this cursor bug), so it makes
some sense if whatever theme that is requires more of Adwaita than
regular Ubuntu does.
** Summary changed:
- [mgag200] Mouse cursor is a semi-opaque white
You have been subscribed to a public bug:
Do not think this is hardware dependent, but I'm using an HPE
MicroServer Gen10 Plus.
I installed the server edition of 22.04. Post-Installation, I added
some desktop environments. After logging in, these are working fine.
However on the gdm login
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
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 1961508, so it is being marked as such. Please
Thanks for the bug report.
Screen tearing during mode changes is somewhat normal. Even more normal
and even more visible in VMs. If that's the only problem then this may
not really be a fixable bug. But I am only guessing. Please provide a
video of the issue so we can confirm.
** Package
Nick,
Please look at https://errors.ubuntu.com/user/ID where ID is the content
of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any
links to recent problems on that page? If so then please send the links
to us.
Please also reproduce the bug again and as soon as it happens run:
Please try selecting 'Ubuntu on Xorg' on the login screen.
Please also upgrade to Ubuntu 22.04 as soon as you can.
--
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/1973143
Title:
Invalid then I suppose.
** Changed in: mutter (Ubuntu)
Status: New => Invalid
--
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/1972749
Title:
Logging into a second Wayland
This bug is closed.
But screen sharing is expected to be broken on Chromium+Wayland due to
bug 1897454.
--
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/1950040
Title:
Wayland
Please try selecting the Xorg option on the login screen. It will either
be called 'Ubuntu on Xorg' or just 'Ubuntu'.
--
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/1970291
Title:
I have installed the updated packages and restarted. Evolution and GNOME
Calendar both still work fine.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** No longer affects: cheese (Ubuntu Jammy)
** Changed in: clutter-gst-3.0 (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: clutter-gst-3.0 (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop
Because this affects more than just Firefox, I am removing the Firefox
task.
I wasn't able to reproduce this bug if I did these steps:
sudo apt uninstall xdg-desktop-portal-gnome
Log out and log back in
Now, snaps will use xdg-desktop-portal-gtk instead.
Therefore, I believe this is a bug in
This bug may be mutter/wayland related as the player seems to work in
xorg but not wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1969512
Title:
Totem unable to play video:
Thanks for your report.
This is a design matter and should better be reported upstream:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
If you report it there, please post the URL to the upstream issue here
for tracking purposes.
P.S. Good that you figured out how to set it via
modinfo nvidia-drm
modinfo: ERROR: Module nvidia-drm not found.
modinfo nvidia_drm
modinfo: ERROR: Module nvidia_drm not found.
modinfo nvidia
filename:
/lib/modules/5.4.0-110-generic/kernel/drivers/char/drm/nvidia.ko
inxi -G
Graphics: Device-1: NVIDIA GT218 [GeForce 210] driver:
Public bug reported:
In Ubuntu 20.04, I was able to set Left Ctrl as my Compose key using
gnome-tweaks. I just upgraded to 22.04, where the Compose key settings
have been removed from gnome-tweaks and moved into control-center, but
Left Ctrl is not in the list of options for Compose.
I was able
I can't confirm that the description matches my issue but maybe it is
the same. So here is my own description:
I use the same monitor 1440p, keyboard and mouse connected via HDMI to
older MacBook Pro and dual boot Laptop (Ubuntu + Win10) with Hybrid
graphics Intel 630HD and GeForce 1050Ti.
Public bug reported:
Impact
--
There is a new point release in the stable GTK 4.6 series.
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.3/NEWS
Also, we are cherry-picking a few patches
- Work around infinite loop in box allocation (Closes: #1010547)
- Make it easier to select the current
but it doesn't show in your lsmod.
how about `modinfo nvidia_drm`?
--
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
Sorry, this is a WONTFIX for Ubuntu 22.04 LTS. Ubuntu 22.04 LTS uses
gnome-control-center 41 which doesn't support setting a theme at all,
except in an Ubuntu-specific patch. If you want the Ubuntu experience,
use the Ubuntu session. If you want the GNOME experience, use the GNOME
session but then
Hi,
I do not remember blacklisting nvidia-drm intentionally, but will check !
Anyway don't you think this line from journalctl:
kernel: [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0
indicates nvidia-drm is fine ?
Running Mint 20.3 still with kernel 5.4 if that matters
update:
no transition plan for nvidia-340.
Then let's see why your nvidia-drm gone.
--
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
** Package changed: nautilus (Ubuntu) => gtk4 (Ubuntu)
** Changed in: gtk4 (Ubuntu)
Importance: Low => High
** Changed in: gtk4 (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- File save/download from all browsers fails to save when file name box is not
active.
+
My Chromium 101.0.4951.54 on 22.04 cannot share screen in Big Blue
Button – the shared image ist just black with the mouse pointer.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Hi,
@Daniel van Vugt (vanvugt), I give you a report.
I have been rebooted my laptop and repeated the problem again, but I
didn't find a file *.crash in /var/crash directory. Apparently, the
problem is not crash (it's my opinion), because Operation System does't
show error messages on my screen,
ok, I aware the `nvidia-drm` should support in nvidia-340.
Did you blacklist it?
Can you check the nvidia-drm whether presenting in your system?
you could probably found it under
find ... /lib/modules/$(uname -r)/...
--
You received this bug notification because you are a member of Ubuntu
Hi,
I aware you don't have "nvidia_drm" which is needed for gdm as well.
u-d-c was wait the "nvidia_drm" be probed and your nvidia driver is 340 is
quite old as what I known.
FWIK, the legacy driver should be nvidia-390 and the next is 470.
I wondering why nvidia-340 is not yet be transited to
Still having upload trouble, i'll find a way to get a crash-report
through another means
** Attachment added: "upload failure crash report"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+attachment/5589244/+files/Screenshot%20from%202022-05-12%2008-47-13.png
--
You
An additional data point; I noted in the linked gitlab bug a couple of
messages noting that "it works with the flatpak". Out of curiosity (as
to whether this might be a well and truly arm64 specific problem), I
tried the flatpak on the pi desktop and: it's got exactly the same
problem (same
I removed one of the extensions i was using, but still am running into
the issue.
1) I've got a crash report that still fails to upload.
```
-rw-r- 1 addyess whoopsie 94220558 May 12 08:03
_usr_bin_gnome-shell.1000.crash
-rw-rw-r-- 1 addyess whoopsie0 May 12 08:03
Public bug reported:
After using the session for a while with a normal workflow like switching
opened windows etc.
Some app windows's dimensions are changed automatically from the left side and
appears behind the dock as shown in the screenshot.
To correct it, the window must be resized and
After further investigation, I found the source of my issue.
Basically the / directory had the wrong ownership. Not sure how I did
that but it seemed to have the side-effect of making systemd-tmpfiles
not create directories as it should.
I saw messages like this in the log that clued me in.
The unit change mentioned before wasn't the right reference,
http://launchpadlibrarian.net/449200364/rygel_0.38.1-2ubuntu3.1_0.38.1-2ubuntu3.2.diff.gz
is a better example
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Unfortunately we've tried "G_DEBUG=fatal_warnings" before (you suggested
it back in comment:4) but I did manage to figure out a couple of things
since last time:
The crash I originally observed (back in comment:6) only occurs on the
very first run of totem. All subsequent runs (even after a
I am not sure and I currently do not have enough time to set up a vm and
re-test this, however the issue happened on a clean (fully updated)
22.04 installation, without any modifications.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1973156
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1971516 ***
https://bugs.launchpad.net/bugs/1971516
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
** This bug has been marked a duplicate of bug 1971516
File save/download from all browsers fails to save when file name box is not
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
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/1972079
Title:
Switching "High Contrast"
This bug also occurs in Ubuntu 22.04 (Jammy).
** Tags added: jammy
--
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/1973156
Title:
Strange graphical glitch during Ubuntu installation
It's the external monitor which is facing issue.
On Thu, 12 May 2022, 2:05 pm Daniel van Vugt, <1973...@bugs.launchpad.net>
wrote:
> Also which monitor is displaying the wrong resolution?
>
> ** Summary changed:
>
> - monitor resolution issue
> + Wayland session limited to 1024x768
>
> **
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm using the same
host system specs as in this bug report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150
While running the test, in
Also, if you have the time then please upgrade to Ubuntu 22.04. Ubuntu
21.10 will reach end-of-life in July.
https://wiki.ubuntu.com/Releases
** Summary changed:
- Wayland session limited to 1024x768
+ [impish] Wayland session limited to 1024x768
--
You received this bug notification because
Also which monitor is displaying the wrong resolution?
** Summary changed:
- monitor resolution issue
+ Wayland session limited to 1024x768
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1736
https://github.com/micheleg/dash-to-dock/issues/1736
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/1736
Importance: Unknown
Status: Unknown
--
You received this bug notification
I'm guessing this was fixed at some point between extension v33 (focal)
and v42 (jammy). Not sure where though.
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
*** This bug is a duplicate of bug 1910613 ***
https://bugs.launchpad.net/bugs/1910613
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 1910613, so it is being marked as such. Please
*** This bug is a duplicate of bug 1910613 ***
https://bugs.launchpad.net/bugs/1910613
Yes the recursion error looks like the issue. It's coming from:
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com
so please open the Extensions app (from package gnome-shell-extension-
49 matches
Mail list logo
