[Desktop-packages] [Bug 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)

[Philip M]

I was able to get something working on my win 11 i9-13900H discrete
RTX2000 laptop.

I used:
mks.enable3d = "TRUE"
mks.enableDX12Renderer = "TRUE"
mks.enableDX11Renderer = "FALSE"
mks.dx12.vendorID = "0x17AA" 

and I also had to do:
settings->system->dislay->graphics
entries for both vmware.exe and vmware-vmx.exe  (its in a subdirectory)
Both entries specify that vmware must run only on RTX2000 and not the cpu GPU.

Still seeing 
MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen 
but that might be known?
I dont think linux will be stable until you back off mesa to not have that 
error.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2061118

Title:
  Rendering issues in virtual machines (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Confirmed
Status in mesa source package in Noble:
  Triaged

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] Re: Unable to click on top left screen

[Yoann M]

Another screenshot that show the box size

** Attachment added: "ubuntu bug 2.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060665/+attachment/5771381/+files/ubuntu%20bug%202.png

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] Re: Unable to click on top left screen

[Yoann M]

First screenshot that show that seems to be a notification

** Attachment added: "ubuntu bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060665/+attachment/5771380/+files/ubuntu%20bug.png

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] Re: Unable to click on top left screen

[Yoann M]

I just got the bug again (you can see it's not very often)

I just sent the debug.

xwininfo is not working on that zone top left zone. I can't click on it.
I can only click outside this box.

I tried again with "lg", and the text show that it's some notification.
It's some "old" Skype notification.

Stopping Skype do not solve the issue, so I think it's linked with the
notification system.

(Note : My notifications are showned on bottom right of my screen, not
top left)

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] monitors.xml.txt

[Yoann M]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/2060665/+attachment/5771364/+files/monitors.xml.txt

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] ShellJournal.txt

[Yoann M]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/2060665/+attachment/5771363/+files/ShellJournal.txt

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] ProcEnviron.txt

[Yoann M]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2060665/+attachment/5771362/+files/ProcEnviron.txt

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] ProcCpuinfoMinimal.txt

[Yoann M]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2060665/+attachment/5771361/+files/ProcCpuinfoMinimal.txt

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] GsettingsChanges.txt

[Yoann M]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/2060665/+attachment/5771360/+files/GsettingsChanges.txt

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] Re: Unable to click on top left screen

[Yoann M]

apport information

** Tags added: apport-collected jammy third-party-packages wayland-
session

** Description changed:

  Random after some time, the top left of the screen can't be clicked (not
  even the mouse move event are dispatched to the window)
  
  Using the Wayland (Alt + F2) "lg" show that a transparent box (385 width
  x 56 height) is over, unable to close it
  
  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]
  
  It seems to be a notification window or something, and it's blocked
  here.
  
  The only way to fix it is to close the session, killing everything
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-01-01 (846 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ Package: gnome-shell 42.9-0ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
+ RelatedPackageVersions: mutter-common 42.9-0ubuntu7
+ Tags: third-party-packages wayland-session jammy
+ Uname: Linux 6.5.0-28-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2060665/+attachment/5771359/+files/Dependencies.txt

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-01 (846 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu7
  Tags: third-party-packages wayland-session jammy
  Uname: Linux 6.5.0-28-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

[Philip M]

Also tried virtualbox this morning on a different win 11 machine with an
nvidia laptop gpu and same thing.

No 3D acceleration is not stable on vmware (crashes after a while)
With 3D acceleration black screens really fast on vmware and virtualbox (which 
uses the vmware driver by default)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118

Title:
  Rendering issues in vmware with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  Triaged

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

[Philip M]

Microsoft Windows [Version 10.0.22631.3447]
Processor   AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16 
Logical Processor(s)
System ModelX570 AORUS PRO WIFI
RTX 2070

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118

Title:
  Rendering issues in vmware with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  Triaged

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2061118] Re: Rendering issues in vmware with 3d on (GTK ngl backend)

[Philip M]

vmware 17.5 win 11 
not fixed with todays iso. mesa is 24.0.5.
Can see gui without enable 3d acceleration, but black screen and have to task 
manager kill with 3d acceleration.
rtx 2070

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118

Title:
  Rendering issues in vmware with 3d on (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Invalid
Status in mesa source package in Noble:
  Triaged

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049988] Re: Latest kernel kills wifi.

[Patrick M]

I think Connman is the culprit?

** Package changed: network-manager (Ubuntu) => connman

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2049988

Title:
  Latest kernel kills wifi.

Status in Connection Manager:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Any news on this?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2049988

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2060665] [NEW] Unable to click on top left screen

[Yoann M]

Public bug reported:

Random after some time, the top left of the screen can't be clicked (not
even the mouse move event are dispatched to the window)

Using the Wayland (Alt + F2) "lg" show that a transparent box (385 width
x 56 height) is over, unable to close it

[0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
window title")]

It seems to be a notification window or something, and it's blocked
here.

The only way to fix it is to close the session, killing everything

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

** Attachment added: "Screenshot from 2024-04-09 13-18-29.png"
   
https://bugs.launchpad.net/bugs/2060665/+attachment/5762696/+files/Screenshot%20from%202024-04-09%2013-18-29.png

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

Title:
  Unable to click on top left screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Random after some time, the top left of the screen can't be clicked
  (not even the mouse move event are dispatched to the window)

  Using the Wayland (Alt + F2) "lg" show that a transparent box (385
  width x 56 height) is over, unable to close it

  [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some
  window title")]

  It seems to be a notification window or something, and it's blocked
  here.

  The only way to fix it is to close the session, killing everything

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

[Filip M]

Should we remove the ppa after the official packages are released?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Mantic:
  Triaged
Status in mutter source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Verify that input never froze for any perceptible period of time.
  4. Run: journalctl -b0 | grep MetaSyncRing
  5. Verify the above command does NOT show messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
  code being modified.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

[Filip M]

This one really affects my productivity. It's not only terminal it's also slack 
and some other apps.
Looking forward to @Daniel's PPA.
This also raises a question of testing upstream packages by Ubuntu team, as 
clearly this wasn't tested in all possible usage cases. I understand not 
everything can be tested in depth, but a bug of this magnitude needs to be 
triaged ASAP and not in weeks time frame. It's bad for enterprise users, and 
it's bad for all the newcomers. We decade old Ubuntu users are kinda used to 
this situations, not happy but used to it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Mantic:
  Triaged
Status in mutter source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Verify that input never froze for any perceptible period of time.
  4. Run: journalctl -b0 | grep MetaSyncRing
  5. Verify the above command does NOT show messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
  code being modified.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2058829] [NEW] Extreme low audio when using headphones

[Vanderson M. do Rosario]

Public bug reported:

The laptop audio works fine, but when I plug a headphone it seems that
there is no audio. If I turn on overamplification it is possible to hear
some low volume sound. So, the audio is actually there, it is just
extremely low.

I tried multiple things that I found only but none seems to work.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
Uname: Linux 6.8.1-060801-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 23 15:21:27 2024
InstallationDate: Installed on 2024-01-20 (64 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: LENOVO 83AW
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to noble on 2024-03-10 (13 days ago)
dmi.bios.date: 09/01/2023
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: MLCN23WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Slim Pro 7 14APH8
dmi.ec.firmware.release: 1.23
dmi.modalias: 
dmi:bvnLENOVO:bvrMLCN23WW:bd09/01/2023:br1.23:efr1.23:svnLENOVO:pn83AW:pvrLenovoSlimPro714APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoSlimPro714APH8:skuLENOVO_MT_83AW_BU_idea_FM_SlimPro714APH8:
dmi.product.family: Slim Pro 7 14APH8
dmi.product.name: 83AW
dmi.product.sku: LENOVO_MT_83AW_BU_idea_FM_Slim Pro 7 14APH8
dmi.product.version: Lenovo Slim Pro 7 14APH8
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2058829

Title:
  Extreme low audio when using headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The laptop audio works fine, but when I plug a headphone it seems that
  there is no audio. If I turn on overamplification it is possible to
  hear some low volume sound. So, the audio is actually there, it is
  just extremely low.

  I tried multiple things that I found only but none seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  Uname: Linux 6.8.1-060801-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 23 15:21:27 2024
  InstallationDate: Installed on 2024-01-20 (64 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: LENOVO 83AW
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to noble on 2024-03-10 (13 days ago)
  dmi.bios.date: 09/01/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MLCN23WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Slim Pro 7 14APH8
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrMLCN23WW:bd09/01/2023:br1.23:efr1.23:svnLENOVO:pn83AW:pvrLenovoSlimPro714APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoSlimPro714APH8:skuLENOVO_MT_83AW_BU_idea_FM_SlimPro714APH8:
  dmi.product.family: Slim Pro 7 14APH8
  dmi.product.name: 83AW
  dmi.product.sku: LENOVO_MT_83AW_BU_idea_FM_Slim Pro 7 14APH8
  dmi.product.version: Lenovo Slim Pro 7 14APH8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058829/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1992187] Re: hplip not working after install in 22.04, python error

[Fabio M. Panico]

Could not understand how to implement the workaround suggested by
Alterbo Donato #4.  I would appreciate if you could clarify.

But uninstalling the package available at Ubuntu 22.04 repository and
installing the package downloaded from HP Developers
(https://developers.hp.com/hp-linux-imaging-and-printing/gethplip)
worked fine for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1992187

Title:
  hplip not working after install in 22.04, python error

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from 20.04 to 22.04.1 (not a new installation): new 
installation of hplip
  >sudo apt install hplip hplip-gui

  Install completes without error.

  Using hplip, e.g.
  >hp-setup

  manual detection of wireless printer using IP works, printer is
  listed, but on 'next' -> process hangs (wait/termination suggested,
  wait does not help)

  alternative: (hplip installs a suite of programs)
  >hp-check(verifies installation and contact to printer, scanner
  produces normal output ending prematurely with error message:

    Saving output in log file: /home/glassel/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.22.2)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or
  .run) to determine if the proper dependencies are installed to successfully 
compile HPLIP.
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an
  already built HPLIP supplied tarball has the proper dependencies installed to 
successfully run.
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both
  compile- and run-time dependencies).

  Check types:
  a. EXTERNALDEP - External Dependencies
  b. GENERALDEP - General Dependencies (required both at compile and run time)
  c. COMPILEDEP - Compile time Dependencies
  d. [All are run-time checks]
  PYEXT SCANCONF QUEUES PERMISSION

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  -Traceback (most recent call last):
    File "/usr/bin/hp-check", line 861, in 
  dep.core.init()
    File "/usr/share/hplip/installer/core_install.py", line 523, in init
  self.get_distro()
    File "/usr/share/hplip/installer/core_install.py", line 661, in get_distro
  if 'MX' in distro_release_name:
  NameError: name 'distro_release_name' is not defined

  further info:
  >apt-cache policy hplip
  hplip:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  100 /var/lib/dpkg/status
   3.21.12+dfsg0-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  > apt-cache policy hplip-gui
  hplip-gui:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main i386 Packages
  100 /var/lib/dpkg/status
   3.21.12+dfsg0-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe i386 Packages

  ---

  I tried alternate ways to install hplip:
  hplip-3.22.6.run downloaded from hp

  this fails with an unmet dependency 'libcups2', but sudo apt install libcups2 
tells me it is
  installed (-dev version, too)

  A fresh install of cups did not help.

  Best regards ... Peter Glassel

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Any news on this bug? Latest patches did not affect it

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2049988

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Has anyone figured out a patch for this? there was an update today,
which I applied. Did not change anything with new kernel, but now old
version boots to airplane mode. I can get the wifi going on older kernel
still.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2049988

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 2049988] Re: Latest kernel kills wifi.

[Patrick M]

Thank you for the reply. I had to apply the command twice. It gave me an 
error the first time. Report was sent ( I think)

On 1/21/24 03:16, Chris Guiver wrote:
> apport-collect 2049988

** Package changed: linux (Ubuntu) => network-manager (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2049988

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2047743] Re: Sound glitches while moving window and talking on discord

[Rafal M]

I think the bug is probably related to KDE itself, but I dont know how
should I report that

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2047743

Title:
  Sound glitches while moving window and talking on discord

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  while being on discord call, moving any window causes the sound to be
  fragmented, choppy, unusable. That probably happens if system is after
  sleep cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  Uname: Linux 6.6.1-060601-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Dec 31 04:36:50 2023
  InstallationDate: Installed on 2023-07-07 (177 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (56 days ago)
  dmi.bios.date: 07/28/2023
  dmi.bios.release: 12.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1220
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z790M-PLUS D4
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1220:bd07/28/2023:br12.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2047743] [NEW] Sound glitches while moving window and talking on discord

[Rafal M]

Public bug reported:

while being on discord call, moving any window causes the sound to be
fragmented, choppy, unusable. That probably happens if system is after
sleep cycle.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
Uname: Linux 6.6.1-060601-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Dec 31 04:36:50 2023
InstallationDate: Installed on 2023-07-07 (177 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to mantic on 2023-11-04 (56 days ago)
dmi.bios.date: 07/28/2023
dmi.bios.release: 12.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1220
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z790M-PLUS D4
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1220:bd07/28/2023:br12.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2047743

Title:
  Sound glitches while moving window and talking on discord

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  while being on discord call, moving any window causes the sound to be
  fragmented, choppy, unusable. That probably happens if system is after
  sleep cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  Uname: Linux 6.6.1-060601-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Dec 31 04:36:50 2023
  InstallationDate: Installed on 2023-07-07 (177 days ago)
  InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-04 (56 days ago)
  dmi.bios.date: 07/28/2023
  dmi.bios.release: 12.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1220
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z790M-PLUS D4
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1220:bd07/28/2023:br12.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1958019]

[m]

(In reply to Gergo K from comment #794)
> (In reply to m from comment #792)
> > I'm on 6.6.4 on a Lenovo Yoga S940-14IIL 
> > 
> > cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819 
> > 
> > Same subsystem_id as for Lenovo 13s Gen2 ITL
> > (https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.
> > c#L10193)
> > 
> > Sound works, but it is high-pitched since the base is missing.
> 
> The C940 also has alc298 and tas2770.
> Please try this:
> sudo nano /etc/modprobe.d/alsa-base.conf
> 
> add this line:
> options snd-hda-intel model=17aa:3818
> 
> save:
> ctrl+o ctrl+x
> 
> sudo reboot

The file didn't exist and therefore was empty. I added the line and
saved the file. There was no change after rebooting. I still get sound,
but the same as before, only high-pitched with no base. Does there need
to be something additional in the file or some other configuration? Is
there some configuration to enable the speakers that give the base?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1958019]

[m]

I'm on 6.6.4 on a Lenovo Yoga S940-14IIL

cat /sys/class/sound/hwC1D0/subsystem_id 0x17aa3819

Same subsystem_id as for Lenovo 13s Gen2 ITL
(https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.c#L10193)

Sound works, but it is high-pitched since the base is missing.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2046224] [NEW] Resolutions lower than max results in corrupted screen

[M. Kurt]

Public bug reported:

Upgrading from 23.04 to 23.10 resulted in corrupt screen when switching
to lower resolutions. Only maximum resolution works.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash 
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias: 
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption mantic ubuntu

** Attachment added: "corrupt-screen.jpg"
   
https://bugs.launchpad.net/bugs/2046224/+attachment/5728569/+files/corrupt-screen.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046224

Title:
  Resolutions lower than max results in corrupted screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Upgrading from 23.04 to 23.10 resulted in corrupt screen when
  switching to lower resolutions. Only maximum resolution works.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Tue Dec 12 01:21:01 2023
  DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Phoenix [17aa:3c92]
  InstallationDate: Installed on 2023-11-04 (38 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash 
amd_pstate=guided vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
  dmi.bios.date: 06/16/2023
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M3CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Slim 5 16APH8
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 

[Desktop-packages] [Bug 2045907] [NEW] GtkFileChooserDialog hangs on large folder with 300000 files

[Martin M]

Public bug reported:

when I paste filename into the location bar (Ctrl+L) the file chooser
hangs.

The file happens to be in a folder with 30 other files and 
GtkFileChooserDialog
tries to offer a filename typing suggestion dropdown which is slow and 
eventually crashes.

When I then kill chrome or firefox then wayland session gets logouted.

Ubuntu version is 23.10

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2045907

Title:
   GtkFileChooserDialog hangs on large folder with 30 files

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  when I paste filename into the location bar (Ctrl+L) the file chooser
  hangs.

  The file happens to be in a folder with 30 other files and 
GtkFileChooserDialog
  tries to offer a filename typing suggestion dropdown which is slow and 
eventually crashes.

  When I then kill chrome or firefox then wayland session gets logouted.

  Ubuntu version is 23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2045907/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2036422] Re: XWayland cannot click fullscreen window beyond 1024x768

[Martin M]

need update to Ubuntu 23.10

** Changed in: xwayland (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2036422

Title:
  XWayland cannot click fullscreen window beyond 1024x768

Status in xwayland package in Ubuntu:
  Fix Released

Bug description:
  When I click in any xwayland window beyond the top-left 1024x768
  rectangle, the window below is clicked.

  Expected result: The xwayland window registers the click
  Actual result: The xwayland window registers the click correctly only in the 
top left 1024x768 pixels rectangle.

  
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  apt-cache policy xwayland
  xwayland:
Installed: 2:22.1.8-1ubuntu1
Candidate: 2:22.1.8-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xwayland 2:22.1.8-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 14:13:07 2023
  InstallationDate: Installed on 2023-08-01 (47 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: xwayland
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2036422] Re: XWayland cannot click fullscreen window beyond 1024x768

[Martin M]

This bug is fully resolved by update to Ubuntu 23.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2036422

Title:
  XWayland cannot click fullscreen window beyond 1024x768

Status in xwayland package in Ubuntu:
  Fix Released

Bug description:
  When I click in any xwayland window beyond the top-left 1024x768
  rectangle, the window below is clicked.

  Expected result: The xwayland window registers the click
  Actual result: The xwayland window registers the click correctly only in the 
top left 1024x768 pixels rectangle.

  
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  apt-cache policy xwayland
  xwayland:
Installed: 2:22.1.8-1ubuntu1
Candidate: 2:22.1.8-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xwayland 2:22.1.8-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 14:13:07 2023
  InstallationDate: Installed on 2023-08-01 (47 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: xwayland
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]

[m...@papersolve.com]

I tested this with the very small patch indicated in #1 and it worked.

I did 
"apt-src install mutter"
applied the patch.txt file with "patch -p1 < patch.txt"
"apt-src build mutter"
it fails all the tests but apparently this is expected, so i just went into the 
obj directory and did "sudo ninja install" and it replaced all the versions 
from the original .deb package.  I logged out and back in, and then I was able 
to restart gnome-shell (alt+f2 and r) while I still had windows open.  

Their discussions about this issue seem to have gotten bogged down in
minutiae of what other bugs are related, does some other bigger patch
fix those bugs, no one tested it, etc.  So I think it might be a good
idea to carry this small patch for now, and hopefully by the time it
starts conflicting it will no longer be necessary because it will be
fixed some other way. :)

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

Title:
  Gnome 45 crash on restart in X11 session [Window manager error:
  Another compositing manager is already running on screen 0 on display
  “:0”]

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Hello,

  Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer
  possible to restart gnome-shell without crashing the session. The only
  way not to crash it is to close all applications before restarting
  gnome-shell. I have verified this too.

  This has already been reported upstream: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050
  a tentative patch for mutter proposed: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598

  Please consider reviewing/testing this patch and pushing an update so
  people can restart gnome-shell session without crashing it.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2042729] [NEW] Xorg freeze

[Calum M Paterson]

Public bug reported:

Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid.  mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and use
computer

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov  4 15:33:14 2023
DistUpgraded: 2023-11-02 15:19:38,871 DEBUG 'libkf5itemviews5' scheduled for 
remove but not safe to remove, skipping
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 
[VGA controller])
   Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:229f]
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
InstallationDate: Installed on 2023-05-24 (164 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=UUID=45e4e3f8-045a-4651-bd83-6087eca44175 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-02 (2 days ago)
dmi.bios.date: 09/19/2023
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET61W (1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QV00BRUK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET61W(1.48):bd09/19/2023:br1.48:efr1.22:svnLENOVO:pn20QV00BRUK:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00BRUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QV00BRUK
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze mantic ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042729

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Computer unresponsive after closing laptop screen and reopening. GDM
  screen does not appear to login, just see contents of the X session
  before i closed the lid.  mouse moves and hardware buttons (mute, caps
  lock etc) are responsive with LEDs. Have to hard reboot to login and
  use computer

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  

[Desktop-packages] [Bug 2040453] Re: Gnome 45 crash on restart in X11 session [Window manager error: Another compositing manager is already running on screen 0 on display “:0”]

[m...@papersolve.com]

This bug is definitely important to me, being able to restart GNOME
Shell after it locks up, crashes, or updating an extension, _without_
losing any of my work or having to restart a large amount of open
programs, is one of the main reasons I still run it on X11.  Luckily I
was testing 23.10 in a VM while working on porting an extension and so
haven't updated my main machine yet.  But I won't be doing that until
this is fixed.  There is a patch on their gitlab but they have to test
it?  It's relatively simple so we could all test a PPA with the change.

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

Title:
  Gnome 45 crash on restart in X11 session [Window manager error:
  Another compositing manager is already running on screen 0 on display
  “:0”]

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Hello,

  Since the upgrade to Ubuntu 23.10 with Gnome45, it is no longer
  possible to restart gnome-shell without crashing the session. The only
  way not to crash it is to close all applications before restarting
  gnome-shell. I have verified this too.

  This has already been reported upstream: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050
  a tentative patch for mutter proposed: 
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7050#note_1876598

  Please consider reviewing/testing this patch and pushing an update so
  people can restart gnome-shell session without crashing it.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2003283] Re: Ubuntu22.04 Remote Desktop doesn't support to display the screen of the second monitor

[m...@papersolve.com]

I just set this up and can confirm, it only sees one monitor (the
"primary"). Very weird. No problem using x0tigervncserver to see them
both.

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

Title:
  Ubuntu22.04 Remote Desktop doesn't support to display the screen of
  the second monitor

Status in gnome-remote-desktop package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 Remote Desktop can only show the screen of the main
  monitor but not for the second monitor. It did work in Ubuntu 20.04
  without any problem on the same computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1
  Uname: Linux 6.1.4-060104-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 19 11:03:30 2023
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2023-01-10 (8 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales

[Fabio M. Panico]

*** This bug is a duplicate of bug 518056 ***
https://bugs.launchpad.net/bugs/518056

I was on 18.04 and that was not an issue for me.

Using US intl. alt. keyboard I could always get ç (cedilha).

Now that I've upgrade to 23.04, this problem came back.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/228077

Title:
  libgtk2 immodules has cedilla disabled in en locales

Status in gnome-control-center:
  Confirmed
Status in GTK+:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Invalid
Status in gnome-control-center package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: libgtk2.0-0

  philsf@philsf-laptop:~$ lsb_release -rd
  Description:  Ubuntu 8.04
  Release:  8.04

  philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0
  libgtk2.0-0:
Installed: 2.12.9-3ubuntu3

  One can't use dead keys to input a c+cedilla in en_US (probably other
  en_* locales). I had this on Gutsy. Now in Hardy, I thought I should
  report, since it's annoying, and the fix is documented.

  Steps to reproduce: 
  - enable deadkeys
  - Open gnome-terminal (or firefox) and enter ' + c 

  What you should get: ç
  What you do get: ć 

  Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ):

  
  Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and 
include ":en" in the cedilla line

  6c6
  < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa" 
  ---
  > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/228077/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2036422] Re: XWayland cannot click fullscreen window beyond 1024x768

[Martin M]

Additional information:

This bug only manifests when using Ubuntu in Virtualbox.

This bug manifests when Virtualbox Virtual screen is set to scale mode

Workaround: When I set Virtualbox Virtual screen to fixed resolution the
problem goes away in some apps.

In other apps the workaround doesn't help and the bug still manifests.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2036422

Title:
  XWayland cannot click fullscreen window beyond 1024x768

Status in xwayland package in Ubuntu:
  New

Bug description:
  When I click in any xwayland window beyond the top-left 1024x768
  rectangle, the window below is clicked.

  Expected result: The xwayland window registers the click
  Actual result: The xwayland window registers the click correctly only in the 
top left 1024x768 pixels rectangle.

  
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  apt-cache policy xwayland
  xwayland:
Installed: 2:22.1.8-1ubuntu1
Candidate: 2:22.1.8-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xwayland 2:22.1.8-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 14:13:07 2023
  InstallationDate: Installed on 2023-08-01 (47 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: xwayland
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

[M-Rick]

** Attachment added: "Capture d’écran du 2023-09-24 15-44-45.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704098/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-45.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2013236

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Incomplete

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

[M-Rick]

** Attachment added: "Capture d’écran du 2023-09-24 15-44-18.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704097/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-44-18.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2013236

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Incomplete

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices

[M-Rick]

I got it working on a 2015 MacBook Air 7.2
From a 23.04 fresh installation it didin't work neither with a 22.04 fresh 
installation. I tried all the tricks I found over internet and nothing worked.
I then had first to install an old Ubuntu 20.04 and block the version of the 
following packages bcmwl-kernel-source linux-headers-5-10.0.84 
linux-headers-5-10.0.84-generic linux-modules-5-10.0.84-generic. Now I have a 
fresh 23.04 version with Wifi on a Broadcom BCM 4360 14e4:43a0.
It seems defintely to be a bug since it worked perfectly out-of-the-box with 
other distros such as Fedora or Arch.

** Attachment added: "Capture d’écran du 2023-09-24 15-43-57.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2013236/+attachment/5704096/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-09-24%2015-43-57.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2013236

Title:
  b43 driver conflicts with bcmwl driver for some Broadcom devices

Status in broadcom-sta package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete
Status in broadcom-sta source package in Lunar:
  New
Status in linux-firmware source package in Lunar:
  Invalid
Status in ubuntu-drivers-common source package in Lunar:
  Incomplete
Status in broadcom-sta source package in Mantic:
  New
Status in linux-firmware source package in Mantic:
  Invalid
Status in ubuntu-drivers-common source package in Mantic:
  Incomplete

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

  Workaround
  --
  You'll first need to blacklist the b43 driver by adding a blacklist file to 
/etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run 
"update-initramfs -u". Then install the bcmwl-kernel-source package. After a 
reboot your wireless device should be available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2036422] [NEW] XWayland cannot click fullscreen window beyond 1024x768

[Martin M]

Public bug reported:

When I click in any xwayland window beyond the top-left 1024x768
rectangle, the window below is clicked.

Expected result: The xwayland window registers the click
Actual result: The xwayland window registers the click correctly only in the 
top left 1024x768 pixels rectangle.


lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04

apt-cache policy xwayland
xwayland:
  Installed: 2:22.1.8-1ubuntu1
  Candidate: 2:22.1.8-1ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xwayland 2:22.1.8-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 18 14:13:07 2023
InstallationDate: Installed on 2023-08-01 (47 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: xwayland
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xwayland (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2036422

Title:
  XWayland cannot click fullscreen window beyond 1024x768

Status in xwayland package in Ubuntu:
  New

Bug description:
  When I click in any xwayland window beyond the top-left 1024x768
  rectangle, the window below is clicked.

  Expected result: The xwayland window registers the click
  Actual result: The xwayland window registers the click correctly only in the 
top left 1024x768 pixels rectangle.

  
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  apt-cache policy xwayland
  xwayland:
Installed: 2:22.1.8-1ubuntu1
Candidate: 2:22.1.8-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xwayland 2:22.1.8-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 14:13:07 2023
  InstallationDate: Installed on 2023-08-01 (47 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: xwayland
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2020674] Re: Artifacts at window borders with mutter 44.1

[m...@papersolve.com]

I can confirm that (after figuring out which packages I had to force
version on and getting them all installed and restarting my session) the
gtk4 patch does fix the issue. No more weird corrupted borders, yay! I
do not see any issues with libreoffice either just in basic testing of
Writer and Calc, not sure what happened with that regression.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2020674

Title:
  Artifacts at window borders with mutter 44.1

Status in GTK+:
  Fix Released
Status in gtk4 package in Ubuntu:
  Fix Released
Status in gtk4 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  Mutter 44.1 switched from using the GL renderer to using Cairo to avoid 
rendering artifacts with the Nvidia drivers. However, this also needed a change 
in GTK4 to avoid other artifacts.

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2976

  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5857

  Test Case
  -
  Install gnome-shell 44.1 (currently in lunar-proposed).
  Install this gtk4 update.
  After installing the updates, log out and log back in.
  Open a terminal and the Chromium web browser.
  Tile the terminal to the left and tile Chromium to the right.

  Verify that there aren't rectangle rendering artifacts near the border
  between the two apps.

  What Could Go Wrong
  ---
  This is a one-line patch, cherry-picked from the gtk-4-10 branch that will be 
included in GTK 4.10.4 (which is expected to be released any day now). This 
puts us just a bit ahead of some other distros.

  See the master bug LP: #2020708 for more details about what it means
  to update GTK4.

  Excerpt from Original Report
  
  I wanted to report that I'm now seeing artifacts around window borders, when 
they are arranged to occupy all available area. I should note I'm also using 
gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2.

  I'm attaching a screen recording of what I'm seeing.

  The artifact at the border also happens across monitors. The tall
  chrome window on the right of the left monitor interferes with the
  windows aligned to the left of the right monitor.

  This happened immediately after updating mutter and gnome shell to
  44.1, it wasn't happening before.

  So far I'm seeing them with just google-chrome and chromium (snap),
  but not other apps I quickly tried (gnome-terminal, firefox).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: libmutter-12-0 44.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 10:17:44 2023
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2011251] Re: When focus-mode=mouse is set, gnome-shell gets into state where clicking on window title bars doesn't raise them

[m...@papersolve.com]

It looks like the gnome bug does acknowledge it only works for 'click'
mode (I use sloppy) so presumably when that gets fixed (and it looks
like they're still thinking about it!) and released then both mine and
yours will too.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2011251

Title:
  When focus-mode=mouse is set, gnome-shell gets into state where
  clicking on window title bars doesn't raise them

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  After the most recent Lunar updates (i.e., with the newest GNOME) my
  gnome-shell got into a state where clicking on the title bar of a
  window wouldn't raise the window (or do anything else), while clicking
  inside the window raised it as expected. The problem went away after I
  rebooted. I think this may have occurred after some other aberrant
  behavior, specifically the shell hanging for about 30 seconds (I will
  file a separate bug about that), so it's possible that things were in
  some sort of broken state because of that and this bug isn't actually
  specifically about the title bar, but I thought I should file a bug
  report about it just in case it's something other people start seeing
  so we can see how frequently it's happening.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44~beta-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 16:16:22 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1302 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 44~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2020277] Re: Update gnome-shell to 44.1

[m...@papersolve.com]

Hmm... unfortunately upgrading (both gnome-shell and mutter) to 44.1 did
not fix the main annoying bug for me where clicking titlebar doesn't
raise the window anymore (on X at least) - #2013216.

Also hitting the weird black bar issue that I didn't see under 44.0
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5857
so I am going to revert to 44.0 and this should probably wait until that is 
fixed (I think it might require a new GTK to be released too?)

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

Title:
  Update gnome-shell to 44.1

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Lunar:
  Fix Committed
Status in gnome-shell source package in Mantic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 44 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/44.1/NEWS

  It is also believed to fix at least one crash issue reported as LP:
  #2016007 but without a clear test case, that bug is not included in
  this SRU verification.

  Test Case
  -
  Complete all the test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  Other Info
  --
  gnome-shell provides the GNOME version number for the Settings app About 
page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by 
gnome-desktop/gnome-desktop3)

  This update requires mutter 44.1 (LP: #2020225). This was done with
  bumped dependencies in debian/control. gnome-shell 44.1 could be run
  with mutter 44.1 but it led to build test failures. Also, mixing
  different versions of mutter & gnome-shell is not supported upstream.

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

[m...@papersolve.com]

Argh, click to raise doesn't get fixed for me with this. Maybe because I
have focus follows mouse also? I still have to click inside the window
somewhere to raise it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2013216

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  Single clicking the title bar of windows without a complex title bar (namely 
a title bar with additional buttons besides the close/maximinze/minimize) does 
not transfer focus to them.

  Test Case
  -
  1. Open gnome-terminal.
  2. Run xedit.
  3. Focus gnome-terminal.
  4. Click Xedit's title bar.

  Expected: Xedit has focus.
  Observed: gnome-terminal retains focus.
  .
  5. Focus Xedit.
  6. Click gnome-terminal's title bar.

  Expected and observed: Xedit relinquishes focus and gnome-terminal
  gets focus.

  Other Info
  --
  I can reproduce this in my main, up to date Lunar system in Xorg and also in 
a virtual machine with the 2023-03-24 09:02 iso 
(https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso).

  What Could Go Wrong
  ---
  This fix is included in the upstream mutter 44.1 release. See LP: #2020225 
for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 29 11:53:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-16 (316 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)

[m...@papersolve.com]

I've seen this in my logs too, QUITE a lot in fact

sudo journalctl --no-hostname --since "30 days ago" | grep "update stage
views actor" | wc -l

gives me back:  221915

But as far as I can tell it doesn't have any effect (GNOME 44.0
certainly has its problems but I was getting it in 43.x too and even
before that and it's not causing hangs or crashes).  Intel i915 kernel
driver and modesetting with X11.

The message is coming from gnome-shell, so I assume if you won't get it
if you run a different DE - but are other DEs also unstable or are they
fine?

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

Title:
  Can't update stage views actor  (regarding MetaWindowGroup,
  MetaWindowActorX11, MetaSurfaceActorX11)

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  These messages repeat:

  [  105.711276] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bba91da500] is on because it needs an 
allocation.
  [  105.711772] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbac95c330] is on because it needs an 
allocation.
  [  105.711903] ingenika gnome-shell[2919]: Can't update stage views actor 
[:0x55bbae726860] is on because it needs an 
allocation.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  Uname: Linux 6.1.11-060111-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 17 21:54:39 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-08-22 (179 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

[m...@papersolve.com]

this should be fixed when ubuntu upgrades to gnome 44.1 which will
hopefully be soon! memory leak bugs that were fixed are also affecting
me (as well as this very annoying bug)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2013216

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Single clicking the title bar of windows without a complex title bar
  (namely a title bar with additional buttons besides the
  close/maximinze/minimize) does not transfer focus to them.

  Reproduction recipe:

  1. Open gnome-terminal.
  2. Run xedit.
  3. Focus gnome-terminal.
  4. Click Xedit's title bar.

  Expected: Xedit has focus.
  Observed: gnome-terminal retains focus.
  .
  5. Focus Xedit.
  6. Click gnome-terminal's title bar.

  Expected and observed: Xedit relinquishes focus and gnome-terminal
  gets focus.

  I can reproduce this in my main, up to date Lunar system in Xorg and
  also in a virtual machine with the 2023-03-24 09:02 iso
  (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-
  amd64.iso).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 29 11:53:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-16 (316 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2017365] [NEW] vanilla-gnome-desktop depends on pulseaudio which results in a conflict

[Thomas M Steenholdt]

Public bug reported:

Installing vanilla-gnome-desktop on a fresh 23.04 install, fails with:

The following packages have unmet dependencies:
 pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
 pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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

** Package changed: pipewire (Ubuntu) => ubuntu-gnome-meta (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/2017365

Title:
  vanilla-gnome-desktop depends on pulseaudio which results in a
  conflict

Status in ubuntu-gnome-meta package in Ubuntu:
  New

Bug description:
  Installing vanilla-gnome-desktop on a fresh 23.04 install, fails with:

  The following packages have unmet dependencies:
   pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
   pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio

[Thomas M Steenholdt]

I realize that the conflict is probably intended and my issue is that
vanilla-gnome-desktop relies on pulseaudio still. I'll create a separate
bug, sorry.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2017196

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio

[Thomas M Steenholdt]

I seem to hit the same dep issues on a freshly installed 23.04 system
when trying to install vanilla-gnome-desktop.

The following packages have unmet dependencies:
 pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
 pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be 
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2017196

Title:
  package pipewire-alsa (not installed) failed to install/upgrade:
  conflicting packages - not installing pipewire-alsa:amd64 [pipewire-
  alsa conflicts with pulseaudio]

Status in pipewire package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required
  software appeared to have downloaded. Committing Changes operated to
  about 84% at which point the system crashed. It was necessary to re-
  initiate the upgrade procedure. This time, the upgrade proceeded to
  about 95% when an error notification appeared on the screen. Further
  upgrades were not attempted.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: pipewire-alsa (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 21 04:46:04 2023
  ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64
  InstallationDate: Installed on 2020-02-04 (1171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: pipewire
  Title: package pipewire-alsa (not installed) failed to install/upgrade: 
conflicting packages - not installing pipewire-alsa:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1093765]

[Christopher M . Peñalver]

AFAIK, the original reporter's preference wasn't ever designed this way
so this is an enhancement request.

Also, nothing changed in:
Version: 7.5.0.3 (AARCH64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 8; OS: Mac OS X 13.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Latest Office still behaves the same way as noted in 
https://bugs.documentfoundation.org/show_bug.cgi?id=58070#c2 :
Microsoft Word for Microsoft 365 MSO (Version 2212 Build 16.0.15928.20278) 
64-bit

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1093765

Title:
  [upstream] switching paragraph style changes character orientation

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:4.0.2-0ubuntu1
Candidate: 1:4.0.2-0ubuntu1
Version table:
   *** 1:4.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in Writer via a terminal:
  cd ~/Desktop && wget 
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1093765/+attachment/3688368/+files/test-bug1093765.doc
 && lowriter --nologo test-bug1093765.doc

  is select all -> change combo box Apply Style from Text Body to
  Heading 1 and the text style changes, preserving the character order.

  4) What happens instead is:
  (Example text=) טקסט לדוגמה

  changes to:
  טקסט לדוגמה (=Example text)

  Microsoft Office Professional Plus 2010 Word Version 14.0.6023.1000 (32-bit) 
changes it to:
  =)טקסט לדוגמהExample text(

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  Uname: Linux 3.5.0-21-generic x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Wed Dec 26 11:20:42 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (67 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1093765/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 892476]

[Christopher M . Peñalver]

As the original reporter, I accept this being root caused to a documentation 
issue now fixed by:
https://bugs.documentfoundation.org/show_bug.cgi?id=43107#c27

I wouldn't have filed this report if it had been documented as such to
begin with.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/892476

Title:
  [Upstream] Regular expression "\n" in replace field inputs "\n"
  instead of paragraph break

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  1) lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.4.4-0ubuntu1~ppa1
Candidate: 1:3.4.4-0ubuntu1~ppa1
Version table:
   *** 1:3.4.4-0ubuntu1~ppa1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

  3) What is expected to happen in LibreOffice Calc is when one of the cells
  contains a line break -> Edit -> Find and Replace... -> in the "Search for"
  drop down \n -> in the "Replace with" drop down \n -> Regular expression 
button
  checked is the line break is replaced with a paragraph break as noted in
  http://help.libreoffice.org/Common/List_of_Regular_Expressions

  4) What happens instead is the line break is replaced with the
  characters \n

  ProblemType: BugDistroRelease: Ubuntu 11.10
  Package: libreoffice-calc 1:3.4.3-3ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov 19 13:02:28 2011
  EcryptfsInUse: YesInstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - 
Release amd64 (20101007)SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/892476/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 892476] Re: [Upstream] Regular expression "\n" in replace field inputs "\n" instead of paragraph break

[Christopher M . Peñalver]

Shahar Or, as per upstream, the root cause was a documentation issue that has 
since been clarified:
https://help.libreoffice.org/7.5/en-US/text/shared/01/0211.html?=SHARED=MAC

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/892476

Title:
  [Upstream] Regular expression "\n" in replace field inputs "\n"
  instead of paragraph break

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  1) lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.4.4-0ubuntu1~ppa1
Candidate: 1:3.4.4-0ubuntu1~ppa1
Version table:
   *** 1:3.4.4-0ubuntu1~ppa1 0
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

  3) What is expected to happen in LibreOffice Calc is when one of the cells
  contains a line break -> Edit -> Find and Replace... -> in the "Search for"
  drop down \n -> in the "Replace with" drop down \n -> Regular expression 
button
  checked is the line break is replaced with a paragraph break as noted in
  http://help.libreoffice.org/Common/List_of_Regular_Expressions

  4) What happens instead is the line break is replaced with the
  characters \n

  ProblemType: BugDistroRelease: Ubuntu 11.10
  Package: libreoffice-calc 1:3.4.3-3ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov 19 13:02:28 2011
  EcryptfsInUse: YesInstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - 
Release amd64 (20101007)SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/892476/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 462564] Re: [Upstream] Deleting a column in Writer deletes whole table

[Christopher M . Peñalver]

Confirmed resolved in 7.5.x.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/462564

Title:
  [Upstream] Deleting a column in Writer deletes whole table

Status in LibreOffice:
  Fix Released
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1)  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt
  && lowriter -nologo test.odt

  is when one highlights the second column of the table -> secondary
  clicks -> Column -> Delete is only that column is deleted. Please see
  movie for more details:
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv

  4) What happens instead is the whole table is deleted.

  Reproducible in:
  lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  WORKAROUND: Split the table then delete the column.

  WORKAROUND: Use Word via WINE.

  Microsoft Office Word 2003 (11.5604.6505)

  apt-cache policy wine1.3
  wine1.3:
    Installed: 1.3.28-0ubuntu1~ppa1~natty1
    Candidate: 1.3.28-0ubuntu1~ppa1~natty1
    Version table:
   *** 1.3.28-0ubuntu1~ppa1~natty1 0
  500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 
Packages
  100 /var/lib/dpkg/status
   1.3.15-0ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Oct 28 09:43:20 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: openoffice.org-core 1:3.1.1-5ubuntu1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2007683] [NEW] ubuntu crash randomly after awake from sleep

[Sharoon M]

Public bug reported:

after suspend ubuntu being lazy and crash , when restart computer i will
be okey

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 17 17:35:23 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-23 (300 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  ubuntu crash randomly after awake from sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after suspend ubuntu being lazy and crash , when restart computer i
  will be okey

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 17 17:35:23 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (300 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)

[zach m]

what does that mean for me?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/2004533

Title:
  Gtk-WARNING ... drawing failure for widget ... invalid value
  (typically too big)

Status in GTK+:
  Unknown
Status in cairo package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

some of my logs:

Gtk-WARNING **: 15:40:57.974: drawing failure for widget 'GtkBox':
invalid value (typically too big) for the size of the input (surface,
pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure
for widget 'GtkPaned': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure
for widget 'GtkBox': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure
for widget 'GtkFileChooserWidget': invalid value (typically too big) for
the size of the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure
for widget 'GtkBox': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:57.974: drawing failure
for widget 'GtkFileChooserDialog': invalid value (typically too big) for
the size of the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: infinite surface
size not supported

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkImage': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkButton': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkPathBar': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkBox': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkStack': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkBox': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkRevealer': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkBox': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkPaned': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkBox': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkFileChooserWidget': invalid value (typically too big) for
the size of the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkBox': invalid value (typically too big) for the size of
the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:40:59.735: drawing failure
for widget 'GtkFileChooserDialog': invalid value (typically too big) for
the size of the input (surface, pattern, etc.)

(firefox-aurora:221704): Gtk-WARNING **: 15:41:12.615: infinite surface
size not supported

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

My desktop is still buggy, I have attached a pic of what the window
controls look like on browser, file/folder windows.

** Attachment added: "Screenshot from 2023-02-02 15-39-43.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+attachment/5644519/+files/Screenshot%20from%202023-02-02%2015-39-43.png

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

Ok, I used the extension manager and have disabled the icons.

I now have no icons and no dock, it says my dock is on, but it is no
longer visible on the desktop

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

I had already disabled all my extensions.

Now I have deleted them and my dock bar is gone (still comes up when i
hit the windows key).

logged out and logged back in same issue.

#2:
# gnome-extensions disable d...@rastersoft.com
Failed to connect to GNOME Shell

yet without the extension specified:
# gnome-extensions disable 
gnome-extensions: No UUID given

Usage:
  gnome-extensions disable [OPTION…] UUID

Disable an extension

Application Options:
  -q, --quiet Do not print error messages


I should also note that ANY full screen video is extremely slow, sluggish 
framerate etc.

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

Let me know if there is anything else you need me to do thanks!

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

** Attachment added: "gssettings.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+attachment/5644402/+files/gssettings.txt

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+attachment/5644401/+files/lspcik.txt

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

** Attachment added: "packages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+attachment/5644400/+files/packages.txt

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] Re: very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily.

[zach m]

let's just change it to desktop gnome instability?


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004533/+attachment/5644399/+files/journal.txt

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Incomplete

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2004533] [NEW] very unstable desktop, icons vanish, cannot control windows, cannot resize or scale multi monitors easily. Oddly today I looked under settings and the Gnome vers

[zach m]

Public bug reported:

A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb  1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'disable-user-extensions' b'true'
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


** Tags: amd64 apport-bug kinetic

** Summary changed:

- very unstable desktop, icons vanish, cannot control windows, cannot resize or 
scale multi monitors easily. Oddly today I looked under settings and the Gnome 
version says 'unknown' while cli shows 43.1
+ very unstable desktop, icons vanish, cannot control windows, cannot resize or 
scale multi monitors easily. Oddly today I looked under settings and the Gnome 
version says 'unknown' while cli shows 43.1. Started immediately after 
upgrading from 22.04 to 22.10

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

Title:
  very unstable desktop, icons vanish, cannot control windows, cannot
  resize or scale multi monitors easily. Oddly today I looked under
  settings and the Gnome version says 'unknown' while cli shows 43.1.
  Started immediately after upgrading from 22.04 to 22.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
 

[Desktop-packages] [Bug 2003569] [NEW] all kinds of graphic issues, cannot scale desktop properly, icons vanish but reappear temporarily when hovering over missing icon then text vanishes again.

[zach m]

Public bug reported:

all kinds of graphic issues, cannot scale desktop properly, icons vanish
but reappear temporarily  when hovering over missing icon then text
vanishes again.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0b.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.78.01  Mon Dec 26 05:58:42 
UTC 2022
 GCC version:
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 20 12:17:19 2023
DistUpgraded: 2023-01-05 13:54:18,926 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: kinetic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed
 virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:859b]
InstallationDate: Installed on 2021-01-17 (733 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ASUS System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=c3541a51-e46f-4010-8668-6d2918b42e5e ro nvidia-drm.modeset=1 quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (14 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4201
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VIII DARK HERO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIDARKHERO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption kinetic possible-manual-nvidia-install 
ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2003569

Title:
  all kinds of graphic issues, cannot scale desktop properly, icons
  vanish but reappear temporarily  when hovering over missing icon then
  text vanishes again.

Status in xorg package in Ubuntu:
  New

Bug description:
  all kinds of graphic issues, cannot scale desktop properly, icons
  vanish but reappear temporarily  when hovering over missing icon then
  text vanishes again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0b.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.78.01  Mon Dec 26 
05:58:42 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: 

[Desktop-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop

[brian m. carlson]

I don't see this happening anymore as of the release of linux-
image-5.19.0-28-generic.  Neither the -28 nor the -29 kernel seem to
cause this to happen anymore, so I suspect this can probably be closed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1998950

Title:
  GPU hang on Alder Lake laptop

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1
  Carbon Gen 10.  When this occurs, part of the image tears away and X
  becomes unusable.  Sometimes the cursor continues to move for a short
  time after the fact.  In order to recover, I must SSH into the machine
  and run `sudo killall -9 Xorg`, which drops me back to the lightdm
  login screen and then things work again.

  I've also seen this on Debian sid on a nearly identical machine, and
  there when upgrading to kernel 6.0 and Mesa 22.3, the problem
  disappears.  However, those are not available in Kinetic.

  I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot
  parameters and this does not affect anything.  The problem has been
  occurring since I installed Ubuntu on this machine when I got it on
  November 17.

  I believe the upstream bug report is this:
  https://gitlab.freedesktop.org/drm/intel/-/issues/6757.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Tue Dec  6 16:42:04 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7]
  InstallationDate: Installed on 2022-11-17 (18 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 21CBCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash 
i915.enable_dc=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2022
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3AET65W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
  dmi.product.family: ThinkPad X1 Carbon Gen 10
  dmi.product.name: 21CBCTO1WW
  dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
  dmi.product.version: ThinkPad X1 Carbon Gen 10
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1998950] Re: GPU hang on Alder Lake laptop

[brian m. carlson]

Since there appears to be upstream patches in kernel 6.0 and Mesa 22.3.1
which fix this, perhaps it would be possible to backport those to the
versions in Ubuntu 22.10?  If not, would it at least be possible to
upload such packages to Lunar so that there's an option which doesn't
involve reinstalling the machine to go back to 22.04?

Right now my machine is freezing multiple times per day and it would be
really valuable to get those backports applied.  I'm pretty sure this
affects all Alder Lake-P GPUs on Kinetic, since the upstream bug report
mentions multiple different hardware variants.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1998950

Title:
  GPU hang on Alder Lake laptop

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1
  Carbon Gen 10.  When this occurs, part of the image tears away and X
  becomes unusable.  Sometimes the cursor continues to move for a short
  time after the fact.  In order to recover, I must SSH into the machine
  and run `sudo killall -9 Xorg`, which drops me back to the lightdm
  login screen and then things work again.

  I've also seen this on Debian sid on a nearly identical machine, and
  there when upgrading to kernel 6.0 and Mesa 22.3, the problem
  disappears.  However, those are not available in Kinetic.

  I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot
  parameters and this does not affect anything.  The problem has been
  occurring since I installed Ubuntu on this machine when I got it on
  November 17.

  I believe the upstream bug report is this:
  https://gitlab.freedesktop.org/drm/intel/-/issues/6757.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Tue Dec  6 16:42:04 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7]
  InstallationDate: Installed on 2022-11-17 (18 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 21CBCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash 
i915.enable_dc=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2022
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3AET65W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
  dmi.product.family: ThinkPad X1 Carbon Gen 10
  dmi.product.name: 21CBCTO1WW
  dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
  dmi.product.version: ThinkPad X1 Carbon Gen 10
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1680087] Re: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instances

[IOhannes m zmoelnig]

i strongly believe that this issue has been fixed with newer versions of
libogg, as found from Ubuntu/focal onwards.

i'm therefore closing this issue.
if you still experience this problem, please ping me.

** Changed in: libogg (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libogg in Ubuntu.
https://bugs.launchpad.net/bugs/1680087

Title:
  package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite
  shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is
  different from other instances of package libogg0:i386

Status in libogg package in Ubuntu:
  Fix Released

Bug description:
  Since I updated ubuntu 14.04 to 16.04, I can not use "apt-get install'

  Vous pouvez lancer « apt-get -f install » pour corriger ces problèmes :
  Les paquets suivants contiennent des dépendances non satisfaites :
   aptitude : Dépend: libcwidget3v5 mais ne sera pas installé
   gstreamer1.0-plugins-base:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne 
sera pas installé
   libflac8:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne sera pas installé
   libtheora0:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
   libvorbis0a:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
  E: Dépendances non satisfaites. Essayez « apt-get -f install » sans paquet

  When I follow the instruction 'apt-get -f install' :

  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack) :
   tentative de remplacement de « /usr/share/doc/libogg0/changelog.Debian.gz », 
qui est différent d'autres instances du paquet libogg0:i386
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/libogg0_1.3.2-1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libogg0 1.3.2-1
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 04:03:24 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  DuplicateSignature:
   package:libogg0:1.3.2-1
   Unpacking libogg0:i386 (1.3.2-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', 
which is different from other instances of package libogg0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other 
instances of package libogg0:i386
  InstallationDate: Installed on 2014-11-03 (884 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libogg
  Title: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from 
other instances of package libogg0:i386
  UpgradeStatus: Upgraded to xenial on 2017-04-03 (1 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1998950] [NEW] GPU hang on Alder Lake laptop

[brian m. carlson]

Public bug reported:

I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1
Carbon Gen 10.  When this occurs, part of the image tears away and X
becomes unusable.  Sometimes the cursor continues to move for a short
time after the fact.  In order to recover, I must SSH into the machine
and run `sudo killall -9 Xorg`, which drops me back to the lightdm login
screen and then things work again.

I've also seen this on Debian sid on a nearly identical machine, and
there when upgrading to kernel 6.0 and Mesa 22.3, the problem
disappears.  However, those are not available in Kinetic.

I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot
parameters and this does not affect anything.  The problem has been
occurring since I installed Ubuntu on this machine when I got it on
November 17.

I believe the upstream bug report is this:
https://gitlab.freedesktop.org/drm/intel/-/issues/6757.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec  6 16:42:04 2022
DistUpgraded: Fresh install
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7]
InstallationDate: Installed on 2022-11-17 (18 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: LENOVO 21CBCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic 
root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash 
i915.enable_dc=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2022
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N3AET65W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
dmi.product.family: ThinkPad X1 Carbon Gen 10
dmi.product.name: 21CBCTO1WW
dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
dmi.product.version: ThinkPad X1 Carbon Gen 10
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze kinetic ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1998950

Title:
  GPU hang on Alder Lake laptop

Status in xorg package in Ubuntu:
  New

Bug description:
  I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1
  Carbon Gen 10.  When this occurs, part of the image tears away and X
  becomes unusable.  Sometimes the cursor continues to move for a short
  time after the fact.  In order to recover, I must SSH into the machine
  and run `sudo killall -9 Xorg`, which drops me back to the lightdm
  login screen and then things work again.

  I've also seen this on Debian sid on a nearly identical machine, and
  there when upgrading to kernel 6.0 and Mesa 22.3, the problem
  disappears.  However, those are not available in Kinetic.

  I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot
  parameters and this does not affect anything.  The problem has been
  occurring since I installed Ubuntu on this machine when I got it on
  November 17.

  I believe the upstream bug report is this:
  https://gitlab.freedesktop.org/drm/intel/-/issues/6757.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)

[Daniel M Gessel]

I mounted a tmpfs in ~/tmp and FireFox can read from there.

I think firefox can read from /home (created a /home/dummy.html file
which FireFox could read).

I haven't tried this (I'm generating temporary html with a script, so a
slightly different version of the same problem), but editing /etc/fstab
to move the mountpoint of the tmpfs at /tmp to /home/tmp, then a link
from /tmp to /home/tmp might work.

But I also saw my first kernel panic after moving some stuff from /tmp
to ~/tmp (but haven't reproduced it again), so I'm not sure this is all
kosher...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1790608

Title:
  [snap] Libreoffice/Firefox do not open files from thunderbird (more
  general: from /tmp)

Status in snapd:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I received a document via e-mail in Thunderbird. I have the
  Libreoffice snap package installed. When I want to open the document
  from Thunderbird, I see the Libreoffice splash screen, and then a
  dialog stating "/tmp/mozilla_0/.docx does not exist."

  The same dialog appears when I navigate to the folder in Files and
  want to open it.

  When I copy the file to my desktop, however, I can open it without
  problems.

  I guess the source of the issue is confinement, that the Libreoffice
  snap can only access files from $HOME. But this breaks the case where
  thunderbird creates a temporary copy in /tmp.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files

[m...@papersolve.com]

Thanks, uninstalling libcanberra-gtk-3-0 helped with this. (I'd only
installed it way back in the distant past to stop those stupid warnings
on the command line!)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993907] Re: nautilus freezes randomly

[Filip M]

Same happened now to me. I have also caught this error:

ERROR:../src/nautilus-file.c:610:nautilus_file_new_from_filename: assertion 
failed: (filename[0] != '\0')
Bail out! ERROR:../src/nautilus-file.c:610:nautilus_file_new_from_filename: 
assertion failed: (filename[0] != '\0')
fish: Job 1, 'nautilus' terminated by signal SIGABRT (Abort)

It crashes right after launching the Nautilus. As if no files are
present.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993907

Title:
  nautilus freezes randomly

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus becomes unresponsive and "files" is not responding sign
  appears at random

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 15:39:58 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-05-13 (161 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993907] Re: nautilus freezes randomly

[Filip M]

This fixed it. Search/Filter now works fine in Nautilus. I hit another
issue just before I checked this bug report, in which Nautilus couldn't
find any files and crashed. Obviously an issue with tracker.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993907

Title:
  nautilus freezes randomly

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus becomes unresponsive and "files" is not responding sign
  appears at random

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 15:39:58 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-05-13 (161 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993907] Re: nautilus freezes randomly

[Filip M]

I can confirm this bug. In my case Nautilus automatically freezes if I
use the search in Nautilus or if I search for files in overview. I
haven’t been able to catch the output or why it freezes. I have upgraded
from 22.04 and previously from 21.10. As a heavy user of Nautilus for my
work this is a bit of a blocker at some times and reduces productivity,
especially because I can’t search or filter files.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993907

Title:
  nautilus freezes randomly

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus becomes unresponsive and "files" is not responding sign
  appears at random

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7
  Uname: Linux 5.19.0-1007-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 15:39:58 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'medium'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1272, 787)'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2022-05-13 (161 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-19 (3 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   python3-nautilus  4.0-1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1966573] Re: package firefox 98.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Nimesh v m]

This bug affected me from upgrading ubuntu 22.04 to 22.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1966573

Title:
  package firefox 98.0.2+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Attempting to upgrade my mostly vanilla Ubuntu 20.04 install to 22.04.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 98.0.2+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/controlC0', 
'/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', 
'/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20220322144853
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Sat Mar 26 23:41:46 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-05-29 (301 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.1.1 dev br0 proto dhcp metric 425 
   169.254.0.0/16 dev enp13s0 scope link metric 1000 
   192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.67 metric 425
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 
3.10.1-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu1
   apt  2.4.3
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 98.0.2+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago)
  dmi.bios.date: 08/28/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F30a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF30a:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993594] Re: Scrolling in a view with many files is broken

[Thomas M Steenholdt]

Possibly related to https://gitlab.gnome.org/GNOME/gtk/-/issues/2971

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993594

Title:
  Scrolling in a view with many files is broken

Status in nautilus package in Ubuntu:
  New

Bug description:
  Scrolling up and down in a Files window, in a directory with many
  files, the scrolling is erratic and seems to often jump to the bottom
  of the view.

  It happens only when scrolling while hovering the actual files (eg.
  using the mouse wheel). If hovering the scrollbar instead, there are
  no problems.

  The problem is bad enough, it's basically useless to get things done.

  Problem happens both in List View and Grid View

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Wed Oct 19 21:42:25 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)'
  InstallationDate: Installed on 2022-05-20 (152 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993594] Re: Scrolling in a view with many files is broken

[Thomas M Steenholdt]

** Attachment added: "Video showing problem. Using mouse wheel to ONLY scroll 
up."
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993594/+attachment/5625351/+files/Screencast%20from%202022-10-19%2021-52-35.webm

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2971
   https://gitlab.gnome.org/GNOME/gtk/-/issues/2971

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993594

Title:
  Scrolling in a view with many files is broken

Status in nautilus package in Ubuntu:
  New

Bug description:
  Scrolling up and down in a Files window, in a directory with many
  files, the scrolling is erratic and seems to often jump to the bottom
  of the view.

  It happens only when scrolling while hovering the actual files (eg.
  using the mouse wheel). If hovering the scrollbar instead, there are
  no problems.

  The problem is bad enough, it's basically useless to get things done.

  Problem happens both in List View and Grid View

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Wed Oct 19 21:42:25 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)'
  InstallationDate: Installed on 2022-05-20 (152 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1993594] [NEW] Scrolling in a view with many files is broken

[Thomas M Steenholdt]

Public bug reported:

Scrolling up and down in a Files window, in a directory with many files,
the scrolling is erratic and seems to often jump to the bottom of the
view.

It happens only when scrolling while hovering the actual files (eg.
using the mouse wheel). If hovering the scrollbar instead, there are no
problems.

The problem is bad enough, it's basically useless to get things done.

Problem happens both in List View and Grid View

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Wed Oct 19 21:42:25 2022
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)'
InstallationDate: Installed on 2022-05-20 (152 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nautilus
UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993594

Title:
  Scrolling in a view with many files is broken

Status in nautilus package in Ubuntu:
  New

Bug description:
  Scrolling up and down in a Files window, in a directory with many
  files, the scrolling is erratic and seems to often jump to the bottom
  of the view.

  It happens only when scrolling while hovering the actual files (eg.
  using the mouse wheel). If hovering the scrollbar instead, there are
  no problems.

  The problem is bad enough, it's basically useless to get things done.

  Problem happens both in List View and Grid View

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Wed Oct 19 21:42:25 2022
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)'
  InstallationDate: Installed on 2022-05-20 (152 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1991493] Re: Data ciphers are not properly configured with openvpn 2.6

[Thomas M Steenholdt]

This update makes it possible to connect to VPNs where the "cipher" (now
"data-ciphers") option is needed, as long as the connection is manually
modified. This part works great.

The Gnome settings interface however, still looks for the "cipher"
option, so this part does not work. The settings interface cannot see
the specified data-ciphers setting and trying to set it from the
interface, sets the cipher option instead, rendering the connection
unusable.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493

Title:
  Data ciphers are not properly configured with openvpn 2.6

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-openvpn package in Ubuntu:
  Fix Released

Bug description:
  OPTIONS ERROR: failed to negotiate cipher with server.  Add the
  server's cipher ('AES-256-CBC') to --data-ciphers (currently
  'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
  this server.

  So basically some servers won't be supported anymore because
  unsupported '--cipher' option is used instead of '--data-ciphers'

  A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
  openvpn/-/merge_requests/46

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1991492] Re: Upgrade to version 1.1.0

[IOhannes m zmoelnig]

libsndfile-1.1.0 is now (2022-09-06) packaged in Debian and will
automatically be imported into Ubuntu with the next DebianImport.

Unfortunately we missed the freeze deadline for 22.10/kinetic, which
means that the first Ubuntu version with the new library version will be
23.04

** Changed in: libsndfile (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsndfile in Ubuntu.
https://bugs.launchpad.net/bugs/1991492

Title:
  Upgrade to version 1.1.0

Status in libsndfile package in Ubuntu:
  Fix Committed

Bug description:
  Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding
  support. It would be great if the version here could be updated.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Magnus M]

I've also experienced this bug and it's a show-stopper for either
upgrading or requires changing distro, and makes Ubuntu unusable for
many enterprises. We don't accept user/password combination so a
fallback to that from Kerberos isn't possible and moving the ccache
isn't possible or supported either.

Also, since the snap:ification, the browser doesn't use system
certificates store anymore, which makes certificates break for all
websites when for example intermediate certs are rotated in the system
store, which is a security issue since users will be taught to accept
expired certificates.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1849346

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1989826] [NEW] cannot start lightdm gui

[Kyle Yannis M Estrada]

Public bug reported:

i installed lightdm but cannot start it manually
using ubuntu 22.04.1 LTS
release 22.04
codename: jammy

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lightdm 1.30.0-0ubuntu5
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
Date: Fri Sep 16 01:27:20 2022
InstallationDate: Installed on 2022-08-28 (18 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy uec-images

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1989826

Title:
  cannot start lightdm gui

Status in lightdm package in Ubuntu:
  New

Bug description:
  i installed lightdm but cannot start it manually
  using ubuntu 22.04.1 LTS
  release 22.04
  codename: jammy

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: lightdm 1.30.0-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  Date: Fri Sep 16 01:27:20 2022
  InstallationDate: Installed on 2022-08-28 (18 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1989067] Re: gnome-control-center Segmentation fault (core dumped)

[Vito M]

I tried reinstalling both and rebooting but no luck, also, sometimes the
settings just work, but when i close the window and try opening it
again, it doesn't open anymore. I have no idea what causes this.

I still tried disabling the rounded window corners even though you said
it was probably another problem, and yeah it didn't work.

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

Title:
  gnome-control-center Segmentation fault (core dumped)

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  When i try to open the settings, i see the loading cursor but noting
  opens, in the system monitor gnome control center appears briefly but
  quickly disappears. When i try to run it in the terminal using `gnome-
  control-center` it returns "Segmentation fault (core dumped)", same
  with `gnome-control-center display` or `gnome-control-center
  --version` which is why i could only specify the gnome-shell version.

  I have tried:
  `sudo apt update; sudo apt dist-upgrade`,
  `sudo apt install --reinstall gnome-control-center`,
  `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system 
restart (this worked temporarily like 3 times but is no longer effective),
  `gsettings reset org.gnome.ControlCenter last-panel`
  `dconf reset -f /org/gnome/control-center/`

  When i run `sudo gnome-control-center` i can briefly see the settings window 
and get this warning after it crashes almost immediately:
  (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit 
changes to dconf: Failed to execute child process “dbus-launch” (No such file 
or directory)
  Error creating rfkill proxy: (null)
  Segmentation fault

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  8 08:56:05 2022
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1989067] Re: gnome-control-center Segmentation fault (core dumped)

[Vito M]

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  gnome-control-center Segmentation fault (core dumped)

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  When i try to open the settings, i see the loading cursor but noting
  opens, in the system monitor gnome control center appears briefly but
  quickly disappears. When i try to run it in the terminal using `gnome-
  control-center` it returns "Segmentation fault (core dumped)", same
  with `gnome-control-center display` or `gnome-control-center
  --version` which is why i could only specify the gnome-shell version.

  I have tried:
  `sudo apt update; sudo apt dist-upgrade`,
  `sudo apt install --reinstall gnome-control-center`,
  `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system 
restart (this worked temporarily like 3 times but is no longer effective),
  `gsettings reset org.gnome.ControlCenter last-panel`
  `dconf reset -f /org/gnome/control-center/`

  When i run `sudo gnome-control-center` i can briefly see the settings window 
and get this warning after it crashes almost immediately:
  (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit 
changes to dconf: Failed to execute child process “dbus-launch” (No such file 
or directory)
  Error creating rfkill proxy: (null)
  Segmentation fault

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  8 08:56:05 2022
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1989067] Re: gnome-control-center Segmentation fault (core dumped)

[Vito M]

The output to `dpkg -l dbus-x11`:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
un  dbus-x11 (no description available)

The system log is included in the attachments.

** Attachment added: "journalctl -b 0 > systemlog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989067/+attachment/5614594/+files/systemlog.txt

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

Title:
  gnome-control-center Segmentation fault (core dumped)

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  When i try to open the settings, i see the loading cursor but noting
  opens, in the system monitor gnome control center appears briefly but
  quickly disappears. When i try to run it in the terminal using `gnome-
  control-center` it returns "Segmentation fault (core dumped)", same
  with `gnome-control-center display` or `gnome-control-center
  --version` which is why i could only specify the gnome-shell version.

  I have tried:
  `sudo apt update; sudo apt dist-upgrade`,
  `sudo apt install --reinstall gnome-control-center`,
  `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system 
restart (this worked temporarily like 3 times but is no longer effective),
  `gsettings reset org.gnome.ControlCenter last-panel`
  `dconf reset -f /org/gnome/control-center/`

  When i run `sudo gnome-control-center` i can briefly see the settings window 
and get this warning after it crashes almost immediately:
  (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit 
changes to dconf: Failed to execute child process “dbus-launch” (No such file 
or directory)
  Error creating rfkill proxy: (null)
  Segmentation fault

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  8 08:56:05 2022
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1989067] [NEW] gnome-control-center Segmentation fault (core dumped)

[Vito M]

Public bug reported:

When i try to open the settings, i see the loading cursor but noting
opens, in the system monitor gnome control center appears briefly but
quickly disappears. When i try to run it in the terminal using `gnome-
control-center` it returns "Segmentation fault (core dumped)", same with
`gnome-control-center display` or `gnome-control-center --version` which
is why i could only specify the gnome-shell version.

I have tried:
`sudo apt update; sudo apt dist-upgrade`,
`sudo apt install --reinstall gnome-control-center`,
`gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system 
restart (this worked temporarily like 3 times but is no longer effective),
`gsettings reset org.gnome.ControlCenter last-panel`
`dconf reset -f /org/gnome/control-center/`

When i run `sudo gnome-control-center` i can briefly see the settings window 
and get this warning after it crashes almost immediately:
(gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit 
changes to dconf: Failed to execute child process “dbus-launch” (No such file 
or directory)
Error creating rfkill proxy: (null)
Segmentation fault

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  8 08:56:05 2022
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

- I am using Ubuntu 22.04.1 LTS
- with GNOME Shell version 42.4
- 
  When i try to open the settings, i see the loading cursor but noting
  opens, in the system monitor gnome control center appears briefly but
  quickly disappears. When i try to run it in the terminal using `gnome-
  control-center` it returns "Segmentation fault (core dumped)", same with
  `gnome-control-center display` or `gnome-control-center --version` which
  is why i could only specify the gnome-shell version.
  
  I have tried:
  `sudo apt update; sudo apt dist-upgrade`,
  `sudo apt install --reinstall gnome-control-center`,
  `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system 
restart (this worked temporarily like 3 times but is no longer effective),
  `gsettings reset org.gnome.ControlCenter last-panel`
  `dconf reset -f /org/gnome/control-center/`
  
  When i run `sudo gnome-control-center` i can briefly see the settings window 
and get this warning after it crashes almost immediately:
  (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit 
changes to dconf: Failed to execute child process “dbus-launch” (No such file 
or directory)
  Error creating rfkill proxy: (null)
  Segmentation fault
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.4
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  8 08:56:05 2022
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-control-center Segmentation fault (core dumped)

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  When i try to open the settings, i see the loading cursor but noting
  opens, in the system monitor gnome control center appears briefly but
  quickly disappears. When i try to run it in the terminal using `gnome-
  control-center` it returns "Segmentation fault (core dumped)", same
  with `gnome-control-center display` or `gnome-control-center
  --version` which is why i could only specify the gnome-shell version.

  I have tried:
  `sudo apt update; sudo apt dist-upgrade`,
  `sudo apt install --reinstall gnome-control-center`,
  `gsettings reset-recursively org.gnome.desktop.wm.keybindings` and system 
restart (this worked temporarily like 3 times but is no longer effective),
  `gsettings reset org.gnome.ControlCenter last-panel`
  `dconf reset -f /org/gnome/control-center/`

  When i run `sudo gnome-control-center` i can briefly see the settings window 
and get this warning after it crashes almost immediately:
  (gnome-control-center:8869): dconf-WARNING **: 09:19:37.256: failed to commit 
changes to dconf: Failed to execute child process “dbus-launch” (No such file 
or directory)
  

[Desktop-packages] [Bug 1988754] [NEW] libreoffice writer crashes when edit the page break

[M. S. Rosyidi]

Public bug reported:

LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
I have tried also using LibreOffice from ppa and it still crashes.

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- LibreOffice Writes crashes when editing the page break. It happens in
- Xubuntu 22.04.1 and also in LinuxMint 21.
+ LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
+ I have tried also using LibreOffice from ppa and it still crashes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1988754

Title:
  libreoffice writer crashes when edit the page break

Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1959747]

[M-mozilla-org]

A capture documenting this bug with Thunderbird 102.2 on Linux (Fedora 36, 
Wayland): 
Between 1.5s and 4.5s the mouse pointer is moving over the message list.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959747

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just
  moving the mouse cursor over a message list results in 365% CPU for
  me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1959747]

[M-mozilla-org]

I can reproduce this on Fedora 36 with Thunderbird 102.2.0 on Wayland.
Setting `gfx.webrender.all false` and `gfx.webrender.force-disabled true` 
doesn't reduce CPU usage for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1959747

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just
  moving the mouse cursor over a message list results in 365% CPU for
  me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1987076] Re: Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

lspci -k

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610691/+files/lspci.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1987076

Title:
  Mouse cannot control windows after suspend and display change

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  My setup is this:

  Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
  Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
  Display: Lenovo T34w-20, connected via USB-C

  The problem started with upgrade to 22.04
  I have had the same exact problem with my previous laptop, a ThinkPad T14s. 
Both of these are AMD laptops, but I had no problem on 21.10.

  Way I can usually reproduce (always?)

  1. Suspend my laptop by yanking out the USB-C cable.
  2. Resume the laptop by connecting a different monitor (same make and model, 
but not the same physical one) and hit the keyboard a few times.

  Note: Resuming on the same physical display does not seem to result in
  the same problem.

  After this, I can no longer control the Windows on my desktop. The
  mouse cursor is active, but moves behind the open windows, and mouse
  click is not registered (at least not in a way that is useful).

  I can navigate the windows and use the applications, using the
  keyboard.

  Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the
  real session, mouse is still "broken".

  Ctrl+Alt+F2 to get to a TTY, and going back to the original session,
  mouse is still "broken".

  Only way I have found to reliably restore functionality is a reboot
  (which I have been doing a lot of the last few months).

  Please let me know what else I can provide you with, in order to get
  this fixed. :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Aug 19 10:32:48 2022
  InstallationDate: Installed on 2022-05-20 (91 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1987076] Re: Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

journalctl -b0

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610690/+files/journal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1987076

Title:
  Mouse cannot control windows after suspend and display change

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  My setup is this:

  Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
  Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
  Display: Lenovo T34w-20, connected via USB-C

  The problem started with upgrade to 22.04
  I have had the same exact problem with my previous laptop, a ThinkPad T14s. 
Both of these are AMD laptops, but I had no problem on 21.10.

  Way I can usually reproduce (always?)

  1. Suspend my laptop by yanking out the USB-C cable.
  2. Resume the laptop by connecting a different monitor (same make and model, 
but not the same physical one) and hit the keyboard a few times.

  Note: Resuming on the same physical display does not seem to result in
  the same problem.

  After this, I can no longer control the Windows on my desktop. The
  mouse cursor is active, but moves behind the open windows, and mouse
  click is not registered (at least not in a way that is useful).

  I can navigate the windows and use the applications, using the
  keyboard.

  Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the
  real session, mouse is still "broken".

  Ctrl+Alt+F2 to get to a TTY, and going back to the original session,
  mouse is still "broken".

  Only way I have found to reliably restore functionality is a reboot
  (which I have been doing a lot of the last few months).

  Please let me know what else I can provide you with, in order to get
  this fixed. :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Aug 19 10:32:48 2022
  InstallationDate: Installed on 2022-05-20 (91 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1987076] Re: Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

Thanks for the directions...

It's not that hard to reproduce here, I just have to move between places
(or I could bring my other monitor closer, for more intense
troubleshooting if need be). But it just happened...

There are no recent crashes and nothing reported by whoopsie. The
requested files are attached.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1987076

Title:
  Mouse cannot control windows after suspend and display change

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  My setup is this:

  Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
  Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
  Display: Lenovo T34w-20, connected via USB-C

  The problem started with upgrade to 22.04
  I have had the same exact problem with my previous laptop, a ThinkPad T14s. 
Both of these are AMD laptops, but I had no problem on 21.10.

  Way I can usually reproduce (always?)

  1. Suspend my laptop by yanking out the USB-C cable.
  2. Resume the laptop by connecting a different monitor (same make and model, 
but not the same physical one) and hit the keyboard a few times.

  Note: Resuming on the same physical display does not seem to result in
  the same problem.

  After this, I can no longer control the Windows on my desktop. The
  mouse cursor is active, but moves behind the open windows, and mouse
  click is not registered (at least not in a way that is useful).

  I can navigate the windows and use the applications, using the
  keyboard.

  Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the
  real session, mouse is still "broken".

  Ctrl+Alt+F2 to get to a TTY, and going back to the original session,
  mouse is still "broken".

  Only way I have found to reliably restore functionality is a reboot
  (which I have been doing a lot of the last few months).

  Please let me know what else I can provide you with, in order to get
  this fixed. :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Aug 19 10:32:48 2022
  InstallationDate: Installed on 2022-05-20 (91 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1987076] [NEW] Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

Public bug reported:

My setup is this:

Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
Display: Lenovo T34w-20, connected via USB-C

The problem started with upgrade to 22.04
I have had the same exact problem with my previous laptop, a ThinkPad T14s. 
Both of these are AMD laptops, but I had no problem on 21.10.

Way I can usually reproduce (always?)

1. Suspend my laptop by yanking out the USB-C cable.
2. Resume the laptop by connecting a different monitor (same make and model, 
but not the same physical one) and hit the keyboard a few times.

Note: Resuming on the same physical display does not seem to result in
the same problem.

After this, I can no longer control the Windows on my desktop. The mouse
cursor is active, but moves behind the open windows, and mouse click is
not registered (at least not in a way that is useful).

I can navigate the windows and use the applications, using the keyboard.

Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real
session, mouse is still "broken".

Ctrl+Alt+F2 to get to a TTY, and going back to the original session,
mouse is still "broken".

Only way I have found to reliably restore functionality is a reboot
(which I have been doing a lot of the last few months).

Please let me know what else I can provide you with, in order to get
this fixed. :)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Fri Aug 19 10:32:48 2022
InstallationDate: Installed on 2022-05-20 (91 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1987076

Title:
  Mouse cannot control windows after suspend and display change

Status in mutter package in Ubuntu:
  New

Bug description:
  My setup is this:

  Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
  Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
  Display: Lenovo T34w-20, connected via USB-C

  The problem started with upgrade to 22.04
  I have had the same exact problem with my previous laptop, a ThinkPad T14s. 
Both of these are AMD laptops, but I had no problem on 21.10.

  Way I can usually reproduce (always?)

  1. Suspend my laptop by yanking out the USB-C cable.
  2. Resume the laptop by connecting a different monitor (same make and model, 
but not the same physical one) and hit the keyboard a few times.

  Note: Resuming on the same physical display does not seem to result in
  the same problem.

  After this, I can no longer control the Windows on my desktop. The
  mouse cursor is active, but moves behind the open windows, and mouse
  click is not registered (at least not in a way that is useful).

  I can navigate the windows and use the applications, using the
  keyboard.

  Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the
  real session, mouse is still "broken".

  Ctrl+Alt+F2 to get to a TTY, and going back to the original session,
  mouse is still "broken".

  Only way I have found to reliably restore functionality is a reboot
  (which I have been doing a lot of the last few months).

  Please let me know what else I can provide you with, in order to get
  this fixed. :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Aug 19 10:32:48 2022
  InstallationDate: Installed on 2022-05-20 (91 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps

[M Conrad]

```bash
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy
muksihs@omen-desktop:~$  set | grep -E 
'XMODIFIERS|GTK_IM_MODULE|QT_IM_MODULE';setxkbmap -query
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus
rules:  evdev
model:  pc105
layout: us
variant:altgr-intl
options:compose:lwin,compose:rwin,grp_led:scroll,mod_led:compose
muksihs@omen-desktop:~$ cat .xsessionrc 
#!/bin/bash

export CLUTTER_IM_MODULE=ibus
export GTK_IM_MODULE=ibus
export QT_IM_MODULE=ibus
export XMODIFIERS=@im=ibus

muksihs@omen-desktop:~$ 
```

I'm using ibus with a local m17n layout.

Layout file: https://github.com/CherokeeLanguage/m17n.d/blob/main/chr-
phonetic.mim

My issue with ibus and intellij/pycharm is that the cursor is positioned
before the last character typed instead of after on short sequences
where a longer sequence exists.

The cursor appears to get moved back one character in the matching case.

I'm not sure the issue I'm having is exactly the same as this issue as
I'm not using dead keys. See
https://youtrack.jetbrains.com/issue/PY-55374/ibus-input-issue-where-
cursor-position-ends-being-before-the-character-inserted

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1863080

Title:
  Unable to use dead keys in Java apps

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  This is same bug as #540751, as it happens again in Ubuntu 19.10 with
  Java 11. Way of reproduce it:

  - Fresh Ubuntu 19.10 install.
  - Install default-jre.
  - Download (for example) lastest NetBeans version.
  - Edit a file in NetBeans, you can't insert characters like 'á'.

  The workaround is the same, define XMODIFIERS='' before launching the
  app.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi

[Joona-M Heikkilä]

gnome-shell[2660]: Object St.Bin (0x5563a04d98d0), has been already
deallocated — impossible to set any property on it. This might be caused
by the object having been destroyed from C code using something such as
destroy(), dispose(), or r>


Still an issue on 21.04 Ubuntu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1905519

Title:
  Syslog is flooded with Object St.Bin (0x565425162c80), has been
  already deallocated — impossible to set any property on it. This might
  be caused by the object having been destroyed from C code using
  something such as destroy(), dispose(), or remove() vfuncs.

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  The syslog is full of these messages, continuously written all day
  long

  Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 
0x56541fffb220 ==
  Nov 25 07:46:42 pc1 gnome-shell[2980]: #0   7ffddbfa1940 b   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 
(1839cb6a2420 @ 208)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 07:42:45 2020
  InstallationDate: Installed on 2014-06-03 (2366 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1973618] Re: can no longer open new windows after some time

[Thomas M Steenholdt]

I haven't been able to find other actual bugs/issues describing this
issue, but there are threads on reddit and such that seem to indicate
that this is a wayland/gnome42 issue, and that it affects all
distributions.

https://www.reddit.com/r/gnome/comments/ugpe12/firefox_on_gnome_42_cant_open_new_windows_after/
https://www.reddit.com/r/archlinux/comments/ugp9af/firefox_on_gnome_42_wayland_cant_create_new/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1973618

Title:
  can no longer open new windows after some time

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  After some time using firefox, I can no longer open a new window.

  => ps -ef | grep -c firefox
  21

  => /snap/bin/firefox

  => ps -ef | grep -c firefox
  21

  There is no new process created and the window never appears.
  I can open new tabs, but when I drag the tab to make it a new window, it is 
never created.

  The only remedy is to restart firefox. Sometimes I need to SIGTERM all
  of the zombi processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 19:45:08 2022
  InstallationDate: Installed on 2021-10-12 (215 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (22 days ago)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

[M Willis Monroe]

I already had xdg-desktop-portal-gnome installed however I'm still
seeing the bug in Google Chrome 101.0.4951.64 (Official Build) (64-bit)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1970148

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze. Download
  files, from any page does not work. Same issue with Firefox.

  Similarly, the browser will freeze when a page is printed to pdf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp