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

2023-08-10 Thread Daniel van Vugt
** 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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967450

Title:
  When switching from fractional scaling back to integer scaling, only
  part of the screen is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967450/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Daniel van Vugt
*** 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 look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1967450
   When switching from 175% fractional scaling back to integer scaling, only a 
quarter of the screen is used

-- 
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/2031077

Title:
  When I change to fractional scaling and back, display doesn't maximize

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2031077/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Daniel van Vugt
*** 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 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.
https://bugs.launchpad.net/bugs/2031077

Title:
  When I change to fractional scaling and back, display doesn't maximize

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2031077/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Launchpad Bug Tracker
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 go back to the normal
size. My display resolution is 2560x1440 but when it goes back to the
normal scaling from fractional, it displays a size on my screen similar
to 1920x1080

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 11 10:28:33 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] [1025:1534]
 NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GA106M [GeForce RTX 3060 Mobile / Max-Q] 
[1025:1547]
InstallationDate: Installed on 2023-07-18 (23 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: Acer Predator PH315-54
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=22124f54-0947-42a4-b5dc-8110372b8f54 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevDb: Error: command ['udevadm', 'info', '--export-db'] failed with exit code 
-11:
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2022
dmi.bios.release: 1.12
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: QX60_TLS
dmi.board.vendor: TGL
dmi.board.version: V1.12
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd06/07/2022:br1.12:efr1.9:svnAcer:pnPredatorPH315-54:pvrV1.12:rvnTGL:rnQX60_TLS:rvrV1.12:cvnAcer:ct10:cvrV1.12:sku:
dmi.product.family: Predator Helios 300
dmi.product.name: Predator PH315-54
dmi.product.sku: 
dmi.product.version: V1.12
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug jammy third-party-packages ubuntu wayland-session
-- 
When I change to fractional scaling and back, display doesn't maximize
https://bugs.launchpad.net/bugs/2031077
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to mutter in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1916372] Re: GIMP CRASHED ON ACCESS OILIFY

2023-08-10 Thread Launchpad Bug Tracker
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.
https://bugs.launchpad.net/bugs/1916372

Title:
  GIMP CRASHED ON ACCESS OILIFY

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1916372/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Utkarsh Gupta
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 subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1949200

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983794] Re: Evolution not deleting autosave files

2023-08-10 Thread Utkarsh Gupta
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 subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1983794

Title:
  Evolution not deleting autosave files

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983794] Re: Evolution not deleting autosave files

2023-08-10 Thread Utkarsh Gupta
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 subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1983794

Title:
  Evolution not deleting autosave files

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Utkarsh Gupta
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 subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1779890

Title:
  gvfsd process does not have the KRB5CCNAME environment set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1968333] Re: FTBFS

2023-08-10 Thread Utkarsh Gupta
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 subscribed to indicator-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1968333

Title:
  FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1968333/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Utkarsh Gupta
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 to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1980334

Title:
  Support Quectel's modem(EM120/160) firmware update, fwupd

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1980334/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Utkarsh Gupta
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 to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1980334

Title:
  Support Quectel's modem(EM120/160) firmware update, fwupd

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1980334/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1991263] Re: duplicate appindicators

2023-08-10 Thread Utkarsh Gupta
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 Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1991263

Title:
  duplicate appindicators

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1991263/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Utkarsh Gupta
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 libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1995349

Title:
  [goodix] The enrolled finger is unknown to device

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint/+bug/1995349/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2003732] Re: Update mutter to 43.2

2023-08-10 Thread Utkarsh Gupta
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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2003732

Title:
  Update mutter to 43.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003732/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Jeremy Bícha
** 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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1983778

Title:
  Major security issue in Ubuntu Desktop default config - Removable
  Media

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1983778/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Jeremy Bícha
** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2030963/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Christian Pernegger
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 make it
out if I squint at it, but ... that just isn't a *highlight*. This is a
use where Ubuntu Orange shines, too. :-(

Similarly, the active workspace in the workspace overview (?) does get
an orange frame, but it's very thin, much too thin to see unless you
look closely. Again, that's not a highlight. A highlight is supposed to
pop out.

In comparison, the highlighting for the current tab in Terminal is ok-
ish. I'd *prefer* for the entire tab to become orange, or to become a
lighter colour in addition to the orange bar, but it's usable.

"Ok, boomer, you're blind. I can see that just fine". Fair enough. Are
you under thirty and (thus still) have 20:20 vision, by any chance? The
point is, it isn't good UI design either way. What's worse, the high
contrast accessibility setting doesn't touch any of it, and that is
definitely a bug.

(I could go on. For example, windows' title bars are now white vs the iconic 
Ubuntu Brown, which makes it hard to tell where the title bar is vs the window 
contents. Many applications also have buttons in the title bar now. It's no 
longer possible to just grab a window and move it on auto-pilot ... If the 
title bar can't be a different colour any more, at least separate it with a 
thick line or something.
In any case, 22.04 is a massive regression in terms of visual UI design vs 
18.04. Form should follow function, not the other way around.)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
Uname: Linux 6.2.0-1009-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 10 12:58:31 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-02 (7 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
RelatedPackageVersions: mutter-common 42.9-0ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2030963/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Daniel van Vugt
** 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:
   * only occurs when moving over animated GUIs.
   * never recovers or corrects itself.
   * was spatial jittering at full frame rate.
-  * reduced the frame rate of the GUI below it.
+  * reduced the frame rate of the GUI below it.
  
  This bug:
   * only occurs when moving over non-animated GUIs.
   * does recover and correct itself.
   * is stuttering at seemingly half frame rate, but perfect spatially.
-  * does not reduce the frame rate of the the GUI below.
+  * does not reduce the frame rate of the the GUI below.
+ 
+ I think the reason we only see this in 42 (jammy) is because that
+ predates the change in the triple buffering algorithm to scale based on
+ "dynamic max render time" alone.

-- 
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/2030959

Title:
  Cursor sometimes stutters after heavy shell animations in 42.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Daniel van Vugt
** 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 elements that are animated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Daniel van Vugt
** 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:
-  * only occurs when moving over animated GUIs
-  * never recovers or corrects itself
+  * only occurs when moving over animated GUIs.
+  * never recovers or corrects itself.
   * was spatial jittering at full frame rate.
+  * reduced the frame rate of the GUI below it.
  
  This bug:
-  * only occurs when moving over non-animated GUIs
-  * does recover and correct itself
+  * only occurs when moving over non-animated GUIs.
+  * does recover and correct itself.
   * is stuttering at seemingly half frame rate, but perfect spatially.
+  * does not reduce the frame rate of the the GUI below.

-- 
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/2030959

Title:
  Cursor sometimes stutters after heavy shell animations in 42.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Daniel van Vugt
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 moving over animated GUIs.
 * never recovers or corrects itself.
 * was spatial jittering at full frame rate.
 * reduced the frame rate of the GUI below it.

This bug:
 * only occurs when moving over non-animated GUIs.
 * does recover and correct itself.
 * is stuttering at seemingly half frame rate, but perfect spatially.
 * does not reduce the frame rate of the the GUI below.

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: mutter (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Daniel van Vugt (vanvugt)
 Status: New


** Tags: cursor performance regression-update

** Also affects: mutter (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu)
   Status: New => Invalid

** Changed in: mutter (Ubuntu Jammy)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** 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:
-  * only occurs when moving over animated GUIs
-  * never recovers and corrected itself
-  * was spatial jittering at full frame rate.
+  * only occurs when moving over animated GUIs
+  * never recovers or corrects itself
+  * was spatial jittering at full frame rate.
  
  This bug:
-  * only occurs when moving over non-animated GUIs
-  * does recover and correct itself
-  * is stuttering at seemingly half frame rate, but spatially perfectly spaced.
+  * only occurs when moving over non-animated GUIs
+  * does recover and correct itself
+  * is stuttering at seemingly half frame rate, but perfect spatially.

-- 
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/2030959

Title:
  Cursor sometimes stutters after heavy shell animations in 42.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

2023-08-10 Thread Valentijn Sessink
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 Electronics
HDR 4K somewhere, then attaching the laptop to the same brand and type
of monitor at a different place, with a different dock, would that
possibly lead to this behaviour? Could others comment on this, i.e. do
you experience this behaviour when using a single dock / single work
place?)

** Attachment added: "journal2.log"
   
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+attachment/5691434/+files/journal2.log

-- 
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/1970495

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[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)

2023-08-10 Thread Valentijn Sessink
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 
0x7f890f70caa0 as subsurface because its parent is not mapped.
aug 10 10:40:28 X1-carbon thunderbird[95811]: Couldn't map window 
0x7f890f70d600 as subsurface because its parent is not mapped.
[...] continues this way, until more alarming messages start showing up, 
"gnome-shell[2767]: WL: error in client communication (pid 151710)" and finally 
"gnome-shell[2767]: WL: error in client communication (pid 2767)" and  journal 
is added as attachment. Eventually I'm removing the monitor cable again and 
things come to a rest.


** Attachment added: "journal.log"
   
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+attachment/5691432/+files/journal.log

-- 
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/1970495

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1970495/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Daniel van Vugt
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

-- 
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/2030947

Title:
  gnome-shell spams journal with `g_closure_add_invalidate_notifier:
  assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2030947/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Julian Andres Klode
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
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Aug 10 10:38:23 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-11-26 (256 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
RelatedPackageVersions: mutter-common 44.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic third-party-packages wayland-session

-- 
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/2030947

Title:
  gnome-shell spams journal with `g_closure_add_invalidate_notifier:
  assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2030947/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2012978] Re: Memory leak

2023-08-10 Thread Daniel van Vugt
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 member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978

Title:
  Memory leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2023572] Re: SRU gjs 1.72.4 to jammy

2023-08-10 Thread Daniel van Vugt
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 member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2023572

Title:
  SRU gjs 1.72.4 to jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Apport retracing service
*** 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.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2030937/+attachment/5691391/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/2030937/+attachment/5691393/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2030937/+attachment/5691396/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2030937/+attachment/5691397/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/2030937/+attachment/5691398/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2030937/+attachment/5691399/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2030937/+attachment/5691400/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 2028071

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/2030937

Title:
  gnome-software crashed with SIGABRT in g_assertion_message_expr()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2030937/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2023-08-10 Thread Andy Chi
** 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
  js::gc::Cell::storeBuffer() from
  js::gc::PostWriteBarrierImpl()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs