date:20220426

Also maybe related: bug 1969422

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

Interesting your system appears to use 'amdgpu' (from bug 1969351). I
wonder if bug 1970043 is the same crash.

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

Thanks, though you don't need the evdi driver if there is no
dock/adapter box. A monitor connected directly to a USB-C port is just a
native DisplayPort connection.

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

Thanks. It looks like a problem with errors.ubuntu.com itself, which is
not uncommon. The crash report exists but it failed to get a stack trace
and so errors.ubuntu.com can't categorise/group the crash reports.

This bug is still open at least, but it does mean we don't get a feel
for how common the crash is. It looks like it may only happen at logout
or during monitor config rearrangement.

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

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor.

Pradeep, if you are experiencing a similar bug with a different root
cause then commenting here may cause confusion. It's probably better if
you open a new bug of your own by running:

  ubuntu-bug gnome-shell

so that we can see the unique circumstances of your machine.

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1970520] Re: [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing on Cirrus Logic CS4213 Chip

It was working fine on Ubuntu 20.04.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing
  on Cirrus Logic CS4213 Chip

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
  Problems I face:

  Whenever I connect headphones, sound comes from both speaker/headphones.
  I have to change Auto-Mute status every time when I connect headphones.
  It automatically changes it's status from Enable to disable after headphone 
disconnect.

  What I tried Yet:

  I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
  But still facing same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
borkarsachin97   9437 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:17:00 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-mute between outputs
  Title: [HDA-Intel - HDA Intel PCH, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron 3520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970520/+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 1970523] [NEW] [Mesa Intel® HD Graphics 3000 (SNB GT2)] Cannot able to Change gamma on Inspiron 3520.

Public bug reported:

I am using Dell Inspiron 3520. It have Mesa Intel® HD Graphics 3000 (SNB GT2) 
Graphics.
Problems I am facing:

I am unable to change gamma via xgamma or randrx.

It was working fine on ubuntu 20.04. After Upgrade it is not working.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
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
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 10:36:19 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0555]
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. Inspiron 3520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=ea5b9322-6015-490d-b607-48fd6b6c04df ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2018
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0486TW
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
dmi.product.name: Inspiron 3520
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
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 jammy ubuntu wayland-session

** Attachment added: "Screenshot after command."
   
https://bugs.launchpad.net/bugs/1970523/+attachment/5584194/+files/Screenshot%20from%202022-04-27%2010-44-01.png

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

Title:
  [Mesa Intel® HD Graphics 3000 (SNB GT2)] Cannot able to Change gamma
  on Inspiron 3520.

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It have Mesa Intel® HD Graphics 3000 (SNB GT2) 
Graphics.
  Problems I am facing:

  I am unable to change gamma via xgamma or randrx.

  It was working fine on ubuntu 20.04. After Upgrade it is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  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
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:36:19 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0555]
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 3520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=ea5b9322-6015-490d-b607-48fd6b6c04df ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias:

[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

2022-04-26 Thread Matthew M. Dean

I found this in my syslog for the crash this morning

Apr 26 10:52:21 desktop whoopsie[]: [10:52:21] Parsing 
/var/crash/_usr_bin_gnome-shell.1000.crash.
Apr 26 10:52:21 desktop whoopsie[]: [10:52:21] Uploading 
/var/crash/_usr_bin_gnome-shell.1000.crash.
Apr 26 10:52:22 desktop whoopsie[]: [10:52:22] Sent; server replied with: 
No error
Apr 26 10:52:22 desktop whoopsie[]: [10:52:22] Response code: 200
Apr 26 10:52:22 desktop whoopsie[]: [10:52:22] Reported OOPS ID 
9fb85060-c589-11ec-9979-fa163e55efd0

Maybe you can pull up the OOPS ID?

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1970520] Re: [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing on Cirrus Logic CS4213 Chip

I Change Auto-Mute status using alsamixer.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing
  on Cirrus Logic CS4213 Chip

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
  Problems I face:

  Whenever I connect headphones, sound comes from both speaker/headphones.
  I have to change Auto-Mute status every time when I connect headphones.
  It automatically changes it's status from Enable to disable after headphone 
disconnect.

  What I tried Yet:

  I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
  But still facing same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
borkarsachin97   9437 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:17:00 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-mute between outputs
  Title: [HDA-Intel - HDA Intel PCH, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron 3520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970520/+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 1970520] [NEW] [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing on Cirrus Logic CS4213 Chip

Public bug reported:

I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
Problems I face:

Whenever I connect headphones, sound comes from both speaker/headphones.
I have to change Auto-Mute status every time when I connect headphones.
It automatically changes it's status from Enable to disable after headphone 
disconnect.

What I tried Yet:

I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
But still facing same issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
  borkarsachin97   9437 F alsamixer
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 10:17:00 2022
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Type: No auto-mute between outputs
Title: [HDA-Intel - HDA Intel PCH, playback] No automute
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2018
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0486TW
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
dmi.product.name: Inspiron 3520
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1970520

Title:
  [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing
  on Cirrus Logic CS4213 Chip

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
  Problems I face:

  Whenever I connect headphones, sound comes from both speaker/headphones.
  I have to change Auto-Mute status every time when I connect headphones.
  It automatically changes it's status from Enable to disable after headphone 
disconnect.

  What I tried Yet:

  I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
  But still facing same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
borkarsachin97   9437 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:17:00 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-mute between outputs
  Title: [HDA-Intel - HDA Intel PCH, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron 3520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970520/+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 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor.

2022-04-26 Thread Pradeep Bhat

I would like to mention same issue here either with c-dock or direct
HDMI plugin.

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1955500] Re: firefox crashes often

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  firefox crashes often

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Recently (since ~2021-12-15) firefox has been crashing a lot, often
  daily.  There's no obvious pattern that I can see.

  Most recent crash logs:
  Dec 21 12:37:51 cerberus firefox.desktop[755990]: Sandbox: Unexpected EOF, op 
0 flags 0200 path /proc/755990/cgroup
  Dec 21 12:37:51 cerberus firefox.desktop[756121]: Exiting due to channel 
error.
  Dec 21 12:37:51 cerberus firefox.desktop[755809]: Exiting due to channel 
error.
  Dec 21 12:37:51 cerberus firefox.desktop[755990]: Exiting due to channel 
error.
  ...
  Dec 21 12:37:51 cerberus firefox.desktop[745228]: [GFX1-]: Receive IPC close 
with reason=AbnormalShutdown
  Dec 21 12:37:51 cerberus firefox.desktop[744870]: Exiting due to channel 
error.
  ...

  Previous crash:
  Dec 20 12:56:53 cerberus kernel: traps: GeckoMain[613052] trap int3 
ip:7fa351cc1295 sp:7fff6ba7eea0 error:0 in libglib-2.>
  Dec 20 12:56:53 cerberus gnome-shell[722119]: Exiting due to channel error.
  Dec 20 12:56:53 cerberus gnome-shell[722386]: Exiting due to channel error.
  Dec 20 12:56:53 cerberus gnome-shell[615970]: Exiting due to channel error.
  Dec 20 12:56:53 cerberus gnome-shell[717612]: Exiting due to channel error.
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 95.0.1+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  jlquinn2641 F pulseaudio
   /dev/snd/controlC0:  jlquinn2641 F pulseaudio
   /dev/snd/controlC2:  jlquinn2641 F pulseaudio
   /dev/snd/controlC1:  jlquinn2641 F pulseaudio
  BuildID: 20211215221728
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 21 13:17:24 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-05-29 (570 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IpRoute:
   default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.10 metric 100
  MostRecentCrashID: bp-6d5c31fc-1b33-459b-bfab-9d3b20211216
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:363
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=54.0/20170612122310 (Out of date)
   Profile0 (Default) - LastVersion=95.0.1/20211215221728 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-11-04 (412 days ago)
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10DAI
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
  dmi.product.family: SMC X10
  dmi.product.name: X10DAi
  dmi.product.sku: 083615D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro
  mtime.conffile..etc.apport.crashdb.conf:

[Desktop-packages] [Bug 1945776] Re: Firefox freezes continuously on Ubuntu 20.04

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Firefox freezes continuously on Ubuntu 20.04

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Similar to other bug in my notebook with Ubuntu 16.04:
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792329

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 92.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefano1615 F pulseaudio
  BuildID: 20210903235534
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  1 13:41:19 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:358
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-05-12 (141 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IpRoute:
   default via 192.168.1.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.1.0/24 dev enp8s0 proto kernel scope link src 192.168.1.47 metric 100
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:358
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=92.0/20210903235534 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2012
  dmi.bios.release: 0.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0RW199
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/30/2012:br0.0:svnDellInc.:pnPrecisionWorkStationT7400:pvr:sku:rvnDellInc.:rn0RW199:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1945776/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

2022-04-26 Thread Matthew M. Dean

Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f50612a82e7 in gbm_surface_release_buffer () from 
/lib/x86_64-linux-gnu/libgbm.so.1
(gdb) bt full
#0  0x7f50612a82e7 in gbm_surface_release_buffer () at 
/lib/x86_64-linux-gnu/libgbm.so.1
#1  0x7f5063665dbf in meta_drm_buffer_gbm_finalize (object=0x55a6d0d9c690) 
at ../src/backends/native/meta-drm-buffer-gbm.c:485
buffer_gbm = 
#2  0x7f5064379dfd in g_object_unref () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x7f506366f5b0 in g_set_object (new_object=0x55a6d0d9c890, 
object_ptr=0x55a6cefbc490) at /usr/include/glib-2.0/gobject/gobject.h:762
old_object = 0x55a6d0d9c690
_object_ptr = {in = 0x55a6cefbc490 "\220\310\331ЦU", out = 
0x55a6cefbc490}
plane_state = 0x55a6cefbc490
#4  swap_plane_buffers (key=, user_data=, 
value=0x55a6cefbc490) at ../src/backends/native/meta-kms-crtc.c:487
_object_ptr = {in = 0x55a6cefbc490 "\220\310\331ЦU", out = 
0x55a6cefbc490}
plane_state = 0x55a6cefbc490
#5  swap_plane_buffers (key=, value=0x55a6cefbc490, 
user_data=) at ../src/backends/native/meta-kms-crtc.c:479
plane_state = 0x55a6cefbc490
#6  0x7f5064256698 in g_hash_table_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f506367b86c in meta_kms_crtc_on_scanout_started (crtc=, crtc=) at ../src/backends/native/meta-kms-crtc.c:496
page_flip_data = 0x55a6cf69d180
l = 
__func__ = "meta_kms_page_flip_data_flipped"
#8  meta_kms_page_flip_data_flipped (kms=, 
user_data=0x55a6cf69d180) at ../src/backends/native/meta-kms-page-flip.c:153
page_flip_data = 0x55a6cf69d180
l = 
__func__ = "meta_kms_page_flip_data_flipped"
#9  0x7f5063695bce in flush_callbacks.isra.0 (kms=kms@entry=0x55a6cec0e9c0) 
at ../src/backends/native/meta-kms.c:478
callback_data = 0x55a6cf078c30
l = 0x55a6d08b2ec0 = {0x55a6cf078c30}
callback_count = 
#10 0x7f506367b8dd in callback_idle (user_data=0x55a6cec0e9c0) at 
../src/backends/native/meta-kms.c:494
kms = 0x55a6cec0e9c0
#11 0x7f5064272c24 in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f50642c76f8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f5064272293 in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7f50635e35c9 in meta_context_run_main_loop (context=, 
error=0x7ffc4dbf21e8) at ../src/core/meta-context.c:437
priv = 0x55a6cec03050
__func__ = "meta_context_run_main_loop"
#15 0x55a6cce14f12 in  ()
#16 0x7f5063314d90 in __libc_start_call_main 
(main=main@entry=0x55a6cce14a70, argc=argc@entry=1, 
argv=argv@entry=0x7ffc4dbf2388) at ../sysdeps/nptl/libc_start_call_main.h:58
self = 
result = 

  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 
6610810358620701876, 140721612858248, 94174890248816, 94174890265080, 
139983260733504, -6609371649918810956, -6548631210224696140}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#17 0x7f5063314e40 in __libc_start_main_impl (main=0x55a6cce14a70, argc=1, 
argv=0x7ffc4dbf2388, init=, fini=, 
rtld_fini=, stack_end=0x7ffc4dbf2378) at ../csu/libc-start.c:392
#18 0x55a6cce151b5 in  ()

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

2022-04-26 Thread Victor Hugo Schulz

I was also affected by this issue when updating from 21.10 to 22.04, not on 
eduroam but on my university's network.
Workaround from post #22 worked for me, but I simply modified the original file 
(/etc/ssl/openssl.cnf).
After reading other comments, I got confused. Is this a bug on Ubuntu's 
wpasupplicant or a problem with the university's infrastructure using old 
vulnerable authentication methods?
If the latter, how should I report it to university's sysadmin?

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1969303] Re: "No package to remove" error when attempting to uninstall

2022-04-26 Thread Robert Ancell

** Changed in: snap-store-desktop
   Status: Fix Released => Confirmed

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

I installed that driver and rebooted, but the problem persists. Also, no
dock is used in my case, only usb-c.

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970408] Re: brltty package disconnecting ttyUSB0 used for Arduino

2022-04-26 Thread Batwam

that's a nice workaround. I still think that there is something odd
going on with the brltty package though as it shouldn't be disconnecting
connections like this.

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

Title:
  brltty package disconnecting ttyUSB0 used for Arduino

Status in brltty package in Ubuntu:
  New

Bug description:
  Hello

  I connected an ESP8266 microcontroller to my pc to use with Arduino.
  However, the interface didn't appears to list ttyUSB0. Upon inspection
  with dmesg, I noticed that the device is recognised but then brltty
  appears to disconnect it.

  [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device found, idVendor=10c4, 
idProduct=ea60, bcdDevice= 1.00
  [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [Tue Apr 26 19:09:35 2022] usb 1-8: Product: CP2102 USB to UART Bridge 
Controller
  [Tue Apr 26 19:09:35 2022] usb 1-8: Manufacturer: Silicon Labs
  [Tue Apr 26 19:09:35 2022] usb 1-8: SerialNumber: 0001
  [Tue Apr 26 19:09:35 2022] cp210x 1-8:1.0: cp210x converter detected
  [Tue Apr 26 19:09:35 2022] usb 1-8: cp210x converter now attached to ttyUSB0
  [Tue Apr 26 19:09:38 2022] usb 1-8: usbfs: interface 0 claimed by cp210x 
while 'brltty' sets config #1
  [Tue Apr 26 19:09:38 2022] cp210x ttyUSB0: cp210x converter now disconnected 
from ttyUSB0
  [Tue Apr 26 19:09:38 2022] cp210x 1-8:1.0: device disconnected

  This also appears to have happended to other people:
  https://stackoverflow.com/questions/52143723/usb-serial-loses-
  connection-immediately-in-new-linux-kernel-4-12-14

  Once the brltty package is removed, the USB device mounts fine and
  Arduino find it (same dmesg as above, without the last 3 lines).

  I'm actually not sure why this package is installed as I deleted it
  without having to remove ubuntu-desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: brltty (not installed)
  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: Tue Apr 26 19:15:04 2022
  InstallationDate: Installed on 2022-04-06 (20 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: brltty
  UpgradeStatus: Upgraded to jammy on 2022-04-18 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1970408/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

I'll try the driver you mentioned and get back to you later.

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

Yes I am using type-c to plug the monitor into my laptop and it looks a
lot like the problem you quoted

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970043] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1970043/+attachment/5584159/+files/ShellJournal.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/1970043

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970043] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1970043/+attachment/5584158/+files/ProcEnviron.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/1970043

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970043] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1970043/+attachment/5584157/+files/ProcCpuinfoMinimal.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/1970043

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970043] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1970043/+attachment/5584156/+files/GsettingsChanges.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/1970043

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

apport information

** Tags added: apport-collected

** Description changed:

  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to mutter42.
  And my computer is an amd 47 4800u machine and should only have one
  integrated graphics card
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-04-26 (0 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ Package: mutter
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
+ RelatedPackageVersions: mutter-common 42.0-3ubuntu2
+ Tags:  jammy wayland-session
+ Uname: Linux 5.15.0-27-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1970043/+attachment/5584155/+files/Dependencies.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/1970043

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970043/+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 1970408] Re: brltty package disconnecting ttyUSB0 used for Arduino

2022-04-26 Thread ionoz

Hi! I have same you problem. but now I can use ttyUSB0 in arduino
normaly.

slove:

1. run cmd. lsusb

(cmd)$  sudo lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse
Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Truevision HD
Bus 001 Device 009: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 001: ID 1d6b:1234 Linux Foundation 2.0 root hub

2. looking for ID (in my case I focus in "Linux Foundation 2.0 root hub" it ID 
1d6b:1234
3. edit file /etc/brltty.conf 
4. in line 109 of brltty.conf  unremak and put ID in usb:x:x ex.
   braille-device usb:1d6b:1234  # Specific USB device by serial number. 
5. save file and then restart

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

Title:
  brltty package disconnecting ttyUSB0 used for Arduino

Status in brltty package in Ubuntu:
  New

Bug description:
  Hello

  I connected an ESP8266 microcontroller to my pc to use with Arduino.
  However, the interface didn't appears to list ttyUSB0. Upon inspection
  with dmesg, I noticed that the device is recognised but then brltty
  appears to disconnect it.

  [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device found, idVendor=10c4, 
idProduct=ea60, bcdDevice= 1.00
  [Tue Apr 26 19:09:35 2022] usb 1-8: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [Tue Apr 26 19:09:35 2022] usb 1-8: Product: CP2102 USB to UART Bridge 
Controller
  [Tue Apr 26 19:09:35 2022] usb 1-8: Manufacturer: Silicon Labs
  [Tue Apr 26 19:09:35 2022] usb 1-8: SerialNumber: 0001
  [Tue Apr 26 19:09:35 2022] cp210x 1-8:1.0: cp210x converter detected
  [Tue Apr 26 19:09:35 2022] usb 1-8: cp210x converter now attached to ttyUSB0
  [Tue Apr 26 19:09:38 2022] usb 1-8: usbfs: interface 0 claimed by cp210x 
while 'brltty' sets config #1
  [Tue Apr 26 19:09:38 2022] cp210x ttyUSB0: cp210x converter now disconnected 
from ttyUSB0
  [Tue Apr 26 19:09:38 2022] cp210x 1-8:1.0: device disconnected

  This also appears to have happended to other people:
  https://stackoverflow.com/questions/52143723/usb-serial-loses-
  connection-immediately-in-new-linux-kernel-4-12-14

  Once the brltty package is removed, the USB device mounts fine and
  Arduino find it (same dmesg as above, without the last 3 lines).

  I'm actually not sure why this package is installed as I deleted it
  without having to remove ubuntu-desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: brltty (not installed)
  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: Tue Apr 26 19:15:04 2022
  InstallationDate: Installed on 2022-04-06 (20 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: brltty
  UpgradeStatus: Upgraded to jammy on 2022-04-18 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1970408/+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 1970107] Re: [nouveau] Xorg crash / Graphics Issue

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

OK we don't need to figure out the secondary nouveau bug if you didn't
mean to use nouveau.

** This bug has been marked a duplicate of bug 1965882
   [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white 
(plus a little flicker)

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

Title:
  [nouveau] Xorg crash / Graphics Issue

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I am using a wayland display manager, an internal graphics / Dedicated
  Graphics laptop where the HDMI is controlled by the dedicated
  graphics. Currently, with proprietary drivers on ubuntu 22.04

  When I connect a display to the hdmi it only shows a white screen,
  when I try to change the projection to mirror, or external only, it
  crashes and goes back onto the logon screen. I currently cannot cast
  at all to a monitor. The monitor I am trying to connect is a 4k and my
  laptop screen is 1080p if that makes a difference. I am sure I am not
  the only one who uses this feature, but because I have a mixture of
  internal and dedicated control, it may have more an issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 09:30:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:08ea]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:08ea]
  InstallationDate: Installed on 2022-04-22 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. G5 5590
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=03aed564-912f-48c9-972f-2517e41b2692 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0MXHK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd12/01/2021:br1.18:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0MXHK3:rvrA01:cvnDellInc.:ct10:cvr:sku08EA:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/ubuntu/+source/mutter/+bug/1970107/+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 1970072] Re: Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

Thanks for the attachments. It looks like the Nvidia kernel driver
encountered problems, which then caused problems in the Nvidia Xorg
driver, and then Xorg crashed.

I would suggest the first thing to do is to remove the kernel parameter
'nvidia-drm.modeset=1' because that wasn't a mature supported option
back in Ubuntu 20.04 (but it is in 22.04).


** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: nvidia

** No longer affects: gnome-shell (Ubuntu)

** Summary changed:

- Frequent GPU Resets (and GUI Freeze) by gsd-media-keys
+ [nvidia] Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

** Tags added: nvidia-drm.modeset

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

Title:
  [nvidia] Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  A fresh install of Ubuntu 20.04.4 has GUI freezes frequently (i.e., a
  dozen times daily) at inconsistent intervals and times, and not
  obviously in response to any particular user input.  The system then
  is unresponsive to user input, although the mouse cursor does continue
  to move about.

  The syslog messages reveal the message from gsd-media-keys "[GFX1]:
  Device reset due to WR context"

  The freeze also is preceded by often hundreds of pulseaudio messages
  related to latency issues, notwithstanding that no audio is playing.
  Often, gdm-x-session messages appear referencing the NVIDIA GPU and
  "WAIT".  The pulseaudio message "setting avail_min=87496" often is the
  last message and if not, one of the last, before the reboot.

  Also common before is a gnome-shell message "Ignored exception from
  dbus method: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  com.gonzaarcr.appmenu was not provided by any .service files", which
  precedes the pulseaudio messages.

  Happy to provide any other information but would welcome some guidance
  because I'm on day 11 or 12 of this installation and wearing out my
  welcome at Google.

  Ubuntu 20.04.4 LTS

  apt-cache returns:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expected behavior:  Stability, especially from the fourth release of a
  LTS.

  Behavior:  Persistent GUI freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 23 16:26:45 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-09 (14 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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/nvidia-graphics-drivers-470/+bug/1970072/+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 1970495] Re: Window manager freezes when plugging in external monitor.

Also it sounds like selecting 'Ubuntu on Xorg' from the login screen
might avoid the problem.

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor.

What is the model of the USB-C dock? Many/most of them use DisplayLink
technology and so require that special kernel driver be installed first:

https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

hidaris, are you plugging the monitor into the laptop or into a dock?

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970043/+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 1970495] Re: Window manager freezes when plugging in external monitor.

Next time the freeze happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Also check for crashes by following the steps in
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1970495] Re: Window manager freezes when plugging in external monitor.

Maybe related: bug 1970043

** Tags added: multimonitor

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

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

** Summary changed:

- Window manager freezes when plugging in external monitor.
+ Window manager freezes when plugging in USB-C dock with external monitor.

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor.

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1970043] Missing required logs.

2022-04-26 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1970043

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970043/+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 1970043] Re: [amdgpu] freeze occurs when wayland is connected to a second monitor

Maybe related: bug 1970495

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

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

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970043/+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 1970043] Re: freeze occurs when wayland is connected to a second monitor

I'll assign this to the kernel too, in case it's a system call that's
blocking.

** Tags added: amdgpu

** Summary changed:

- freeze occurs when wayland is connected to a second monitor
+ [amdgpu] freeze occurs when wayland is connected to a second monitor

** No longer affects: gnome-shell (Ubuntu)

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

** Tags added: multimonitor

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: 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/1970043

Title:
  [amdgpu] freeze occurs when wayland is connected to a second monitor

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I didn't encounter this bug with ubuntu 21.10 and when I tried to use
  x11 in 22.04 everything was fine, so it seems to be related to
  mutter42. And my computer is an amd 47 4800u machine and should only
  have one integrated graphics card

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 00:38:15 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/linux/+bug/1970043/+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 1970031] Re: [Xiaomi Timi TM1701] Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

Wayland is back thanks to updates last night (bug 1968929).

But this bug sounds like a problem with the default colour profile.


** Package changed: mutter (Ubuntu) => gnome-control-center (Ubuntu)

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [Xiaomi Timi TM1701] Instead of gray, my monitor displays pink-gray.
  Ubuntu 22.04

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my
  monitor started showing a gray-pink color. I can't take a screenshot
  because it will just be gray on your monitor (i checked the screenshot
  in windows 11). Did the developers break something in the video card
  driver or why did it happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sat Apr 23 19:54:00 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/ubuntu/+source/gnome-control-center/+bug/1970031/+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 1970495] Re: Window manager freezes when plugging in external monitor.

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Window manager freezes when plugging in external monitor.

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1969815] Re: Dual screens started blinking from blank to another type of blank for =<1 second each state

Sorry, I made a typo. Please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

** Tags added: radeon

** Summary changed:

- Dual screens started blinking from blank to another type of blank for =<1 
second each state
+ [radeon] Dual screens started blinking from blank to another type of blank 
for =<1 second each state

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

Title:
  [radeon] Dual screens started blinking from blank to another type of
  blank for =<1 second each state

Status in marco package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower.
  Laptops went well as they are standard running wifi (note to self:
  next time upgrade one using a USB docking station+as many externally
  attached devices as possible should prove in a quite pleasurable end-
  user experience)

  For the tower: this is the dual-screen portrait system I have been
  opening up defects for months now. Same config too. Anyways, after I
  rebooted the overall booting process happened pretty well until TTY7
  tried kicking it and totally failed doing so hence rendered my system
  totally broken.

  The behavior of my screens is that they started blinking from blank to
  another type of blank for =<1 second each state. But during one of
  those states there seemed to be Wayland as I could just see the mouse
  cursor fly around when activated.

  Accessing other TTYs was also impossible as even though pressing
  CTRL+ALT+F2|F3|etc would indeed display a login prompt that within
  that same blinking instant that it had altered back to only that
  blinking cursor symbol(_) at the top-hand-left.

  That behavior held true for all TTYs.

  Pressing the power button did showed up the UM symbol alongside
  standard shutdown routine happened OK.

  Solution was: unplug one of the two monitor and automagically jammy's
  login screen popped up.

  If I replug that 2nd monitor while I am inside a working TTY7 session
  then the same (original) problem happens in which I cannot use any of
  the screens and when I re-unplug one of the two screens again I am re-
  back again at the jammy login having lost the current session that I
  had.

  Both of my screens are the same model and both use HDMI.

  I have attached my ~/.config/monitors.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1969815/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

You might be commenting on the wrong bug now. We're still getting zero
crash reports in gbm_surface_release_buffer, at least none since gnome-
shell version 42.0-1ubuntu1.

Can you provide a stack trace of the most recent crash and confirm that
it happened after the update to 42.0-2ubuntu1 ?

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1967651] Re: Unicomp trackball/keyboard not recognised in Xorg sessions

Weird. That's been the default input handler for years so I don't know
why your system didn't have it installed.

Still, not a bug in the package itself if the package was missing.


** Bug watch added: 
gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues #51
   https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/51

** Also affects: xserver-xorg-input-libinput via
   https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/51
   Importance: Unknown
   Status: Unknown

** Changed in: xserver-xorg-input-libinput (Ubuntu)
   Status: Fix Released => Invalid

** Summary changed:

- Unicomp trackball/keyboard not recognised in Xorg sessions
+ xserver-xorg-input-libinput is not installed and input doesn't work

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

Title:
  xserver-xorg-input-libinput is not installed and input doesn't work

Status in xserver-xorg-input-libinput:
  Unknown
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid

Bug description:
  after updating to jammy beta, xorg does not work for any desktop, in
  every case the desktop comes up, but there is no response to keyboard
  or mouse (not even numlock). I tried unplugging and replugging the
  devices with no luck.

  All desktops do 'work' in the wayland version, but the display flashes
  frequently, showing parts of other windows

  ubuntu=bug gathers information, but does not open the browser window after 
reporting that it's uploaded the data.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: 2022-03-29 14:49:15,830 INFO cache.commit()
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:0123]
  InstallationDate: Installed on 2021-09-20 (194 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: SYSTEM_MANUFACTURER HX90
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=f8f3b117-f767-4bda-9258-5e776fd90ba3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-29 (4 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  XorgLog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/05/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 5.19
  dmi.board.asset.tag: Default string
  dmi.board.name: HX90
  dmi.board.vendor: Default string
  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:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd08/05/2021:br5.19:svnSYSTEM_MANUFACTURER:pnHX90:pvrDefaultstring:rvnDefaultstring:rnHX90:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: HX90
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: SYSTEM_MANUFACTURER
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/xserver-xorg-input-libinput/+bug/1967651/+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 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time

** Package changed: mutter (Ubuntu) => gdm3 (Ubuntu)

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Fix 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/1969121

Title:
  System fallback to gdm login screen when hot-plugging a external
  monitor in 1st time

Status in OEM Priority Project:
  Fix Committed
Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  [Steps to reproduce]
  1. Install Jammy daily build
  2. dist-upgrade to verify https://bugs.launchpad.net/mutter/+bug/1964037
  3. reboot with no attach monitor
  4. attach monitor after booting

  [Expect result]
  external monitor works directly

  [Actual result]
  system go back to gdm login screen

  [Additional information]
  1. the external port is connecting to dGPU.
  2. happens on wayland only
  3. Only back to login screen in 1st attach, 2nd, 3rd, etc.. works good

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 14 21:22:47 2022
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969121/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Unknown
Status in metacity package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1799679/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Unknown
Status in metacity package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1799679/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: metacity (Ubuntu)
   Status: New => Confirmed

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Unknown
Status in metacity package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1799679/+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 1970413] Re: Moving windows around is laggy

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

This is technically an old bug 1799679. It just became worse in 22.04
since GNOME started using GTK4, hence OpenGL, and so most apps are now
affected.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510
(Ubuntu)

** This bug has been marked a duplicate of bug 1799679
   Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL 
app windows

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

Title:
  Moving windows around is laggy

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  When I move a window around, it's lagging and sometimes it's freezing
  for a second. This is happening after the upgrade to Ubuntu 22.04.
  Also, it happens all the time, even after I restart my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 15:09:42 2022
  DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed
   nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] 
[1458:3733]
  InstallationDate: Installed on 2021-11-08 (168 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970413/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows

2022-04-26 Thread Luís Cunha dos Reis Infante da Câmara

** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging
  OpenGL app windows

Status in Mutter:
  Unknown
Status in metacity package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  Nvidia driver causes Xorg to use 100% CPU and shows high lag and
  stutter... but only when dragging glxgears/glxheads, or any window
  over them. Other apps do not exhibit the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nvidia-driver-390 390.87-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Wed Oct 24 19:11:15 2018
  InstallationDate: Installed on 2018-05-26 (151 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1799679/+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 1970502] Re: New release 91.8

** Description changed:

  Thunderbird 91.8 has been released.
  
  Please package this version to all Ubuntu releases under standard
  support.
  
- Debian has released this version on April 10.
+ Debian has released a security advisory on April 10.

** Information type changed from Private Security to Public Security

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

Title:
  New release 91.8

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Thunderbird 91.8 has been released.

  Please package this version to all Ubuntu releases under standard
  support.

  Debian has released a security advisory on April 10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1970502/+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 1970459] Re: import of ca-certificate in browser does not work

2022-04-26 Thread Seth Arnold

I switched this from ca-certificates to firefox and chromium-browser,
since both browsers manage their own certificate lists and don't use the
system-provided ca-certificates. (You manage that with different tools,
see the first few lines of /etc/ca-certificates.conf for details.)

Thanks

** Package changed: ca-certificates (Ubuntu) => firefox (Ubuntu)

** Also affects: chromium-browser (Ubuntu)
   Importance: Undecided
   Status: 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/1970459

Title:
  import of ca-certificate in browser does not work

Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I tried to import a CA root certificate into both Firefox and Chrome.
  In Firefox, the import button just didn't do anything, in Chrome
  pressing "import" hangs up the browser. This means I can't reach the
  intranet of the company I work for.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ca-certificates 20211016
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:16:12 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970459/+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 1970459] [NEW] import of ca-certificate in browser does not work

You have been subscribed to a public bug:

I tried to import a CA root certificate into both Firefox and Chrome. In
Firefox, the import button just didn't do anything, in Chrome pressing
"import" hangs up the browser. This means I can't reach the intranet of
the company I work for.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ca-certificates 20211016
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 19:16:12 2022
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy
-- 
import of ca-certificate in browser does not work
https://bugs.launchpad.net/bugs/1970459
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox in Ubuntu.

-- 
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 1967843] Re: cheese display corrupted under Ubuntu 22.04

2022-04-26 Thread Jan Steffens

I added a fix for this to Arch's `clutter-gst` (bug link
https://bugs.archlinux.org/task/74222):

https://github.com/archlinux/svntogit-packages/blob/packages/clutter-
gst/trunk/0001-video-sink-Remove-RGBx-BGRx-support.patch

This allows MJPEG cameras to work properly.

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

Title:
  cheese display corrupted under  Ubuntu 22.04

Status in Cheese:
  Unknown
Status in cheese package in Ubuntu:
  Triaged
Status in cheese source package in Jammy:
  Triaged

Bug description:
  The cheese application produces a corrupted display under Ubuntu 22.04
  with a Logitech C525 webcam. When started from the command line,
  cheese produces repeated warnings of the form...

  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.

  Adding /etc/modprobe.d/uvcvideo.conf

  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: cheese 41.1-1build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: wayland-session third-party-packages jammy gstreamer-error
  Uname: Linux 5.15.0-25-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: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


--

[Desktop-packages] [Bug 1970495] Re: Window manager freezes when plugging in external monitor.

2022-04-26 Thread Brian Rossa

EDIT: Updated title.

Taking the dock out of the loop and simply plugging in an HDMI monitor
also causes the problem. Below is the syslog from single plug/unplug
cycle.

```
$ tail -f /var/log/syslog 
Apr 26 18:54:49 dathon systemd[1]: Starting Hostname Service...
Apr 26 18:54:49 dathon nautilus[7520]: Called "net usershare info" but it 
failed: Failed to execute child process “net” (No such file or directory)
Apr 26 18:54:49 dathon dbus-daemon[463]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Apr 26 18:54:49 dathon systemd[1]: Started Hostname Service.
Apr 26 18:54:49 dathon rtkit-daemon[905]: Supervising 6 threads of 3 processes 
of 1 users.
Apr 26 18:54:49 dathon rtkit-daemon[905]: message repeated 5 times: [ 
Supervising 6 threads of 3 processes of 1 users.]
Apr 26 18:54:49 dathon rtkit-daemon[905]: Successfully made thread 7601 of 
process 7406 owned by '1000' RT at priority 10.
Apr 26 18:54:49 dathon rtkit-daemon[905]: Supervising 7 threads of 4 processes 
of 1 users.
Apr 26 18:55:02 dathon rtkit-daemon[905]: message repeated 12 times: [ 
Supervising 7 threads of 4 processes of 1 users.]
Apr 26 18:55:19 dathon systemd[1]: systemd-hostnamed.service: Deactivated 
successfully.
Apr 26 18:55:35 dathon gnome-shell[1649]: Spurious clutter_actor_allocate 
called for actor 
0x55ebc7aac030/[:0x55ebc7aac030]
 which isn't a descendent of the stage!
Apr 26 18:55:35 dathon gnome-shell[1649]: Timelines with detached actors are 
not supported. [:0x55ebc7679c30] in animation of 
duration 500ms but not on stage.
Apr 26 18:55:35 dathon gnome-shell[1649]: Timelines with detached actors are 
not supported. [:0x55ebc73bf090] in animation of 
duration 500ms but not on stage.
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 39 with keysym 39 (keycode 12).
Apr 26 18:55:36 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
Apr 26 18:55:36 dathon gnome-shell[1649]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
Apr 26 18:55:46 dathon gnome-shell[1649]: Timelines with detached actors are 
not supported. [:0x55ebc0ff0520] in animation of 
duration 500ms but not on stage.
Apr 26 18:55:46 dathon gnome-shell[1649]: st_widget_get_theme_node called on 
the widget [0x55ebc5e96130 Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom 
shrink running-dots fixed extended:insensitive "dashtodockContainer"] which is 
not in the stage.
Apr 26 18:55:46 dathon gnome-shell[1649]: Spurious clutter_actor_allocate 
called for actor 
0x55ebc5e96130/[:0x55ebc5e96130]
 which isn't a descendent of the stage!
Apr 26 18:55:46 dathon gnome-shell[1649]: Timelines with detached actors are 
not supported. [:0x55ebc267e930] in animation of 
duration 500ms but not on stage.
Apr 26 18:55:46 dathon gnome-shell[1649]: Timelines with detached actors are 
not supported. [:0x55ebc4435000] in animation of 
duration 500ms but not on stage.
Apr 26 18:55:47 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
Apr 26 18:55:47 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
Apr 26 18:55:47 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
Apr 26 18:55:47 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
Apr 26 18:55:47 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
Apr 26 18:55:47 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
Apr 26 18:55:47 dathon gnome-shell[1649]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
Apr 26 18:55:47 dathon gnome-shell[1649]: Window

[Desktop-packages] [Bug 1970495] [NEW] Window manager freezes when plugging in external monitor.

2022-04-26 Thread Brian Rossa

Public bug reported:

1. Problem DOES appear on Lenovo T470s (Intel).
2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
3. Problem does NOT appear on either of the above *when in the Live Installer*.

I specifically checked that my dock behaved well under the Live
Installer before deciding to move my workstations to Jammy. Upon logging
into a fresh Jammy install, I found the following problem behavior: When
the dock is plugged in, the built-in display freezes and the dock-
attached displays power up but never render anything (ie, they stay
black). Unplugging the USB-C cable gets mouse/keyboard response back on
the built-in display.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
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: Tue Apr 26 18:32:35 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-26 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1970495

Title:
  Window manager freezes when plugging in external monitor.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1. Problem DOES appear on Lenovo T470s (Intel).
  2. Problem DOES appear on Lenovo T14 Gen2 (AMD).
  3. Problem does NOT appear on either of the above *when in the Live 
Installer*.

  I specifically checked that my dock behaved well under the Live
  Installer before deciding to move my workstations to Jammy. Upon
  logging into a fresh Jammy install, I found the following problem
  behavior: When the dock is plugged in, the built-in display freezes
  and the dock-attached displays power up but never render anything (ie,
  they stay black). Unplugging the USB-C cable gets mouse/keyboard
  response back on the built-in display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  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: Tue Apr 26 18:32:35 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  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/1970495/+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 1970492] [NEW] Firefox update pushing me to update to 91.0.1 when I am on 91.0.2

2022-04-26 Thread archerbob

Public bug reported:

I am using Firefox on Ubuntu 16.04 and has been spamming me to update my
browser for awhile now and thus I did so today to 91.0.2, only to
discover the update spam continues telling me to update to 91.0.1 :/

What can I say, why is pushing people to update to a previous version a
thing?

Please give me a patch that allows users like me to choose whether I
want to update, OR NOT, and disable the update spam message that occurs
multiple times a day!

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


** Tags: 16.04 91.0.1 91.0.2 annoying firefox spam ubuntu update updater

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

Title:
  Firefox update pushing me to update to 91.0.1 when I am on 91.0.2

Status in firefox package in Ubuntu:
  New

Bug description:
  I am using Firefox on Ubuntu 16.04 and has been spamming me to update
  my browser for awhile now and thus I did so today to 91.0.2, only to
  discover the update spam continues telling me to update to 91.0.1 :/

  What can I say, why is pushing people to update to a previous version
  a thing?

  Please give me a patch that allows users like me to choose whether I
  want to update, OR NOT, and disable the update spam message that
  occurs multiple times a day!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970492/+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 1970491] [NEW] ubuntu-22.04 could not run firefox -safe-mofe

2022-04-26 Thread Seiichi Nakashima

Public bug reported:

Hi,

I download and install ubuntu-22.04-desktop-amd64.iso( 2022-04-19 )
and I want to set firefox peformance option changing off to use safemode.
but do not work.

nakasima@nakasima-pc:~$ uname -a
Linux nakasima-pc 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

nakasima@nakasima-pc:~$ firefox -safe-mode
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
Gtk-Message: 07:00:45.360: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:00:45.399: Failed to load module "canberra-gtk-module"

** Affects: xdg-user-dirs-gtk (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-22.04 could not run firefox -safe-mofe

Status in xdg-user-dirs-gtk package in Ubuntu:
  New

Bug description:
  Hi,

  I download and install ubuntu-22.04-desktop-amd64.iso( 2022-04-19 )
  and I want to set firefox peformance option changing off to use safemode.
  but do not work.

  nakasima@nakasima-pc:~$ uname -a
  Linux nakasima-pc 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

  nakasima@nakasima-pc:~$ firefox -safe-mode
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  Gtk-Message: 07:00:45.360: Failed to load module "canberra-gtk-module"
  Gtk-Message: 07:00:45.399: Failed to load module "canberra-gtk-module"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1970491/+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

2022-04-26 Thread James Loh

Yes, Olivier. You are correct. I tried a VM and didn't observe the
problem. However, the problem occurs on real hardware. This problem is
not in Ubuntu 20.04.

-- 
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:
  Incomplete

Bug description:
  Whenever any file is downloaded, the browser will freeze.

  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

[Desktop-packages] [Bug 1970489] [NEW] Some (eg firefox) snap's modal dialogs don't follow dark-theme preference until log out and log back

2022-04-26 Thread Nicolás Abel Carbone

Public bug reported:

In firefox for example, if I change from dark to light theme or from
dark to light, while the main app follow the theme change, the modal
dialogs (eg. Save page as...) don't change theme.

In the attached screenshot, you can see a dark themed firefox and a
light themed modal dialog.

If I log out and back in, the modal dialogs now follow the theme
correctly.

Another app that seems to have the same issue is telegram-desktop. But
other, like vscode or cura-slicer (all snaps) work as expected.

Initially I thought it was a firefox issue and filed a bug report in
bugzilla. You can see the discussion about it here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1766339

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-desktop-portal 1.14.3-0ubuntu2
ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0
Uname: Linux 5.17.0-1003-oem x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 18:29:50 2022
InstallationDate: Installed on 2022-02-02 (83 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: xdg-desktop-portal
UpgradeStatus: Upgraded to jammy on 2022-03-18 (39 days ago)

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1970489/+attachment/5584128/+files/Captura%20desde%202022-04-25%2019-23-12.png

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

Title:
  Some (eg firefox) snap's modal dialogs don't follow dark-theme
  preference until log out and log back

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  In firefox for example, if I change from dark to light theme or from
  dark to light, while the main app follow the theme change, the modal
  dialogs (eg. Save page as...) don't change theme.

  In the attached screenshot, you can see a dark themed firefox and a
  light themed modal dialog.

  If I log out and back in, the modal dialogs now follow the theme
  correctly.

  Another app that seems to have the same issue is telegram-desktop. But
  other, like vscode or cura-slicer (all snaps) work as expected.

  Initially I thought it was a firefox issue and filed a bug report in
  bugzilla. You can see the discussion about it here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1766339

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0
  Uname: Linux 5.17.0-1003-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 18:29:50 2022
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: xdg-desktop-portal
  UpgradeStatus: Upgraded to jammy on 2022-03-18 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1970489/+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 1970248] Re: .deb files open with Archive Manager by default

Manatas, do you have more detail about when you think the behavior
changed?

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

Title:
  .deb files open with Archive Manager by default

Status in snap-store-desktop:
  Triaged
Status in desktop-file-utils package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Jammy:
  Triaged
Status in desktop-file-utils package in Baltix:
  New

Bug description:
  Impact
  --
  Someone who downloads a .deb file usually wants to install the .deb when they 
open it. Opening it with Archive Manager is really confusing.

  Test Case
  -
  Download a .deb
  Open your Downloads folder with the file manager.
  Double click on the .deb
  The Ubuntu Software app should open with a button that says Install.

  More Details
  
  desktop-file-utils provides /etc/gnome/defaults.list
  In that file, there is this line (and several other lines also referring to 
the same .desktop)

  application/vnd.debian.binary-package=snap-store_ubuntu-software-
  local-file.desktop

  But when I look at /snap/snap-store/575/usr/share/applications/
  there is gnome-software-local-file.desktop

  which is a different file name.

  I believe this issue can be fixed in either snap-store or with
  desktop-file-utils.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1970248/+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 1969577] Re: Small icons in app grid of Activities Overview

2022-04-26 Thread Duke

** Summary changed:

- Small icon in Activity Overview
+ Small icons in app grid of Activities Overview

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

Title:
  Small icons in app grid of Activities Overview

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Opinion

Bug description:
  I just installed Ubuntu 22.04 LTS. As soon as I installed, I noticed that the 
icons present in "Show Applications" are smaller than expected (i.e. smaller 
than that used to be in other versions). So here it is:
  https://i.postimg.cc/2jn4xVh3/Screenshot-from-2022-04-20-13-36-48.png

  issue went gone when i disable ubuntu dock extension

  https://i.postimg.cc/cJd7KZr6/Screenshot-from-2022-04-20-13-35-44.png

  Here is my system information:
  $sudo lshw -short
  H/W path Device  Class  Description
  ===
   system 81WA 
(LENOVO_MT_81WA_BU_idea_FM_
  /0   busLNVNB161216
  /0/0 memory 128KiB BIOS
  /0/4 processor  Intel(R) Core(TM) i3-10110U 
CPU
  /0/4/5   memory 128KiB L1 cache
  /0/4/6   memory 512KiB L2 cache
  /0/4/7   memory 4MiB L3 cache
  /0/24memory 4GiB System Memory
  /0/24/0  memory 4GiB Row of chips DDR4 
Synchrono
  /0/24/1  memory [empty]
  /0/100   bridge Intel Corporation
  /0/100/2 /dev/fb0displayCometLake-U GT2 [UHD Graphics]
  /0/100/4 genericXeon E3-1200 v5/E3-1500 
v5/6th G
  /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 
v5
  /0/100/12genericComet Lake Thermal Subsytem
  /0/100/14busComet Lake PCH-LP USB 3.1 
xHCI H
  /0/100/14/0  usb1busxHCI Host Controller
  /0/100/14/0/3input10 input  Microsoft Microsoft Nano 
Transce
  /0/100/14/0/7input16 multimedia Integrated Camera: Integrated 
C
  /0/100/14/0/acommunication  Bluetooth 9460/9560 Jefferson 
Pe
  /0/100/14/1  usb2busxHCI Host Controller
  /0/100/14.2  memory RAM memory
  /0/100/14.3  wlp0s20f3   networkComet Lake PCH-LP CNVi WiFi
  /0/100/15busSerial IO I2C Host Controller
  /0/100/16communication  Comet Lake Management Engine 
Int
  /0/100/17storageComet Lake SATA AHCI 
Controller
  /0/100/19busComet Lake Serial IO I2C Host 
Co
  /0/100/19.2  communication  Intel Corporation
  /0/100/1dbridge Comet Lake PCI Express Root 
Port
  /0/100/1d/0  /dev/nvme0  storageKBG40ZNT256G TOSHIBA MEMORY
  /0/100/1d/0/0hwmon2  disk   NVMe disk
  /0/100/1d/0/2/dev/ng0n1  disk   NVMe disk
  /0/100/1d/0/1/dev/nvme0n1disk   256GB NVMe disk
  /0/100/1d/0/1/1  volume 1023MiB Windows FAT volume
  /0/100/1d/0/1/2  /dev/nvme0n1p2  volume 2047MiB Linux swap volume
  /0/100/1d/0/1/3  /dev/nvme0n1p3  volume 59GiB EFI partition
  /0/100/1d/0/1/4  /dev/nvme0n1p4  volume 175GiB EFI partition
  /0/100/1fbridge Comet Lake PCH-LP LPC Premium 
Co
  /0/100/1f/0  system PnP device PNP0c02
  /0/100/1f/1  system PnP device PNP0c02
  /0/100/1f/2  system PnP device PNP0c02
  /0/100/1f/3  system PnP device PNP0c02
  /0/100/1f/4  genericPnP device INT3f0d
  /0/100/1f/5  input  PnP device PNP0303
  /0/100/1f/6  system PnP device PNP0c02
  /0/100/1f/7  system PnP device PNP0c02
  /0/100/1f/8  input12 input  Ideapad extra buttons
  /0/100/1f.3  card0   multimedia Comet Lake PCH-LP cAVS
  /0/100/1f.3/0input18 input  HDA Intel PCH Mic
  /0/100/1f.3/1input19 input  HDA Intel PCH Headphone
  /0/100/1f.3/2input20 input  HDA Intel PCH HDMI/DP,pcm=3
  /0/100/1f.3/3input21 input  HDA Intel PCH HDMI/DP,pcm=7
  /0/100/1f.3/4input22 input

[Desktop-packages] [Bug 1559129] Re: Replace defaults.list by mimeapps.list

2022-04-26 Thread Mantas Kriaučiūnas

** Tags added: jammy

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

Title:
  Replace defaults.list by mimeapps.list

Status in desktop-file-utils package in Ubuntu:
  Confirmed

Bug description:
  That's something we forgot to do, maybe worth doing before the LTS?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1559129/+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 1969303] Re: "No package to remove" error when attempting to uninstall

2022-04-26 Thread Raquel Montanana Grau

Sorry I changed the status involuntarely. Please roll back

** Changed in: snap-store-desktop
   Status: Confirmed => Fix Released

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1969303/+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 1970248] Re: .deb files open with Archive Manager by default

2022-04-26 Thread Mantas Kriaučiūnas

GNOME 40 and newer doesn't use /usr/share/applications/defaults.list
file, I think this is the main issue why deb files are opened by Archive
Manager, for more info look at

https://help.gnome.org/admin/system-admin-guide/stable/mime-types-
application.html.en

Quick fix could be to change the name of /usr/share/applications/defaults.list 
symlink to mimeapps.list , but I'm not 100% sure, because there is a line in 
/usr/share/applications/gnome-mimeapps.list
application/x-deb=org.gnome.FileRoller.desktop

The /usr/share/applications/mimeapps.list and
/usr/share/applications/gnome-mimeapps.list files specify which
application is registered to open specific MIME types by default. These
files are provided by the distribution.

To override the system defaults for all users on the system, you need to
create a /etc/xdg/mimeapps.list or /etc/xdg/gnome-mimeapps.list file
with a list of MIME types for which you want to override the default
registered application.

Files located in /etc/xdg/ take precedence over files found in
/usr/share/applications/. Additionally, /etc/xdg/gnome-mimeapps.list
takes precedence over /etc/xdg/mimeapps.list

Btw, there is a bug #1559129 (Replace defaults.list by mimeapps.list)
already reported few years ago by Ubuntu developer, but it seems someone
forgot to fix that :(

** Also affects: desktop-file-utils (Baltix)
   Importance: Undecided
   Status: New

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

Title:
  .deb files open with Archive Manager by default

Status in snap-store-desktop:
  Triaged
Status in desktop-file-utils package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Jammy:
  Triaged
Status in desktop-file-utils package in Baltix:
  New

Bug description:
  Impact
  --
  Someone who downloads a .deb file usually wants to install the .deb when they 
open it. Opening it with Archive Manager is really confusing.

  Test Case
  -
  Download a .deb
  Open your Downloads folder with the file manager.
  Double click on the .deb
  The Ubuntu Software app should open with a button that says Install.

  More Details
  
  desktop-file-utils provides /etc/gnome/defaults.list
  In that file, there is this line (and several other lines also referring to 
the same .desktop)

  application/vnd.debian.binary-package=snap-store_ubuntu-software-
  local-file.desktop

  But when I look at /snap/snap-store/575/usr/share/applications/
  there is gnome-software-local-file.desktop

  which is a different file name.

  I believe this issue can be fixed in either snap-store or with
  desktop-file-utils.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/1970248/+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 1559129] Re: Replace defaults.list by mimeapps.list

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: desktop-file-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  Replace defaults.list by mimeapps.list

Status in desktop-file-utils package in Ubuntu:
  Confirmed

Bug description:
  That's something we forgot to do, maybe worth doing before the LTS?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1559129/+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 1966637] Re: don't have good text copy method like on android / ios as using touch monitor, firefox snap

2022-04-26 Thread Florian Klug

I cleanly installed Jammy Jellyfish today on my Thinkpad X1 Yoga 3rd Gen
and can confirm, that with the snap version of firefox neither the gnome
on screen keyboard is triggered nor can one scroll with touch. After
removing the snap version and installing the deb version from the
Mozilla Team PPA both issues work out of the box

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

Title:
  don't have good text copy method like on android / ios as using touch
  monitor, firefox snap

Status in OEM Priority Project:
  New
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  don't have a good text copy method like on android/ios as using a
  touch monitor

  OS: jammy update @ 2022/03/28
  firefox snap: 98.0.2-1 r1154

  it's not good on URL entry or text entry box on the HTML page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966637/+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 1970471] Re: Changing applications bug 22.04LTS

2022-04-26 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (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/1970471

Title:
  Changing applications bug 22.04LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Firefox and the android studio code opened at the same time.
  If I am using Firefox and want to move into studio code, I press the "super" 
key to show all the apps running and click with my mouse the studio code app. 
Instead of showing ASC it keeps showing me Firefox, but not the other way 
around, when I am in ASC and want to change to Firefox, it does change.
  This only happens when using the "super" key by itself, when using "super + 
tab" or "alt + tab" it does change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 21:06:02 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba Corporation HD Graphics 5500 [1179:000a]
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
   |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 
480M
   |__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
   |__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  MachineType: TOSHIBA Satellite Pro R50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=b739b2dd-b328-4bee-a14e-8e1cc4583783 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2015
  dmi.bios.release: 1.20
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.20
  dmi.board.asset.tag: 00
  dmi.board.name: Satellite Pro R50-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.20:bd01/30/2015:br1.20:efr1.10:svnTOSHIBA:pnSatelliteProR50-B:pvrPSSG2E-00K004CE:rvnTOSHIBA:rnSatelliteProR50-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPSSG2E:
  dmi.product.family: 00
  dmi.product.name: Satellite Pro R50-B
  dmi.product.sku: PSSG2E
  dmi.product.version: PSSG2E-00K004CE
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/ubuntu/+source/xorg/+bug/1970471/+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 1970471] [NEW] Changing applications bug 22.04LTS

You have been subscribed to a public bug:

I have Firefox and the android studio code opened at the same time.
If I am using Firefox and want to move into studio code, I press the "super" 
key to show all the apps running and click with my mouse the studio code app. 
Instead of showing ASC it keeps showing me Firefox, but not the other way 
around, when I am in ASC and want to change to Firefox, it does change.
This only happens when using the "super" key by itself, when using "super + 
tab" or "alt + tab" it does change.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 21:06:02 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Toshiba Corporation HD Graphics 5500 [1179:000a]
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
 |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
 |__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
 |__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
MachineType: TOSHIBA Satellite Pro R50-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=b739b2dd-b328-4bee-a14e-8e1cc4583783 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/30/2015
dmi.bios.release: 1.20
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.20
dmi.board.asset.tag: 00
dmi.board.name: Satellite Pro R50-B
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.ec.firmware.release: 1.10
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.20:bd01/30/2015:br1.20:efr1.10:svnTOSHIBA:pnSatelliteProR50-B:pvrPSSG2E-00K004CE:rvnTOSHIBA:rnSatelliteProR50-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPSSG2E:
dmi.product.family: 00
dmi.product.name: Satellite Pro R50-B
dmi.product.sku: PSSG2E
dmi.product.version: PSSG2E-00K004CE
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
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 jammy ubuntu wayland-session
-- 
Changing applications bug 22.04LTS
https://bugs.launchpad.net/bugs/1970471
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
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 1970131] Re: Can't rotate display with AMD graphics on 22.04 LTS

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

** This bug has been marked a duplicate of bug 1970473
   Xorg crash

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

Title:
  Can't rotate display with AMD graphics on 22.04 LTS

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  Ubuntu 22.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970131/+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 1970131] Re: Can't rotate display with AMD graphics on 22.04 LTS

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

Bug #1970473 reported by me with apport duplicates this bug

Please mark as duplicate and fix with that information
Replication is easy! Just use AMD graphics and rotate.

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

Title:
  Can't rotate display with AMD graphics on 22.04 LTS

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  Ubuntu 22.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970131/+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 1970473] [NEW] Xorg crash

Public bug reported:

When using Settings/Display/Orientation/Portret right and Apply then X
crashes and login screen is displayed. Tested with 3 different AMD
systems (older). Bug is not present with Intel graphics

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.470
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 19:30:33 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2010
dmi.bios.release: 1.11
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G6 v01.11
dmi.board.asset.tag: CZC1332VBJ
dmi.board.name: 3047h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC1332VBJ
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq 6005 Pro MT PC
dmi.product.sku: AT493AV
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
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 crash jammy 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/1970473

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias:

[Desktop-packages] [Bug 1970131] Re: Can't rotate display with AMD graphics on 22.04 LTS

Apport cannot collect or upload more information AFTER X crashed and I login
again to desktop!
Authorized in browser with my account as required

ubuntu@ubuntu:~$ apport-collect 1970131
The authorization page:

(https://launchpad.net/+authorize-token?oauth_token=0h79wv3scsGhvtz9cbkL_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
Gtk-Message: 19:02:21.185: Failed to load module "canberra-gtk-module"
Gtk-Message: 19:02:21.188: Failed to load module "canberra-gtk-module"
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
Package mutter not installed and no hook available, ignoring

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

Title:
Can't rotate display with AMD graphics on 22.04 LTS

Status in mutter package in Ubuntu:
Incomplete

Bug description:
When using Settings/Display/Orientation/Portret right and Apply then X
crashes and login screen is displayed. Tested with 3 different AMD
systems (older). Bug is not present with Intel graphics

Ubuntu 22.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970131/+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 1970470] [NEW] Loading circle takes some time to disappear on Flatpak apps

2022-04-26 Thread Manu Romero

Public bug reported:

When opening a Flatpak app, it opens as usual, but even when it's
already open, the loading circle in the top panel doesn't dissapear
until some time (~10 sec). As a side effect, the app takes long time to
show up in the dock.

If I open the app via `flatpak run app` in terminal, this issue does not
occur. It only happens when opening it from the app drawer or the search
function in Activities.

Ubuntu version: Ubuntu 22.04 LTS
Package version: 42.0-2ubuntu1

Expected to happen: The loading circle on the top panel should disappear as 
soon as the app loads when it's launched from the app drawer.
What happened: The loading circle remains a few seconds and that leads to the 
app icon not showing in the dock.

Hardware:
* CPU: Intel Core i7-7500U
* RAM: 16 GB DDR4 2133 MHz
* GPU: Intel HD Graphics 620 (using the Wayland session)

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


** Tags: 22.04 flatpak gnome

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

Title:
  Loading circle takes some time to disappear on Flatpak apps

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When opening a Flatpak app, it opens as usual, but even when it's
  already open, the loading circle in the top panel doesn't dissapear
  until some time (~10 sec). As a side effect, the app takes long time
  to show up in the dock.

  If I open the app via `flatpak run app` in terminal, this issue does
  not occur. It only happens when opening it from the app drawer or the
  search function in Activities.

  Ubuntu version: Ubuntu 22.04 LTS
  Package version: 42.0-2ubuntu1

  Expected to happen: The loading circle on the top panel should disappear as 
soon as the app loads when it's launched from the app drawer.
  What happened: The loading circle remains a few seconds and that leads to the 
app icon not showing in the dock.

  Hardware:
  * CPU: Intel Core i7-7500U
  * RAM: 16 GB DDR4 2133 MHz
  * GPU: Intel HD Graphics 620 (using the Wayland session)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970470/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

2022-04-26 Thread Alexander Browne

** Summary changed:

- "Connection failed" for WPA Enterprise network eduroam
+ "Connection failed" for WPA Enterprise network (e.g. eduroam)

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

** Description changed:

- GNOME Remote desktop crashes if fuse3 package is not installed as it
- provides fusermount3, that fuse_session_mount() implicitly requires.
+ Impact
+ ==
+ GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.
  
- libfuse3 is currently suggesting fusermount3, I'm wondering if we should
- instead recommending it, given that one of the library function relies
- on that.
+ Test Case
+ =
+ Verify that gnome-remote-desktop has a dependency on fuse3
  
- Otherwise, we should probably make the g-r-d dependency stronger.
+ What Could Go Wrong
+ ==
+ This just adds a dependency.
+ 
+ This bug should be very uncommon because a system without fuse3 also
+ wouldn't have xdg-desktop-portal installed meaning Snaps don't work and
+ wouldn't have ubuntu-desktop-minimal installed.
+ 
+ Other Info
+ =
+ libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.
+ 
+ For Ubuntu 22.10, we should see if the kernel can support this natively
+ without needing fusermount3 as suggested in comment 1.
+ 
  
  Stack trace:
  
  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
- writer_func = 
- writer_user_data = 
- recursion = 
- depth = 
- __func__ = "g_log_structured_array"
- _g_boolean_var_ = 
+ writer_func = 
+ writer_user_data = 
+ recursion = 
+ depth = 
+ __func__ = "g_log_structured_array"
+ _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
- fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
- n_fields = 
+ fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
+ n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
- domain = 0x0
- data = 0x0
- depth = 
- log_func = 0x7f79092e2ee0 
- domain_fatal_mask = 
- masquerade_fatal = 0
- test_level = 6
- was_fatal = 
- was_recursion = 
- buffer = 
- msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
- msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
- i = 2
- size = 
+ domain = 0x0
+ data = 0x0
+ depth = 
+ log_func = 0x7f79092e2ee0 
+ domain_fatal_mask = 
+ masquerade_fatal = 0
+ test_level = 6
+ was_fatal = 
+ was_recursion = 
+ buffer = 
+ msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
+ msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
+ i = 2
+ size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
- args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
+ args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed301820) at 
../src/grd-rdp-fuse-clipboard.c:1321
- rdp_fuse_clipboard = 0x5605ed301820
- args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
- argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
- result = 
- 
+ rdp_fuse_clipboard = 0x5605ed301820
+ args = {argc = 1, argv = 0x7f7860001070, allocated = 1}
+ argv = {0x7ffe23912a12 "/usr/libexec/gnome-remote-desktop-daemon"}
+ result = 
  
  Further details:
-  -

[Desktop-packages] [Bug 1970072] Re: Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

2022-04-26 Thread ebsf

Regarding 22.04, please advise what reason exists to think it might be
better.

Also, please advise why I should spend days reinstalling because of
someone else's failure instead of the failure being addressed.

Besides, note https://bugs.launchpad.net/subiquity/+bug/1970140.  The
22.04 server installer fails.  Some idiot thought to implement kernel
video drivers in the live iso, and further, to switch to nouveau without
disabling kernel mode setting, and further, not to provide any boot
alternatives, and further, to provide no documentation (the server
reference is for 20.04.  One cannot imagine a more sublime or
humiliating failure, for all to see.  I'll need a reason to take the
time even to download the ISO.

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

Title:
  Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Ubuntu 20.04.4 has GUI freezes frequently (i.e., a
  dozen times daily) at inconsistent intervals and times, and not
  obviously in response to any particular user input.  The system then
  is unresponsive to user input, although the mouse cursor does continue
  to move about.

  The syslog messages reveal the message from gsd-media-keys "[GFX1]:
  Device reset due to WR context"

  The freeze also is preceded by often hundreds of pulseaudio messages
  related to latency issues, notwithstanding that no audio is playing.
  Often, gdm-x-session messages appear referencing the NVIDIA GPU and
  "WAIT".  The pulseaudio message "setting avail_min=87496" often is the
  last message and if not, one of the last, before the reboot.

  Also common before is a gnome-shell message "Ignored exception from
  dbus method: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  com.gonzaarcr.appmenu was not provided by any .service files", which
  precedes the pulseaudio messages.

  Happy to provide any other information but would welcome some guidance
  because I'm on day 11 or 12 of this installation and wearing out my
  welcome at Google.

  Ubuntu 20.04.4 LTS

  apt-cache returns:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expected behavior:  Stability, especially from the fourth release of a
  LTS.

  Behavior:  Persistent GUI freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 23 16:26:45 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-09 (14 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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/1970072/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

2022-04-26 Thread Matthew M. Dean

gnome-shell/jammy,now 42.0-2ubuntu1 amd64 [installed]
  graphical shell for the GNOME desktop

As sure as when I opened the original bug.

Are you sure your receiving reports? Are you talking about that popup
that that says Ubuntu has encountered and error and do you want to send
an error report or something? That doesn't happen.

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1969422/+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 1970072] Re: Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

2022-04-26 Thread ebsf

Trying the attachment again.

The interface won't allow designation of more than one.

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970072/+attachment/5584043/+files/lspci.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/1970072

Title:
  Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Ubuntu 20.04.4 has GUI freezes frequently (i.e., a
  dozen times daily) at inconsistent intervals and times, and not
  obviously in response to any particular user input.  The system then
  is unresponsive to user input, although the mouse cursor does continue
  to move about.

  The syslog messages reveal the message from gsd-media-keys "[GFX1]:
  Device reset due to WR context"

  The freeze also is preceded by often hundreds of pulseaudio messages
  related to latency issues, notwithstanding that no audio is playing.
  Often, gdm-x-session messages appear referencing the NVIDIA GPU and
  "WAIT".  The pulseaudio message "setting avail_min=87496" often is the
  last message and if not, one of the last, before the reboot.

  Also common before is a gnome-shell message "Ignored exception from
  dbus method: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  com.gonzaarcr.appmenu was not provided by any .service files", which
  precedes the pulseaudio messages.

  Happy to provide any other information but would welcome some guidance
  because I'm on day 11 or 12 of this installation and wearing out my
  welcome at Google.

  Ubuntu 20.04.4 LTS

  apt-cache returns:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expected behavior:  Stability, especially from the fourth release of a
  LTS.

  Behavior:  Persistent GUI freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 23 16:26:45 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-09 (14 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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/1970072/+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 1970072] Re: Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

2022-04-26 Thread ebsf

Regarding the file request, please see attached.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970072/+attachment/5584042/+files/prevboot.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/1970072

Title:
  Frequent GPU Resets (and GUI Freeze) by gsd-media-keys

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Ubuntu 20.04.4 has GUI freezes frequently (i.e., a
  dozen times daily) at inconsistent intervals and times, and not
  obviously in response to any particular user input.  The system then
  is unresponsive to user input, although the mouse cursor does continue
  to move about.

  The syslog messages reveal the message from gsd-media-keys "[GFX1]:
  Device reset due to WR context"

  The freeze also is preceded by often hundreds of pulseaudio messages
  related to latency issues, notwithstanding that no audio is playing.
  Often, gdm-x-session messages appear referencing the NVIDIA GPU and
  "WAIT".  The pulseaudio message "setting avail_min=87496" often is the
  last message and if not, one of the last, before the reboot.

  Also common before is a gnome-shell message "Ignored exception from
  dbus method: Gio.DBusError:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  com.gonzaarcr.appmenu was not provided by any .service files", which
  precedes the pulseaudio messages.

  Happy to provide any other information but would welcome some guidance
  because I'm on day 11 or 12 of this installation and wearing out my
  welcome at Google.

  Ubuntu 20.04.4 LTS

  apt-cache returns:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Expected behavior:  Stability, especially from the fourth release of a
  LTS.

  Behavior:  Persistent GUI freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr 23 16:26:45 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-04-09 (14 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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/1970072/+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 1969842] Re: No font available after installing in user space

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: snapd (Ubuntu)
   Status: New => Confirmed

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

Title:
  No font available after installing in user space

Status in libreoffice package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I can't find the installed "Ecofont Vera Sans" under LibreOffice
  (7.3.2.2)  in Ubuntu (20.04.4 LTS).

  ---
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ---
  LibreOffice (snap snapcraft.io)
  Version: 7.3.2.2 / LibreOffice Community
  Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
  CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

  ---
  Ecofont Vera Sans Download page: 
https://www.fonts4free.net/ecofont-vera-sans-font.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969842/+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 1969842] Re: No font available after installing in user space

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libreoffice (Ubuntu)
   Status: New => Confirmed

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

Title:
  No font available after installing in user space

Status in libreoffice package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I can't find the installed "Ecofont Vera Sans" under LibreOffice
  (7.3.2.2)  in Ubuntu (20.04.4 LTS).

  ---
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ---
  LibreOffice (snap snapcraft.io)
  Version: 7.3.2.2 / LibreOffice Community
  Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
  CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

  ---
  Ecofont Vera Sans Download page: 
https://www.fonts4free.net/ecofont-vera-sans-font.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969842/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-04-26 Thread Clemens Lang

See also https://bugzilla.redhat.com/show_bug.cgi?id=2069239. For those
that have this problem with the "0A0C0103:SSL routines::internal error"
message, check whether your radius server possibly only supports TLS 1.1
or older. Those servers would default to rsa_pkcs1_md5_sha1 as TLS
signature algorithm, which does not meet the 80 bits of security
requirement of OpenSSL 3's default SECLEVEL of 1.

Try setting SECLEVEL to 0 to see if that fixes the issue for you. Talk
to your Radius server administrator to recommend they offer TLS 1.2 or
higher.

** Bug watch added: Red Hat Bugzilla #2069239
   https://bugzilla.redhat.com/show_bug.cgi?id=2069239

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1969842] Re: No font available after installing in user space

2022-04-26 Thread Rico Tzschichholz

This procedure will install the font to "$HOME/.local/share/fonts/"
which is not accessible by the LibreOffice snap due to its confinement.

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

Title:
  No font available after installing in user space

Status in libreoffice package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I can't find the installed "Ecofont Vera Sans" under LibreOffice
  (7.3.2.2)  in Ubuntu (20.04.4 LTS).

  ---
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  ---
  LibreOffice (snap snapcraft.io)
  Version: 7.3.2.2 / LibreOffice Community
  Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528
  CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3
  Locale: it-IT (en_US.UTF-8); UI: en-US
  Calc: threaded

  ---
  Ecofont Vera Sans Download page: 
https://www.fonts4free.net/ecofont-vera-sans-font.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969842/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-04-26 Thread Christopher Barrington-Leigh

Whoops -- actually, my enterprise network was a university's main wifi
(wpa.mcgill.ca), not eduroam. I propose to generalize the title of this
bug by dropping eduroam or changing it to (e.g. eduroam)

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-04-26 Thread Christopher Barrington-Leigh

On a Thinkpad X230 I had this problem after upgrading to 22.04.

The recipe in comment 23 by nfalse solved the problem for me.

Thank you (though this is only a temporary workaround, given its use of
"UnsafeLegacyRenegotiation")

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1965314] Autopkgtest regression report (firejail/0.9.68-3ubuntu1)

2022-04-26 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted firejail (0.9.68-3ubuntu1) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

firejail/0.9.68-3ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#firejail

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Please remove firefox binaries for ppc64el and s390x from the release
  pocket

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  With bug #1962021, the firefox packages in jammy are becoming "transitional 
packages" that install the firefox snap and wrapper scripts.
  However the snap is available only on amd64, armhf and arm64, so to allow the 
new packages to migrate the existing binaries for ppc64el and s390x that are no 
longer built from source need to be removed.

  For s390x this should be fairly uncontroversial, as Ubuntu desktop in
  general isn't officially supported on this architecture, and firefox
  isn't tested there, only known to build successfully (autopkgtests
  have always been failing there).

  For ppc64el this is perhaps a bit more controversial, although the
  reality is that firefox on this architecture receives no testing from
  Ubuntu developers (not from the desktop team anyway), and autopkgtests
  have always been failing there. I don't have numbers of firefox users
  on this architecture.

  Note that upstream is not committed to supporting these architectures
  either, they fall in their Tier-3 targets (see https://firefox-source-
  docs.mozilla.org/contributing/build/supported.html#supported-build-
  targets). Given that the maintenance of the firefox snap is a joint
  effort between Mozilla and the Ubuntu desktop team, it is unlikely
  that we will start building the firefox snap for ppc64el or s390x.

  The binaries that need removing are: firefox, firefox-dbg, firefox-
  dev, firefox-geckodriver.

  The last three in the list (firefox-dbg, firefox-dev, firefox-geckodriver) do 
not have any reverse dependencies.
  The binary package firefox itself is recommended or suggested by a good 
number of packages, and is also a direct dependency of the following packages:
    - cinnamon-desktop-environment (all): depends on "firefox-esr | firefox | 
chromium | gnome-www-browser"
    - firefox-dbg: not an issue as this one also needs removing
    - firefox-geckodriver: not an issue as this one also needs removing
    - firefox-launchpad-plugin (all): depends on "firefox"
    - gnome-core (linux-any): depends on "firefox-esr (>= 78) | firefox (>= 78) 
| chromium | chromium-browser | epiphany-browser"
    - webhttrack (any): depends on "iceape-browser | iceweasel | icecat | 
mozilla | firefox | mozilla-firefox | www-browser"
    - x2gothinclient-minidesktop (all): depends on "firefox-esr | firefox | 
chromium | x-www-browser"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965314/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"

2022-04-26 Thread Blaze

I do use a gateway actually

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

Title:
  remmina "Cannot connect to the RDP server ... via TLS. Check that the
  client and server support a common TLS version"

Status in freerdp2 package in Ubuntu:
  Confirmed
Status in freerdp2 source package in Jammy:
  Confirmed

Bug description:
  Xubuntu Jammy (21.04)
  after upgrade
 libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
 libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
  Remmina can't connect to any RDP server (Win2008 R2) with error:
  "Cannot connect to the RDP server ... via TLS. Check that the client and 
server support a common TLS version"

  Rollback to Impish version of libs
 libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2
 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2
  makes it work normal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1970413] Re: Moving windows around is laggy

2022-04-26 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (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/1970413

Title:
  Moving windows around is laggy

Status in xorg package in Ubuntu:
  New

Bug description:
  When I move a window around, it's lagging and sometimes it's freezing
  for a second. This is happening after the upgrade to Ubuntu 22.04.
  Also, it happens all the time, even after I restart my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 15:09:42 2022
  DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed
   nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] 
[1458:3733]
  InstallationDate: Installed on 2021-11-08 (168 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/ubuntu/+source/xorg/+bug/1970413/+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 1970413] [NEW] Moving windows around is laggy

You have been subscribed to a public bug:

When I move a window around, it's lagging and sometimes it's freezing
for a second. This is happening after the upgrade to Ubuntu 22.04. Also,
it happens all the time, even after I restart my computer.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-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  510.60.02  Wed Mar 16 11:24:05 
UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 15:09:42 2022
DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed
 nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] 
[1458:3733]
InstallationDate: Installed on 2021-11-08 (168 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
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 jammy performance ubuntu
-- 
Moving windows around is laggy
https://bugs.launchpad.net/bugs/1970413
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"

2022-04-26 Thread msaxl

> I've been testing this patch and it didn't help in my case

what would probably be useful in this thread if someone would post the
output of ex.

xfreerdp /v:  /log-level:debug

I know we are talk about remmina here, but it would be very strange if
xfreerdp works and remmina doesn't.

For me before applying this patch the relevant last lines where

[DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_HYBRID
[ERROR][com.freerdp.core] - rdg_process_close_packet:freerdp_set_last_error_ex 
E_PROXY_INTERNALERROR [0x800759D8]
[com.freerdp.core.nego] - Failed to connect with NLA security

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

Title:
  remmina "Cannot connect to the RDP server ... via TLS. Check that the
  client and server support a common TLS version"

Status in freerdp2 package in Ubuntu:
  Confirmed
Status in freerdp2 source package in Jammy:
  Confirmed

Bug description:
  Xubuntu Jammy (21.04)
  after upgrade
 libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
 libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1)
  Remmina can't connect to any RDP server (Win2008 R2) with error:
  "Cannot connect to the RDP server ... via TLS. Check that the client and 
server support a common TLS version"

  Rollback to Impish version of libs
 libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2
 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2
  makes it work normal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

2022-04-26 Thread Stefan Bader

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
  KMS update: CRTC property (GAMMA_LUT) not found]

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  Screen can't turn back on by clicking keyboard after screen off by meta + l 
key.
  Try to do VT switch can make the screen back, some error poped when I try to 
wake up screen.

  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-03-31 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Tags: wayland-session jammy third-party-packages
  Uname: Linux 5.15.0-23-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

  ==

  SRU Justification

  [Impact]
  The backlight power won't come back after the meta + l to turn off the 
display on ADL machines.

  [Fix]
  Below series of commits from v5.17 fix this issue
  1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
  17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
  e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform

  [Test]
  Verified on at least 2 different machines, the backlight is on after the 
screen dimmed with touchpad movement or key stroke.

  [Where problems could occcur]
  The patches only affect ADL-P and up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1970141] Re: Desktop background is no longer displayed always solid black

2022-04-26 Thread Brian Murray

** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell
(Ubuntu)

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

Title:
  Desktop background is no longer displayed always solid black

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi I'm running Ubuntu 20.4 with the Apr 20 updates applied.

  gnome-session:
Installed: (none)
Candidate: 3.36.0-2ubuntu1
Version table:
   3.36.0-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages
  gnome-shell:
Installed: 3.36.9-0ubuntu0.20.04.2
Candidate: 3.36.9-0ubuntu0.20.04.2
Version table:
   *** 3.36.9-0ubuntu0.20.04.2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.4-1ubuntu1~20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   3.36.1-5ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  I accept that this is "cosmetic" but it's still annoying.

  I have two large monitors attached which I run as a large single
  workspace across both screens.

  I have been running this for years without problem over several Ubuntu
  releases.

  Following the recent upgrade (Apr 20 2022), my desktop wallpaper is no
  longer displayed properly.

  Almost all of it is covered in solid black except for a very small
  sliver of the wallpaper at the bottom of each screen.

  If I change the desktop background there is no effect (except for the
  small sliver at the bottom of the screen) changes.

  If I reboot, or if I log in as a different user, there is no change.

  If I click "Activities" or press the Windows button, the menu of
  desktops I can switch to is displayed with the correct wallpaper, but
  when I switch to it it comes out all black on both screens (apart from
  the icons, any windows and the sliver at the bottom of the screen).

  I have 2 different laptops which I have upgraded also but those are
  OK. I've not tried any dual-screen on them.

  Possibly relevant is that I have an nVidia display controller.

  It does appear to be a problem that has crept in with the most recent
  update.

  Everything else I do is unaffected as far as I can see but I'd just
  like something different from the boring solid black.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.37
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 22:47:59 2022
  InstallationDate: Installed on 2020-10-10 (561 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-10-10T15:40:13.152625

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970141/+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 1970141] [NEW] Desktop background is no longer displayed always solid black

You have been subscribed to a public bug:

Hi I'm running Ubuntu 20.4 with the Apr 20 updates applied.

gnome-session:
  Installed: (none)
  Candidate: 3.36.0-2ubuntu1
  Version table:
 3.36.0-2ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages
gnome-shell:
  Installed: 3.36.9-0ubuntu0.20.04.2
  Candidate: 3.36.9-0ubuntu0.20.04.2
  Version table:
 *** 3.36.9-0ubuntu0.20.04.2 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.4-1ubuntu1~20.04.2 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 3.36.1-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

I accept that this is "cosmetic" but it's still annoying.

I have two large monitors attached which I run as a large single
workspace across both screens.

I have been running this for years without problem over several Ubuntu
releases.

Following the recent upgrade (Apr 20 2022), my desktop wallpaper is no
longer displayed properly.

Almost all of it is covered in solid black except for a very small
sliver of the wallpaper at the bottom of each screen.

If I change the desktop background there is no effect (except for the
small sliver at the bottom of the screen) changes.

If I reboot, or if I log in as a different user, there is no change.

If I click "Activities" or press the Windows button, the menu of
desktops I can switch to is displayed with the correct wallpaper, but
when I switch to it it comes out all black on both screens (apart from
the icons, any windows and the sliver at the bottom of the screen).

I have 2 different laptops which I have upgraded also but those are OK.
I've not tried any dual-screen on them.

Possibly relevant is that I have an nVidia display controller.

It does appear to be a problem that has crept in with the most recent
update.

Everything else I do is unaffected as far as I can see but I'd just like
something different from the boring solid black.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.37
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 24 22:47:59 2022
InstallationDate: Installed on 2020-10-10 (561 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-10-10T15:40:13.152625

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


** Tags: amd64 apport-bug dist-upgrade focal
-- 
Desktop background is no longer displayed always solid black
https://bugs.launchpad.net/bugs/1970141
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
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 1970168] Re: File-save prompt is extremely buggy, potentially unusable

I believe the "unable to save" part of this bug is
https://launchpad.net/bugs/1969622 and the fix is rolling out as an
update now.

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

Title:
  File-save prompt is extremely buggy, potentially unusable

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  File-save prompt/window keeps growing after every save and won't
  resize once fullscreen until I change the scaling factor and change it
  back so it becomes small. Sometimes it won't let me save or exit the
  prompt at all. Once I traverse through folders within the prompt it
  requires me to edit the filename to enable the "Save" button. Not an
  issue in 21.10, only on 22.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 19:16:37 2022
  InstallationDate: Installed on 2022-04-23 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   10   Done2022-04-24T20:15:28+12:00  2022-04-24T20:15:28+12:00  Refresh 
"firefox" snap from "latest/stable" channel
   12   Done2022-04-24T20:46:41+12:00  2022-04-24T20:48:10+12:00  Remove 
"firefox" snap
   13   Done2022-04-24T20:50:08+12:00  2022-04-24T20:50:55+12:00  Install 
"firefox" snap
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970168/+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 1970424] Re: firefox snap can not open any file dialogs

ubuntu-desktop-minimal Recommends xdg-desktop-portal-gnome and
Recommends are installed by default.

If you intentionally don't install Recommends, then your system will
have bugs like this.

But we can look at making the dependency stronger.

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Invalid

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

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-meta (Ubuntu)
   Status: Invalid => Triaged

** Summary changed:

- firefox snap can not open any file dialogs
+ Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

** Description changed:

+ I propose having ubuntu-desktop-minimal depend on
+ xdg-desktop-portal-gnome | xdg-desktop-portal-backend
+ 
+ Currently, there is only a Recommends on xdg-desktop-portal-gnome.
+ 
+ If a system doesn't have that dependency installed, then desktop snaps
+ including our critical Firefox and Chromium snaps have severe missing
+ functionality.
+ 
+ Original Bug Report
+ ---
  With ubuntu 22.04 firefox comes as snap package by default.
  
  it is not possible to open any file dialog. save graphics as, save html
  page, import certificate never opens a file dialog.
  
  firefox is completly useless without that file dialog.
  
  (the root case is ubuntu uses snap)
  
  further: in snap store firefox has no icon and it's called firefox not
  "Firefox".

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Medium => High

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

Title:
  Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  I propose having ubuntu-desktop-minimal depend on
  xdg-desktop-portal-gnome | xdg-desktop-portal-backend

  Currently, there is only a Recommends on xdg-desktop-portal-gnome.

  If a system doesn't have that dependency installed, then desktop snaps
  including our critical Firefox and Chromium snaps have severe missing
  functionality.

  Original Bug Report
  ---
  With ubuntu 22.04 firefox comes as snap package by default.

  it is not possible to open any file dialog. save graphics as, save
  html page, import certificate never opens a file dialog.

  firefox is completly useless without that file dialog.

  (the root case is ubuntu uses snap)

  further: in snap store firefox has no icon and it's called firefox not
  "Firefox".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1970424/+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 1970445] Re: Browser Save Dialog - Save button does become disabled when switching to a (sub)directory

2022-04-26 Thread Paul White

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

Already fixed as per bug #1969622 but thanks for reporting.

** This bug has been marked a duplicate of bug 1969622
   save file dialog doesn't allow saving to a directory without 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/1970445

Title:
  Browser Save Dialog - Save button does become disabled when switching
  to a (sub)directory

Status in nautilus package in Ubuntu:
  New

Bug description:
  When pressing save on a browser, the save dialog opens.
  You can press save in the current (last) directory. The button is enabled and 
NOT grayed out.

  If for example there is a ~/Downloads/test directory, switching to the
  test directory does disable the save button.

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  nautilus:
Installed: 1:42.0-1ubuntu2
Candidate: 1:42.0-1ubuntu2
Version table:
   *** 1:42.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What you expected to happen
  When saving a file from a browser; i expect to be able to select a different 
already existing directory as save location and save the file in that directory.

  What happened instead
  When switching to directory during the  download promt, the save button 
becomes disabled.

  Workaround
  When the save is blocked - add and a remove a space to the filename pending. 
That does reenable the save.
  This is NOT an issue for directories created within the download promt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970445/+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 1970445] [NEW] Browser Save Dialog - Save button does become disabled when switching to a (sub)directory

2022-04-26 Thread Daniel R

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

Public bug reported:

When pressing save on a browser, the save dialog opens.
You can press save in the current (last) directory. The button is enabled and 
NOT grayed out.

If for example there is a ~/Downloads/test directory, switching to the
test directory does disable the save button.

Description:Ubuntu 22.04 LTS
Release:22.04

nautilus:
  Installed: 1:42.0-1ubuntu2
  Candidate: 1:42.0-1ubuntu2
  Version table:
 *** 1:42.0-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

What you expected to happen
When saving a file from a browser; i expect to be able to select a different 
already existing directory as save location and save the file in that directory.

What happened instead
When switching to directory during the  download promt, the save button becomes 
disabled.

Workaround
When the save is blocked - add and a remove a space to the filename pending. 
That does reenable the save.
This is NOT an issue for directories created within the download promt.

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

** Attachment added: "sample steps images"
   https://bugs.launchpad.net/bugs/1970445/+attachment/5583985/+files/steps.zip

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

Title:
  Browser Save Dialog - Save button does become disabled when switching
  to a (sub)directory

Status in nautilus package in Ubuntu:
  New

Bug description:
  When pressing save on a browser, the save dialog opens.
  You can press save in the current (last) directory. The button is enabled and 
NOT grayed out.

  If for example there is a ~/Downloads/test directory, switching to the
  test directory does disable the save button.

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  nautilus:
Installed: 1:42.0-1ubuntu2
Candidate: 1:42.0-1ubuntu2
Version table:
   *** 1:42.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What you expected to happen
  When saving a file from a browser; i expect to be able to select a different 
already existing directory as save location and save the file in that directory.

  What happened instead
  When switching to directory during the  download promt, the save button 
becomes disabled.

  Workaround
  When the save is blocked - add and a remove a space to the filename pending. 
That does reenable the save.
  This is NOT an issue for directories created within the download promt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970445/+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 1970401] Re: Gnome screen recorder don`t start or not installed on 22.04

2022-04-26 Thread Brian Murray

** Project changed: gnome-shell => gnome-shell (Ubuntu)

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

Title:
  Gnome screen recorder don`t  start or not installed on 22.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Problem: Gnome screen recorder dont start. If I use  Ctrl + Alt + Shift + R 
nothing happens.
  If I use PrintScrn , screenshot and screen-recorder appears. screenshot 
works, but screen recorder not, only for half a second appear on top bar the 
red 00:00 but disappears without recording. 
  I thought its problem of zero  screencast-length but its not that, because on 
dconf there is not  
org.gnome.settings-daemon.plugins.media-keys.max-screencast-length 
  also on gsettings, for example if I command 
  $ gsettings set org.gnome.settings-daemon.plugins.media-keys 
max-screencast-length 300
  No such key “max-screencast-length”

  It looks to me that screencast is not installed(?) 
  or something conflicts? 

  system software info:

  $ cat /etc/*release* && uname -ar
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS"
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  Linux all1 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

  $ gnome-shell --version
  GNOME Shell 42.0

  $ gsettings list-recursively | grep org.gnome.shell.keybindings
  org.gnome.shell.keybindings focus-active-notification ['n']
  org.gnome.shell.keybindings open-application-menu ['F10']
  org.gnome.shell.keybindings screenshot ['Print']
  org.gnome.shell.keybindings screenshot-window ['Print']
  org.gnome.shell.keybindings shift-overview-down ['Down']
  org.gnome.shell.keybindings shift-overview-up ['Up']
  org.gnome.shell.keybindings show-screen-recording-ui ['R']
  org.gnome.shell.keybindings show-screenshot-ui ['Print']
  org.gnome.shell.keybindings switch-to-application-1 ['1']
  org.gnome.shell.keybindings switch-to-application-2 ['2']
  org.gnome.shell.keybindings switch-to-application-3 ['3']
  org.gnome.shell.keybindings switch-to-application-4 ['4']
  org.gnome.shell.keybindings switch-to-application-5 ['5']
  org.gnome.shell.keybindings switch-to-application-6 ['6']
  org.gnome.shell.keybindings switch-to-application-7 ['7']
  org.gnome.shell.keybindings switch-to-application-8 ['8']
  org.gnome.shell.keybindings switch-to-application-9 ['9']
  org.gnome.shell.keybindings toggle-application-view ['a']
  org.gnome.shell.keybindings toggle-message-tray ['v', 'm']
  org.gnome.shell.keybindings toggle-overview ['s']

  $ gsettings list-recursively | grep 
org.gnome.settings-daemon.plugins.media-keys
  org.gnome.settings-daemon.plugins.media-keys battery-status ['']
  org.gnome.settings-daemon.plugins.media-keys battery-status-static 
['XF86Battery']
  org.gnome.settings-daemon.plugins.media-keys calculator ['']
  org.gnome.settings-daemon.plugins.media-keys calculator-static 
['XF86Calculator']
  org.gnome.settings-daemon.plugins.media-keys control-center ['']
  org.gnome.settings-daemon.plugins.media-keys control-center-static 
['XF86Tools']
  org.gnome.settings-daemon.plugins.media-keys custom-keybindings @as []
  org.gnome.settings-daemon.plugins.media-keys decrease-text-size ['']
  org.gnome.settings-daemon.plugins.media-keys eject ['']
  org.gnome.settings-daemon.plugins.media-keys eject-static ['XF86Eject']
  org.gnome.settings-daemon.plugins.media-keys email ['']
  org.gnome.settings-daemon.plugins.media-keys email-static ['XF86Mail']
  org.gnome.settings-daemon.plugins.media-keys help ['', 'F1']
  org.gnome.settings-daemon.plugins.media-keys hibernate ['']
  org.gnome.settings-daemon.plugins.media-keys hibernate-static ['XF86Suspend', 
'XF86Hibernate']
  org.gnome.settings-daemon.plugins.media-keys home ['']
  org.gnome.settings-daemon.plugins.media-keys home-static ['XF86Explorer']
  org.gnome.settings-daemon.plugins.media-keys increase-text-size ['']
  org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-down ['']
  org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-down-static 
['XF86KbdBrightnessDown']
  org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-toggle ['']
  org.gnome.settings-daemon.plugins.media-keys 
keyboard-brightness-toggle-static ['XF86KbdLightOnOff']
  org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-up ['']
  org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-up-static 
['XF86KbdBrightnessUp']

[Desktop-packages] [Bug 1970401] [NEW] Gnome screen recorder don`t start or not installed on 22.04

You have been subscribed to a public bug:

Problem: Gnome screen recorder dont start. If I use  Ctrl + Alt + Shift + R 
nothing happens.
If I use PrintScrn , screenshot and screen-recorder appears. screenshot works, 
but screen recorder not, only for half a second appear on top bar the red 00:00 
but disappears without recording. 
I thought its problem of zero  screencast-length but its not that, because on 
dconf there is not  
org.gnome.settings-daemon.plugins.media-keys.max-screencast-length 
also on gsettings, for example if I command 
$ gsettings set org.gnome.settings-daemon.plugins.media-keys 
max-screencast-length 300
No such key “max-screencast-length”

It looks to me that screencast is not installed(?) 
or something conflicts? 

system software info:

$ cat /etc/*release* && uname -ar
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS"
PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
UBUNTU_CODENAME=jammy
Linux all1 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux

$ gnome-shell --version
GNOME Shell 42.0

$ gsettings list-recursively | grep org.gnome.shell.keybindings
org.gnome.shell.keybindings focus-active-notification ['n']
org.gnome.shell.keybindings open-application-menu ['F10']
org.gnome.shell.keybindings screenshot ['Print']
org.gnome.shell.keybindings screenshot-window ['Print']
org.gnome.shell.keybindings shift-overview-down ['Down']
org.gnome.shell.keybindings shift-overview-up ['Up']
org.gnome.shell.keybindings show-screen-recording-ui ['R']
org.gnome.shell.keybindings show-screenshot-ui ['Print']
org.gnome.shell.keybindings switch-to-application-1 ['1']
org.gnome.shell.keybindings switch-to-application-2 ['2']
org.gnome.shell.keybindings switch-to-application-3 ['3']
org.gnome.shell.keybindings switch-to-application-4 ['4']
org.gnome.shell.keybindings switch-to-application-5 ['5']
org.gnome.shell.keybindings switch-to-application-6 ['6']
org.gnome.shell.keybindings switch-to-application-7 ['7']
org.gnome.shell.keybindings switch-to-application-8 ['8']
org.gnome.shell.keybindings switch-to-application-9 ['9']
org.gnome.shell.keybindings toggle-application-view ['a']
org.gnome.shell.keybindings toggle-message-tray ['v', 'm']
org.gnome.shell.keybindings toggle-overview ['s']

$ gsettings list-recursively | grep org.gnome.settings-daemon.plugins.media-keys
org.gnome.settings-daemon.plugins.media-keys battery-status ['']
org.gnome.settings-daemon.plugins.media-keys battery-status-static 
['XF86Battery']
org.gnome.settings-daemon.plugins.media-keys calculator ['']
org.gnome.settings-daemon.plugins.media-keys calculator-static 
['XF86Calculator']
org.gnome.settings-daemon.plugins.media-keys control-center ['']
org.gnome.settings-daemon.plugins.media-keys control-center-static ['XF86Tools']
org.gnome.settings-daemon.plugins.media-keys custom-keybindings @as []
org.gnome.settings-daemon.plugins.media-keys decrease-text-size ['']
org.gnome.settings-daemon.plugins.media-keys eject ['']
org.gnome.settings-daemon.plugins.media-keys eject-static ['XF86Eject']
org.gnome.settings-daemon.plugins.media-keys email ['']
org.gnome.settings-daemon.plugins.media-keys email-static ['XF86Mail']
org.gnome.settings-daemon.plugins.media-keys help ['', 'F1']
org.gnome.settings-daemon.plugins.media-keys hibernate ['']
org.gnome.settings-daemon.plugins.media-keys hibernate-static ['XF86Suspend', 
'XF86Hibernate']
org.gnome.settings-daemon.plugins.media-keys home ['']
org.gnome.settings-daemon.plugins.media-keys home-static ['XF86Explorer']
org.gnome.settings-daemon.plugins.media-keys increase-text-size ['']
org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-down ['']
org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-down-static 
['XF86KbdBrightnessDown']
org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-toggle ['']
org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-toggle-static 
['XF86KbdLightOnOff']
org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-up ['']
org.gnome.settings-daemon.plugins.media-keys keyboard-brightness-up-static 
['XF86KbdBrightnessUp']
org.gnome.settings-daemon.plugins.media-keys logout ['Delete']
org.gnome.settings-daemon.plugins.media-keys magnifier ['8']
org.gnome.settings-daemon.plugins.media-keys magnifier-zoom-in 
['equal']
org.gnome.settings-daemon.plugins.media-keys magnifier-zoom-out 
['minus']
org.gnome.settings-daemon.plugins.media-keys media ['']
org.gnome.settings-daemon.plugins.media-keys media-static ['XF86AudioMedia']
org.gnome.settings-daemon.plugins.media-keys mic-mute ['']

[Desktop-packages] [Bug 1952107] Re: Google Contacts API Deprecated