gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix
Attached is a debdiff that resolves the issue on Focal. Version 5.
** Patch added: "Debdiff for tracker-miners on Focal v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725476/+files/lp1779890_focal_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on Jammy. Version 5.
** Patch added: "Debdiff for tracker-miners on Jammy v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725475/+files/lp1779890_jammy_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on lunar. Version 5.
** Patch added: "Debdiff for tracker-miners on Lunar v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725474/+files/lp1779890_lunar_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on mantic. Version 5.
** Patch added: "Debdiff for tracker-miners on Mantic v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725473/+files/lp1779890_mantic_v5.debdiff
--
You received this bug
Attached is a debdiff that resolves this issue on debian unstable /
noble.
** Patch removed: "Debdiff for tracker-miners on Focal V3"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5679384/+files/lp1779890_focal_v3.debdiff
** Patch removed: "Debdiff
(justdenis) => Matthew Ruffell (mruffell)
** Changed in: gvfs (Ubuntu Mantic)
Importance: Unknown => Undecided
** Changed in: gvfs (Ubuntu Mantic)
Status: Confirmed => Invalid
** Changed in: gvfs (Ubuntu Noble)
Importance: Unknown => Undecided
** Changed in: gvfs (
Upstream bug: https://gitlab.gnome.org/GNOME/glib/-/issues/3185
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3185
https://gitlab.gnome.org/GNOME/glib/-/issues/3185
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when attempting to
** Also affects: gvfs (Ubuntu Mantic)
Importance: Unknown
Status: New
** Also affects: tracker-miners (Ubuntu Mantic)
Importance: High
Assignee: Denison Barbosa (justdenis)
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Attached is a v4 for Jammy that updates the version to ubuntu0.1 in both
d/changelog and d/tracker-extract.postinst
** Patch added: "Debdiff for tracker-miners on Jammy V4"
Attached is a V3 debdiff for Mantic that fixes this issue
** Patch added: "Debdiff for tracker-miners on Mantic V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679388/+files/lp1779890_mantic_v3.debdiff
--
You received this bug notification because you
Attached is a V3 debdiff for Lunar that fixes this issue
** Patch added: "Debdiff for tracker-miners on Lunar V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679387/+files/lp1779890_lunar_v3.debdiff
--
You received this bug notification because you are
Attached is a V3 debdiff for Kinetic that fixes this issue
** Patch added: "Debdiff for tracker-miners on Kinetic V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679386/+files/lp1779890_kinetic_v3.debdiff
--
You received this bug notification because
Attached is a V3 debdiff for Jammy that fixes this issue
** Patch added: "Debdiff for tracker-miners on Jammy V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679385/+files/lp1779890_jammy_v3.debdiff
--
You received this bug notification because you are
Attached is a V3 debdiff for Focal that fixes this issue
** Patch removed: "debdiff for tracker-miners on jammy"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663488/+files/lp1779890_jammy_v2.debdiff
** Patch removed: "debdiff for tracker-miners on
** Patch removed: "debdiff for tracker-miners on Focal"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663487/+files/lp1779890_focal.debdiff
** Patch removed: "Debdiff for tracker-miners fix on Kinetic"
Attached is a v2 debdiff for Focal, after Denison correctly pointed out
that I was missing a patch.
** Description changed:
[ Impact ]
The KRB5CCNAME environment variable points to the Kerberos ticket of the
current machine and this ticket is used for authentication in Active
Attached is a v2 debdiff for kinetic. Again, minor changes, corrected
version, dep3 tags.
** Patch added: "debdiff for tracker-miners on kinetic"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663489/+files/lp1779890_kinetic_v2.debdiff
--
You received
Attached is a v2 debdiff for Jammy. Very minor changes, corrected
version, tidied up dep3 tags.
** Patch added: "debdiff for tracker-miners on jammy"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663488/+files/lp1779890_jammy_v2.debdiff
--
You received
Attached is a debdiff for Focal.
** Patch added: "debdiff for tracker-miners on Focal"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5663487/+files/lp1779890_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Description changed:
[ Impact ]
- The KRB5CCNAME environment variable points to the Kerberos ticket of the
current machine and this ticket is used for authentication in Active Directory
servers.
+
+ The KRB5CCNAME environment variable points to the Kerberos ticket of the
+ current
cal)
Importance: Undecided => Medium
** Changed in: tracker-miners (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad
** Changed in: tracker-miners (Ubuntu Jammy)
Status: New => In Progress
** Changed in: tracker-miners (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: tracker-miners (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: tracker-miners (Ubuntu Kinetic)
I built the patch Jan provided into a test package, available in the
below ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1967843-test
When I install it, the testcase is fixed, shown in the attachment, and
cheese works as normal.
Jeremy, shall we submit the patch to Debian, and SRU to
Hi renbag,
Thanks for attaching your smb.conf and sssd.conf, I will try add them
into my reproducer and see if I get closer to seeing the problem.
Maybe when you log in, smbd mounts the samba shares to
/home/aduser/{Public},{Shared} before kerberos manages to acquire a new
ticket and place it in
Hi everyone, Fady, renbag,
I have been working on this bug on and off for a little while now, but I
am stuck because I can't reproduce what you are all seeing. Having a
reproducer will greatly speed up getting a fix created for this issue.
In my client gvfsd is always started via systemd --user,
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
Hi Daniel,
I built "clutter: Mark clutter_stage_grab() return value as transfer
full" from https://gitlab.gnome.org/GNOME/mutter/-/issues/2189 into
mutter 42~beta-1ubuntu2 in a ppa and installed it.
I rebooted, and changed back to 1 minute fade time, and reproduced the
issue, so that particular
I have installed gsettings-desktop-schemas 42~rc-1ubuntu3 from the
release pocket, and the dark theme migration took place. All of my
applications are now consistently dark themed again, including gnome-
disks, nautilus, calculator and calendar. When swapping from light to
dark, the change is
Hi Sebastien,
Thankyou for your suggestion about libhandy-1. I had 1.5.91-2 installed.
I downgraded to 1.5.91-1 and my issue vanished, nautilus, gnome-disks
and calendar are back to dark theme now.
On 1.5.91-2, toggling back and forth between light and dark did not do
anything.
Tagging
I use the wayland session. I have recorded a short screencast of
reproducing the issue. I went gnome settings > power > screen blank > 1
minute to speed it up.
The screencast has journalctl -f running, and there is no output.
Interestingly, after enough clicks it seemed to start working again.
Actually, Nautilus has started doing it now as well. gedit still uses
yaru. calculator uses yaru. calendar uses adwaita. Maybe my system is
cursed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
Public bug reported:
gnome-disks does not apply the Yaru theme, when all other GNOME
applications respect the default theme.
See attached screenshot.
gnome-disks 42~rc-1ubuntu1
gnome-shell 42~beta-1ubuntu2
yaru-theme-gtk 22.04.1
** Affects: gnome-disk-utility (Ubuntu)
Importance:
gnome-disks is using adwaita instead of Yaru.
** Attachment added: "Screenshot of incorrect theme"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1965067/+attachment/5569412/+files/Screenshot%20from%202022-03-16%2015-08-41.png
** Also affects: gnome-disk-utility (Ubuntu
Managed to reproduce at again, this time at 15:54.
** Attachment added: "Second reproduction logs"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+attachment/5568923/+files/repro2.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I finally managed to reproduce it, and I have
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 set.
Attached is journalctl. It happened at 15:29 March 15. (edit, actually
15:29)
** Attachment added: "journal of repro"
Hi Jeremy,
Sorry, I should have rebooted first. The settings link is there and it
works. Happy to say verified.
--
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/1964136
Title:
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567874/+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/1964539/+attachment/5567871/+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: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567873/+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: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567870/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567872/+files/ProcEnviron.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
** Tags added: apport-collected package-from-proposed third-party-
packages wayland-session
** Description changed:
[Impact]
Occasionally, when the screen has been locked for a medium length of
time, > 5 mins, when you press the spacebar, enter your password, the
Just to clarify, we will be adding the option to launch gnome-control-
center from the system menu? I keep finding myself trying to launch it
from there to check sound settings before meetings, but it is missing,
and have to launch from overview instead.
I think this is a feature that LTS users
** Also affects: gnome-shell (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: jammy
--
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/1964539
Title:
** Also affects: gnome-shell (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: jammy
--
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/1964541
Title:
Public bug reported:
[Impact]
If you move the mouse as the system fades into black for the
screensaver, the screensaver will be prevented as normal, but the user
will not be able to interact with the shell.
Mouse clicks are ignored, and most key presses are ignored too.
Workaround is to press
Public bug reported:
Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
attempting to re-arrange tabs in Firefox fails. Click and drag the tab
and release, nothing changes. The next click to the tab is ignored.
syslog has the following:
Mar 11 13:06:47 desktop firefox[2192]:
** Attachment added: "Primary screen stuck, secondary is unlocked"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+attachment/5567839/+files/IMG_20220311_122713.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Public bug reported:
[Impact]
Occasionally, when the screen has been locked for a medium length of
time, > 5 mins, when you press the spacebar, enter your password, the
primary display freezes and the lockscreen slider does not slide up. The
secondary screen is fine, and unlocks.
See screenshot
Performing verification for Focal.
I will first reproduce the problem with glib2.0 2.64.6-1~ubuntu20.04.3
from -security with the libglib2.0-0 libglib2.0-bin libglib2.0-data
packages.
I deleted all existing schemas from /usr/share/glib-2.0/schemas and
replaced them with a set of schemas which
Attached is a debdiff for glib2.0 on Focal which fixes this problem.
** Patch added: "Debdiff for glib2.0 for Focal"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1930359/+attachment/5510466/+files/lp1930359_focal.debdiff
** Tags removed: regression-update
** Tags added: sts-sponsor
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Focal)
** Changed in: glib2.0 (Ubuntu)
Status: New => Fix Released
** Changed in: glib2.0 (Ubuntu Focal)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu Focal)
Importance: Undecided => High
Hi Daniel,
Yes, I am sure this is the same issue that they are experiencing there,
and I now believe the issue lies in glib, and not mutter.
When we install mutter-common, it calls the libglib2.0-0 hook to
recompile the gsettings schemas.
The customer provided me with a tarball of their
Okay, the affected user has now started experiencing the issue again,
and was forced to roll mutter back on their fleet.
We managed to get some logs this time, and we have determined what is
happening.
When the user upgrades the mutter packages, particularly mutter-common,
the libglib2.0-0 hook
The affected user cannot reproduce the issue anymore. The new mutter
packages install fine in their environment, and gdm starts every time.
They have since rolled out the new mutter packages to their fleet
without any issues.
I'm going to mark this bug as invalid, as we can't reproduce the issue
** Attachment added: "screenshot of working gdm on AWS"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+attachment/5505412/+files/Screenshot%20from%202021-06-18%2013-40-15.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I spent some time attempting to reproduce on AWS today, using a
g4dn.xlarge instance, which has a Nvidia Tesla T4 GPU, which supports
GRID.
I installed ubuntu-desktop-minimal and rebooted, and gdm started fine
with mutter 3.36.9-0ubuntu0.20.04.1. I confirmed this by looking at the
instance
I built a test package based on mutter 3.36.9-0ubuntu0.20.04.1, and
reverted the three commits introduced by LP #1905825, namely:
commit: 92834d8feceeac538299a47a8c742e155de4e6e8
From: Kai-Heng Feng
Date: Mon, 21 Dec 2020 14:34:43 +0800
Subject: renderer/native: Refactor modeset boilerplate into
Hello,
Just a note that mutter 3.36.9-0ubuntu0.20.04.1 has introduced a
regression in a VMware Horizon VDI environment, where gdm fails to
start, and has taken out several hundred VDIs.
I am tracking the issue in bug 1930359.
The plan is to make a test package with the patches from bug 1905825
Hello,
Just a note that mutter 3.36.9-0ubuntu0.20.04.1 has introduced a
regression in a VMware Horizon VDI environment, where gdm fails to
start, and has taken out several hundred VDIs.
I am tracking the issue in bug 1930359.
The plan is to make a test package with the patches from bug 1905825
.
Currently looking into what landed in bug 1919143 and bug 1905825.
[Testcase]
[Where problems can occur]
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Affects: mutter (Ubuntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status
Attached is a debdiff for Hirsute which re-applies "screen: Use clean
env when creating new tab" and is the same patch in the PPA.
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully
** Description changed:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that
It seems the revert for "screen: Use clean env when creating new tab" is
already in 3.38.1, and I checked the Ubuntu source package, and the
revert is in place.
https://gitlab.gnome.org/GNOME/gnome-
terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
Interesting.
I might try a test build
Performing verification for Bionic.
I want to say straight up, I haven't been able to reproduce the problem,
I have tried many mechanisms, but I can not reproduce the 20 second
shell hang and crash, as documented in https://github.com/GSConnect
Might also be related:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1922839
Title:
Opening new tab in
Seems this is a long running issue.
Upstream bug:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #253
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253
** Bug watch added:
Public bug reported:
[Impact]
If you launch gnome-terminal by right clicking a directory in Nautilus,
selecting "Open in Terminal", you get a fully functional terminal
window.
If you then press the new tab button, or ctrl-shift-t to open a new
terminal tab, you will find that most environment
Version tested in hirsute is 3.38.1-1ubuntu1.
I checked Groovy, with 3.38.0-1ubuntu1.1, and the problem does not happen.
Both systems using Wayland session.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Performing verification for gnome-shell in Bionic.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
Performing verification for gnome-shell in Focal.
During this verification I will explain how VMware Horizon SSO works,
and will prove that the gnome-shell in -proposed is equivalent to the
custom gnome-shell package distributed by VMware.
I will begin by walking through the SSO workflow, based
Attached is a debdiff for gnome-shell for Focal with the required
patches to implement VMware Horizon SSO support.
** Patch added: "gnome-shell debdiff for Focal"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886592/+attachment/5423914/+files/lp1886592_focal.debdiff
--
You
Attached is a debdiff for Bionic which implements support for VMware
Horizon SSO in gnome-shell.
** Patch added: "gnome-shell debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886592/+attachment/5423915/+files/lp1886592_bionic.debdiff
--
You received this bug
** Description changed:
[Impact]
VMware Horizon is a VDI product that runs atop of VMware's normal
virtualisation stack, and it supports SSO authentication for login.
In the past, the VMware Horizon agent has been pretty buggy, and
requires SSO patches to be present to function,
nee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Affects: gnome-shell (Ubuntu Eoan)
Importance: Undecided
Status: Won't Fix
** Af
Oops, sorry. I rebooted my machine and the problem does not reproduce,
since I installed 3.36.0-2ubuntu2 and hadn't rebooted.
** Changed in: gnome-shell (Ubuntu Focal)
Status: Incomplete => Fix Released
** Tags removed: champagne
--
You received this bug notification because you are a
Attached is a screencast demonstrating the problem.
** Attachment added: "Screencast of virtual desktops breaking"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+attachment/5343942/+files/Screencast%20from%2001-04-20%2011%3A08%3A18.webm
--
You received this bug
Public bug reported:
gnome-shell: virtual desktops broken as windows appear on every desktop,
regardless of where they are placed
On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you
open a few applications, such as gnome-disks, nautilus and firefox, then
move a window to a
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Low
Status: Fix Released
** Also affects: yaru-theme (Ubuntu Focal)
I did some extensive digging and found why it is fixed in Adwaita and
not Yaru.
Two weeks ago, the below commit was merged to gnome-shell. It checks to
see if the string width is longer than the box width, and if it is, it
switches to a hardcoded "leightweight" width of 13pt.
commit
I found the bug. The font-size is too large in .message-dialog-content
.message-dialog-title.
It is set to 18pt, but the largest it should be is 13pt.
Attached is a picture demonstrating each font size, no other changes made.
** Attachment added: "Comparison of font sizes"
I went and checked Yaru theme from Eoan, and the dialogue is displayed
correctly. Maybe something broke on the move to the new dialogue box? Attached
is the same gnome-disks dialogue on Eoan.
I still think the issue is the font is too big on the title of the new Yaru
theme dialogue box.
**
Hello MadsRH and Daniel,
I checked the Adwaita theme, and no text clipping is seen, and things are as
expected. Attached is a screenshot of the same gnome-disks password dialogue in
Adwaita.
** Attachment added: "Screenshot of Adwaita password overlay box"
Public bug reported:
If you have a password overlay dialogue box present on your screen, for
example, trying to mount an encrypted disk image from gnome-disks, or
trying to unlock an ssh key, if the lock screen appears while the
dialogue is in place, after unlocking the screen, you can still
I opened an issue upstream: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/2321
--
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/1866275
Title:
Password overlay dialogue
Public bug reported:
On Focal, if you go to the 'About' pane in gnome-control-center, a large
GNOME icon is displayed. On previous releases, usually an Ubuntu logo is
displayed instead.
Is this change intentional? Or did upstream GNOME change a file name or
something?
Attached is a screenshot.
** Information type changed from Private to Public
--
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/1858857
Title:
gnome-calendar: Hits assert when timezone set to Etc/UTC
90 matches
Mail list logo
