[Bug 1967450] Re: When switching from fractional scaling back to integer scaling, only part of the screen is used

** Summary changed: - When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used + When switching from fractional scaling back to integer scaling, only part of the screen is used -- You received this bug notification because you are a member of

[Bug 2031077] Re: When I change to fractional scaling and back, display doesn't maximize

*** This bug is a duplicate of bug 1967450 *** https://bugs.launchpad.net/bugs/1967450 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 1967450, so it is being marked as such. Please

[Bug 2031077] Re: When I change to fractional scaling and back, display doesn't maximize

*** This bug is a duplicate of bug 1967450 *** https://bugs.launchpad.net/bugs/1967450 Thanks for the bug report. I have seen this happen a few times myself but had not been able to reproduce it reliably enough to follow up on. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed

[Bug 2031077] [NEW] When I change to fractional scaling and back, display doesn't maximize

You have been subscribed to a public bug: When I go to the display settings and I change to fractional scaling (150% is what I used) and I turn off fractional scaling, the display doesn't maximize to the full screen size. I need to manually set it to 200% and then back to 100% for the display to

[Bug 1916372] Re: GIMP CRASHED ON ACCESS OILIFY

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gimp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu.

[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libcanberra (Ubuntu Kinetic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1983794] Re: Evolution not deleting autosave files

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: evolution (Ubuntu Kinetic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1983794] Re: Evolution not deleting autosave files

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libcanberra (Ubuntu Kinetic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: tracker-miners (Ubuntu Kinetic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1968333] Re: FTBFS

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: indicator-keyboard (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1980334] Re: Support Quectel's modem(EM120/160) firmware update, fwupd

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-software (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed

[Bug 1980334] Re: Support Quectel's modem(EM120/160) firmware update, fwupd

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-firmware (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed

[Bug 1991263] Re: duplicate appindicators

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-shell-extension-appindicator (Ubuntu Kinetic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1995349] Re: [goodix] The enrolled finger is unknown to device

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libfprint (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 2003732] Re: Update mutter to 43.2

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Kinetic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media

** Package changed: gnome-control-center (Ubuntu) => gsettings-desktop- schemas (Ubuntu) ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 2030963] Re: default theme highlights hard to see

** Package changed: gnome-shell (Ubuntu) => yaru-theme (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/2030963 Title: default theme highlights hard to see To manage

[Bug 2030963] [NEW] default theme highlights hard to see

Public bug reported: In 22.04's default theme, it's almost impossible for me to make out which app or window is the currently selected one in the window switcher (alt-tab) or the application switcher (super-tab). The "highlighted" item is just a slightly different shade of grey. I mean, I can

[Bug 2030959] Re: Cursor sometimes stutters after heavy shell animations in 42.9

** Description changed: Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur. This is different to the recent bug fix that probably caused it: Bug 2023766:  

[Bug 2023766] Re: Mouse cursor stutters over GUI elements that are animated

** Changed in: mutter (Ubuntu Lunar) 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. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters over GUI

[Bug 2030959] Re: Cursor sometimes stutters after heavy shell animations in 42.9

** Description changed: Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur. This is different to the recent bug fix that probably caused it: Bug 2023766: -  

[Bug 2030959] [NEW] Cursor sometimes stutters after heavy shell animations in 42.9

Public bug reported: Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur. This is different to the recent bug fix that probably caused it: Bug 2023766:  * only occurs when

[Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)

Then I tried to suspend; resume with monitor attached. Didn't work either - see second log file. (One thing I'm wondering: I *am* using the same brand and type of monitor, connected to the same brand and type of dock, at *different places*. Could that be the culprit? I.e. having used the LG

[Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)

Connecting the dock without monitor is fine. Then connecting the DisplayPort connector: aug 10 10:40:28 X1-carbon thunderbird[95811]: Couldn't map window 0x7f892a156640 as subsurface because its parent is not mapped. aug 10 10:40:28 X1-carbon thunderbird[95811]: Couldn't map window

[Bug 2030947] Re: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed`

Thanks for the bug report. This looks like a leak. Since I can't find any other reports of this in Ubuntu or upstream yet, please try disabling all extensions and then log in again. ** Tags added: gnome-shell-leak logspam ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete --

[Bug 2030947] [NEW] gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed`

Public bug reported: gnome-shell logs gnome-shell[4537]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed multiple times per second for weeks now. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 44.3-1ubuntu1

[Bug 2012978] Re: Memory leak

It was reverted from the archive. Jammy is back on 1.72.2-0ubuntu2 now. > @sil2100: Hey! The package was phased to 0 instantly from 10% with a lot of error reports ** Changed in: gjs (Ubuntu Jammy) Status: Fix Released => Triaged -- You received this bug notification because you are a

[Bug 2023572] Re: SRU gjs 1.72.4 to jammy

It was reverted from the archive. Jammy is back on 1.72.2-0ubuntu2 now. > @sil2100: Hey! The package was phased to 0 instantly from 10% with a lot of error reports ** Changed in: gjs (Ubuntu Jammy) Status: Fix Released => Triaged -- You received this bug notification because you are a

[Bug 2030937] Re: gnome-software crashed with SIGABRT in g_assertion_message_expr()

*** This bug is a duplicate of bug 2028071 *** https://bugs.launchpad.net/bugs/2028071 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 #2028071, so is being marked as such.

[Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in