[Desktop-packages] [Bug 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error

[Launchpad Bug Tracker]

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

** Changed in: cups-filters (Ubuntu)
   Status: New => Confirmed

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

Title:
  CUPS fails to print to autodetected printers because of cups-browsed
  error

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  When trying to autodetected IPP printers, print job stays in queue.

  lpstat -l:

  HP_LaserJet_CM1415fn_44A808_-23 erik 30720   So 08 Dez 2019 
15:50:20 CET
  Status: No suitable destination host found by cups-browsed.
  Alarme: resources-are-not-ready
  in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_

  Removing the print job, restarting cups-browsed with `service cups-
  browsed restart` followed by `service cups restart` enables printing
  for one print job; the next one fails again with the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.25.13-1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Dec  8 16:06:02 2019
  InstallationDate: Installed on 2019-10-19 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic 
root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+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 1855595] Re: CUPS fails to print to autodetected printers because of cups-browsed error

[Mark Smith]

Adding some cross-linking to help people who encounter this in the
future, and perhaps also help the devs:

This is discussed in the Ask Ubuntu post:
https://askubuntu.com/questions/1128164/no-suitable-destination-host-
found-by-cups-browsed

The solution there (which worked for me) is to `apt remove cups-browsed`
and add the printer manually.

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

Title:
  CUPS fails to print to autodetected printers because of cups-browsed
  error

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  When trying to autodetected IPP printers, print job stays in queue.

  lpstat -l:

  HP_LaserJet_CM1415fn_44A808_-23 erik 30720   So 08 Dez 2019 
15:50:20 CET
  Status: No suitable destination host found by cups-browsed.
  Alarme: resources-are-not-ready
  in Warteschlange eingereiht für HP_LaserJet_CM1415fn_44A808_

  Removing the print job, restarting cups-browsed with `service cups-
  browsed restart` followed by `service cups restart` enables printing
  for one print job; the next one fails again with the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.25.13-1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Dec  8 16:06:02 2019
  InstallationDate: Installed on 2019-10-19 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/HP_LaserJet_CM1415fn_44A808_.ppd: Permission denied
   grep: /etc/cups/ppd/Samsung_C48x_Series_SEC84251900EE44_.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_utwd0l@/vmlinuz-5.3.0-24-generic 
root=ZFS=rpool/ROOT/ubuntu_utwd0l ro quiet splash vt.handoff=1
  SourcePackage: cups-filters
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1855595/+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 1905370] Re: The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

[lizhiyuan]

Sorry to disturb you, but I found a solution: install TopIcons Plus gnome 
plugin. Plug address: https://extensions.gnome.org/extension/1031/topicons/
I mean the taskbar icon in the upper right corner of the system default. And I 
had misunderstood the log, the log of the previous post has nothing to do with 
this question. :(
But this problem is still strange, because software such as nextcloud, qvray, 
etc. can apply for the tray icon after booting, but there is no way to display 
the icon when booting.
After installing the plug-in, these software can display the icon after 
booting. Is this a problem caused by the gnome api?

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

Title:
  The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1905370/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Enes]

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

Same issue

Kernel : 5.4.0-56-generic
OS : Ubuntu 20.04.1 LTS
Machine : Abra A7 V5.2
Headset : Mi TW Earphones 2 Basic

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1906917] [NEW] 显示应用程序崩溃

[CLT]

Public bug reported:

点击显示应用程序  点击全部   点击文件夹文件夹展开后 关闭文件夹 或者点击文件夹外部。 程序崩溃，而且外部右边的点，无端增多。

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  5 18:59:58 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.10, 5.4.0-57-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
   Subsystem: Lenovo GeForce GT 720M [17aa:3800]
InstallationDate: Installed on 2020-12-03 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20296
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=c7b9132a-4d74-45d2-8be0-fb16c50b7717 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2013
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: 89CN32WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo IdeaPad S410p
dmi.board.vendor: LENOVO
dmi.board.version: FAB3
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S410p
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnLENOVO:bvr89CN32WW:bd11/22/2013:br1.32:efr1.22:svnLENOVO:pn20296:pvrLenovoIdeaPadS410p:rvnLENOVO:rnLenovoIdeaPadS410p:rvrFAB3:cvnLENOVO:ct10:cvrLenovoIdeaPadS410p:
dmi.product.family: IDEAPAD
dmi.product.name: 20296
dmi.product.sku: LENOVO_MT_20296
dmi.product.version: Lenovo IdeaPad S410p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal performance third-party-packages ubuntu

** Patch added: "2020-12-04 09-02-48 的屏幕截图.png"
   
https://bugs.launchpad.net/bugs/1906917/+attachment/5441214/+files/2020-12-04%2009-02-48%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.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/1906917

Title:
  显示应用程序崩溃

Status in xorg package in Ubuntu:
  New

Bug description:
  点击显示应用程序  点击全部   点击文件夹文件夹展开后 关闭文件夹 或者点击文件夹外部。 程序崩溃，而且外部右边的点，无端增多。

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 18:59:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
 Subsystem: Lenovo GeForce GT 720M [17aa:3800]
  InstallationDate: Installed on 2020-12-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20296
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=c7b9132a-4d74-45d2-8be0-fb16c50b7717 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2013
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 89CN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad S410p
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dm

[Desktop-packages] [Bug 1906917] Re: 显示应用程序崩溃

[CLT]

** Attachment added: "2020-12-04 09-02-48 的屏幕截图.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906917/+attachment/5441236/+files/2020-12-04%2009-02-48%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.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/1906917

Title:
  显示应用程序崩溃

Status in xorg package in Ubuntu:
  New

Bug description:
  点击显示应用程序  点击全部   点击文件夹文件夹展开后 关闭文件夹 或者点击文件夹外部。 程序崩溃，而且外部右边的点，无端增多。

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 18:59:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
 Subsystem: Lenovo GeForce GT 720M [17aa:3800]
  InstallationDate: Installed on 2020-12-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20296
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=c7b9132a-4d74-45d2-8be0-fb16c50b7717 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2013
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 89CN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad S410p
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S410p
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr89CN32WW:bd11/22/2013:br1.32:efr1.22:svnLENOVO:pn20296:pvrLenovoIdeaPadS410p:rvnLENOVO:rnLenovoIdeaPadS410p:rvrFAB3:cvnLENOVO:ct10:cvrLenovoIdeaPadS410p:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20296
  dmi.product.sku: LENOVO_MT_20296
  dmi.product.version: Lenovo IdeaPad S410p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906917/+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 1906917] Re: 显示应用程序崩溃

[CLT]

** Attachment added: "2020-12-04 09-02-53 的屏幕截图.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906917/+attachment/5441237/+files/2020-12-04%2009-02-53%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.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/1906917

Title:
  显示应用程序崩溃

Status in xorg package in Ubuntu:
  New

Bug description:
  点击显示应用程序  点击全部   点击文件夹文件夹展开后 关闭文件夹 或者点击文件夹外部。 程序崩溃，而且外部右边的点，无端增多。

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 18:59:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
 Subsystem: Lenovo GeForce GT 720M [17aa:3800]
  InstallationDate: Installed on 2020-12-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20296
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=c7b9132a-4d74-45d2-8be0-fb16c50b7717 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2013
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 89CN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad S410p
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S410p
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr89CN32WW:bd11/22/2013:br1.32:efr1.22:svnLENOVO:pn20296:pvrLenovoIdeaPadS410p:rvnLENOVO:rnLenovoIdeaPadS410p:rvrFAB3:cvnLENOVO:ct10:cvrLenovoIdeaPadS410p:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20296
  dmi.product.sku: LENOVO_MT_20296
  dmi.product.version: Lenovo IdeaPad S410p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906917/+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 1906917] Re: 显示应用程序崩溃

[CLT]

** Attachment added: "2020-12-04 09-02-42 的屏幕截图.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906917/+attachment/5441235/+files/2020-12-04%2009-02-42%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.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/1906917

Title:
  显示应用程序崩溃

Status in xorg package in Ubuntu:
  New

Bug description:
  点击显示应用程序  点击全部   点击文件夹文件夹展开后 关闭文件夹 或者点击文件夹外部。 程序崩溃，而且外部右边的点，无端增多。

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 18:59:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
 Subsystem: Lenovo GeForce GT 720M [17aa:3800]
  InstallationDate: Installed on 2020-12-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20296
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=c7b9132a-4d74-45d2-8be0-fb16c50b7717 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2013
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 89CN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad S410p
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S410p
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr89CN32WW:bd11/22/2013:br1.32:efr1.22:svnLENOVO:pn20296:pvrLenovoIdeaPadS410p:rvnLENOVO:rnLenovoIdeaPadS410p:rvrFAB3:cvnLENOVO:ct10:cvrLenovoIdeaPadS410p:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20296
  dmi.product.sku: LENOVO_MT_20296
  dmi.product.version: Lenovo IdeaPad S410p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906917/+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 1896334] Re: SRU 3.36.6

[Amr Ibrahim]

Please proceed with the gnome-shell SRU, version 3.36.7 is already out
LP: #1903764.

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  SRU 3.36.6

Status in gnome-shell package in Ubuntu:
  In Progress
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Incomplete
Status in yaru-theme source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6

  Since the theme side of the project in ubuntu is shipped via Yaru
  theme, that project is included in the SRU.

  The changes involving yaru here are ONLY gnome-shell upstream changes applied 
to the Yaru sources, as per this we can consider them also part of the GNOME 
release.
  In fact:
  - Ubuntu's GNOME shell uses a Yaru theme based on upstream
gnome-shell This theme basically takes the shell's data/ directory,
applies some diffs and generates a gresource file out of it, that it's
then loaded on startup (in place of the upstream one).
  - GNOME Shell applied some fixes to the theme (se its data/
directory diffs)
  - In order to get those fixes in Ubuntu main session we have to sync
the upstream changes applied to such dir to yaru's src/gnome-shell
path
  - You can easily compare the diffs applied there to match the ones
happening in its upstream counterpart.

  The yaru-theme's `gnome-shell/upstream` directory is just for documentation 
and
  to allow three way merges when updating to new versions of gnome-shell,
  and it is not used for generating the final packages at all

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in popup-grab handling, gdm view fixes,
  lockscreen display changes in some hw, extensions updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+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 1906919] [NEW] Saving a file in gedit crashes desktop to login screen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When saving a file in gedit (or whatever the default text editor is) it
crashes my entire desktop, and I end up on the login screen.

ubuntu 20.10

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

-- 
Saving a file in gedit crashes desktop to login screen
https://bugs.launchpad.net/bugs/1906919
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 1906919] Re: Saving a file in gedit crashes desktop to login screen

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1906919

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: 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/1906919

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906919/+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 1906917] Re: 显示应用程序崩溃

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  显示应用程序崩溃

Status in xorg package in Ubuntu:
  New

Bug description:
  点击显示应用程序  点击全部   点击文件夹文件夹展开后 关闭文件夹 或者点击文件夹外部。 程序崩溃，而且外部右边的点，无端增多。

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 18:59:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.10, 5.4.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
 Subsystem: Lenovo GeForce GT 720M [17aa:3800]
  InstallationDate: Installed on 2020-12-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20296
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=c7b9132a-4d74-45d2-8be0-fb16c50b7717 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2013
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 89CN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo IdeaPad S410p
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB3
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S410p
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvr89CN32WW:bd11/22/2013:br1.32:efr1.22:svnLENOVO:pn20296:pvrLenovoIdeaPadS410p:rvnLENOVO:rnLenovoIdeaPadS410p:rvrFAB3:cvnLENOVO:ct10:cvrLenovoIdeaPadS410p:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20296
  dmi.product.sku: LENOVO_MT_20296
  dmi.product.version: Lenovo IdeaPad S410p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906917/+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 1906919] Re: Saving a file in gedit crashes desktop to login screen

[abcdef]

I tried, but I apparently used the wrong account and now it just refuses
every time.

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906919/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[Jalon Funk]

I was referring to Julian comment which stated df can't ignore this.

If you don't want to this fuse fs to be created then either remove xdg-
desktop-portal package or mask xdg-document-portal.service with:

systemctl --user mask xdg-document-portal.service

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

Title:
  df: /run/user/1000/doc: Operation not permitted

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

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+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 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

[Gunnar Hjalmarsson]

Fixed in appstream 0.13.1-1

** Changed in: appstream (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in GObject Introspection:
  Unknown
Status in appstream package in Ubuntu:
  Fix Released
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1903574/+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 1906449] Re: [nvidia] [amdgpu] Xorg randomly freezes

[Robert Jansen]

Same problem here. Reproducable by switching virtual terminals a few times with 
.
The only thing the system responds to is a ping (but no ssh) and a 
REISUB.
This only happens to me on kernel 5.4.0-56-generic. If I revert to the previous 
kernel, 5.4.0-54-generic, the freeze does not happen.

After every freeze journalctl always shows a SIMD error that seems to cause the 
freeze.
Below are two examples:

dec 03 17:23:05 zen kernel: simd exception:  [#1] SMP NOPTI
dec 03 17:23:05 zen kernel: CPU: 5 PID: 1195 Comm: Xorg Tainted: G   OE 
5.4.0-56-generic #62-Ubuntu
dec 03 17:23:05 zen kernel: Hardware name: Micro-Star International Co., Ltd. 
MS-7C52/B450M-A PRO MAX (MS-7C52), BIOS 3.40 01/22/2020
dec 03 17:23:05 zen kernel: RIP: 
0010:CalculateDelayAfterScaler.constprop.0+0xb2/0x320 [amdgpu]
dec 03 17:23:05 zen kernel: Code: 10 45 b0 f2 45 0f 59 84 24 08 0d 00 00 f2 44 
0f 5e 45 d0 f2 48 0f 2a c8 f2 0f 59 c8 66 0f ef c0 f2 41 0f 5a 84 24 60 17 00 
00  41 0f 5e c8 f2 0f 5c 4d c8 f2 0f 5a c9 e8 7b df f7 ff f2 0f 10
dec 03 17:23:05 zen kernel: RSP: 0018:a135419cf708 EFLAGS: 00010202
dec 03 17:23:05 zen kernel: RAX: 3c00 RBX: 0002 RCX: 

dec 03 17:23:05 zen kernel: RDX: 0001 RSI:  RDI: 
8e2cb16c1f38
dec 03 17:23:05 zen kernel: RBP: a135419cf780 R08: 0002 R09: 
0f00
dec 03 17:23:05 zen kernel: R10: 0001 R11: 8e2cb16c53b8 R12: 
8e2cb16c1f38
dec 03 17:23:05 zen kernel: R13:  R14:  R15: 
0001
dec 03 17:23:05 zen kernel: FS:  7f43ee050a80() 
GS:8e2d6e94() knlGS:
dec 03 17:23:05 zen kernel: CS:  0010 DS:  ES:  CR0: 80050033
dec 03 17:23:05 zen kernel: CR2: 7fc926c8b3e0 CR3: 0007e605 CR4: 
00340ee0
dec 03 17:23:05 zen kernel: Call Trace:

and

dec 04 06:53:51 zen kernel: simd exception:  [#1] SMP NOPTI
dec 04 06:53:51 zen kernel: CPU: 0 PID: 5889 Comm: kworker/0:2 Tainted: G   
OE 5.4.0-56-generic #62-Ubuntu
dec 04 06:53:51 zen kernel: Hardware name: Micro-Star International Co., Ltd. 
MS-7C52/B450M-A PRO MAX (MS-7C52), BIOS 3.40 01/22/2020
dec 04 06:53:51 zen kernel: Workqueue: events console_callback
dec 04 06:53:51 zen kernel: RIP: 
0010:CalculateDelayAfterScaler.constprop.0+0xb2/0x320 [amdgpu]
dec 04 06:53:51 zen kernel: Code: 10 45 b0 f2 45 0f 59 84 24 08 0d 00 00 f2 44 
0f 5e 45 d0 f2 48 0f 2a c8 f2 0f 59 c8 66 0f ef c0 f2 41 0f 5a 84 24 60 17 00 
00  41 0f 5e c8 f2 0f 5c 4d c8 f2 0f 5a c9 e8 7b df f7 ff f2 0f 10
dec 04 06:53:51 zen kernel: RSP: 0018:ad2c42a77618 EFLAGS: 00010202
dec 04 06:53:51 zen kernel: RAX: 0f00 RBX: 0002 RCX: 

dec 04 06:53:51 zen kernel: RDX: 0001 RSI:  RDI: 
9e845b851f38
dec 04 06:53:51 zen kernel: RBP: ad2c42a77690 R08: 0002 R09: 
0f00
dec 04 06:53:51 zen kernel: R10: 0001 R11: 9e845b8553b8 R12: 
9e845b851f38
dec 04 06:53:51 zen kernel: R13:  R14:  R15: 
0001
dec 04 06:53:51 zen kernel: FS:  () 
GS:9e852e80() knlGS:
dec 04 06:53:51 zen kernel: CS:  0010 DS:  ES:  CR0: 80050033
dec 04 06:53:51 zen kernel: CR2: 55d78231afd0 CR3: 000724648000 CR4: 
00340ef0
dec 04 06:53:51 zen kernel: Call Trace:
dec 04 06:53:51 zen kernel:  
dml20v2_ModeSupportAndSystemConfigurationFull+0x403f/0x5d60 [amdgpu]
dec 04 06:53:51 zen kernel:  dml_get_voltage_level+0x127/0x200 [amdgpu]
dec 04 06:53:51 zen kernel:  dcn20_fast_validate_bw+0x376/0xaf0 [amdgpu]
dec 04 06:53:51 zen kernel:  dcn20_validate_bandwidth_internal+0xaf/0x290 
[amdgpu]
dec 04 06:53:51 zen kernel:  ? resource_build_scaling_params+0x709/0x9c0 
[amdgpu]
dec 04 06:53:51 zen kernel:  dcn20_validate_bandwidth+0x31/0x100 [amdgpu]
dec 04 06:53:51 zen kernel:  dc_validate_global_state+0x260/0x2d0 [amdgpu]
dec 04 06:53:51 zen kernel:  ? drm_modeset_lock_all_ctx+0xd9/0xe0 [drm]
dec 04 06:53:51 zen kernel:  amdgpu_dm_atomic_check+0x60c/0x860 [amdgpu]
dec 04 06:53:51 zen kernel:  drm_atomic_check_only+0x2b1/0x450 [drm]
dec 04 06:53:51 zen kernel:  drm_atomic_commit+0x18/0x50 [drm]
dec 04 06:53:51 zen kernel:  drm_client_modeset_commit_atomic+0x1d0/0x1f0 [drm]
dec 04 06:53:51 zen kernel:  drm_client_modeset_commit_force+0x55/0x160 [drm]
dec 04 06:53:51 zen kernel:  drm_fb_helper_pan_display+0xcf/0x230 
[drm_kms_helper]
dec 04 06:53:51 zen kernel:  fb_pan_display+0x8c/0x110
dec 04 06:53:51 zen kernel:  bit_update_start+0x20/0x50
dec 04 06:53:51 zen kernel:  fbcon_switch+0x380/0x550
dec 04 06:53:51 zen kernel:  redraw_screen+0xfe/0x270
dec 04 06:53:51 zen kernel:  complete_change_console+0x3f/0xe0
dec 04 06:53:51 zen kernel:  change_console+0x55/0x90
dec 04 06:53:51 zen kernel:  console_callback+0x178/0x190
dec 04 06:53:51 zen kernel:  ? pwq_dec_

[Desktop-packages] [Bug 1906449] Re: [nvidia] [amdgpu] Xorg randomly freezes

[Kuroš Taheri-Golværzi]

I tried installing nvidia 450 and 455, and on both tries, I get the same
issue. When I try setting the driver settings to use nouveau instead,
the GUI doesn't even load. It's just a black screen (that resembles a
TTY) with the text:

such-and-such / such-and-such blocks
ucsi_acpi usbc000:00: ppm init failed -110

An so then I need to use  to go into the TTY, reinstall
nvidia, and and at least solves *that* problem and I can get back into
the GUI. But then it's the same screen-freeze issue again.

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

Title:
  [nvidia] [amdgpu] Xorg randomly freezes

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xfce4 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Initially, I thought it only happened during file transfers (because
  that's when it happens most often), but I later found that it can
  happen at any time, because I just turned my computer on, went to go
  make a coffee, have a cigarette, and when I came back, the entire
  screen, desktop, system, etc had frozen again. I always need to hold
  the power button down to do an emergency restart, because I can't even
  use Alt+F# to get into the TTY.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .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  440.95.01  Thu May 28 
07:03:08 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Dec  1 12:28:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.95.01, 5.4.0-56-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2020-12-01 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=11577769-570c-4297-a9b2-35fb3a30f6bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  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:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video

[Desktop-packages] [Bug 1873238] Re: Deja-dup icon is missing only runs from terminal

[Vej]

Hello Keith,

Déjà Dup has been moved to a "submenu" called helper programs or the
like (I only have a translated version available so I am not sure about
the exact name here). Try searching for "Backup" that should bring the
icon up.

Please tell us if this fixes the issue or not.

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

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

Title:
  Deja-dup icon is missing only runs from terminal

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  This is occuring just on Ubuntu 20.04 Beta for me.

  The Deja-Dup icon has gone missing from the application's menu.
  Searching for it does not yield any results via the gnome shell
  search.

  It will run if I open a terminal and type "deja-dup"

  While running from the terminal instead of the description in the top
  bar/panel being the expected "Backups" the description now reads
  "Org.gnome.DejaDup"

  All other functionality seems to work as normal when run from
  terminal.

  I have tried uninstalling and reinstalling via synaptic and the Ubuntu
  Software but the issue is persisting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.6-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 10:59:36 2020
  InstallationDate: Installed on 2019-10-20 (178 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to focal on 2020-04-06 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1873238/+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 1873238] Re: Deja-dup icon is missing only runs from terminal

[Michael Terry]

I think the English word used is Utilities

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

Title:
  Deja-dup icon is missing only runs from terminal

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  This is occuring just on Ubuntu 20.04 Beta for me.

  The Deja-Dup icon has gone missing from the application's menu.
  Searching for it does not yield any results via the gnome shell
  search.

  It will run if I open a terminal and type "deja-dup"

  While running from the terminal instead of the description in the top
  bar/panel being the expected "Backups" the description now reads
  "Org.gnome.DejaDup"

  All other functionality seems to work as normal when run from
  terminal.

  I have tried uninstalling and reinstalling via synaptic and the Ubuntu
  Software but the issue is persisting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.6-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 10:59:36 2020
  InstallationDate: Installed on 2019-10-20 (178 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to focal on 2020-04-06 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1873238/+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 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

[Matthias Klumpp]

Not really fixed, AppStream has an incomplete workaround for the
gobject-introspection bug (which may break at any time for new functions
in either Python or Vala, if we aren't super careful).

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in GObject Introspection:
  Unknown
Status in appstream package in Ubuntu:
  Fix Released
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1903574/+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 1906945] [NEW] package texlive-base 2019.20200218-1 failed to install/upgrade: Versuch, »/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf« zu überschreiben, welches auch in P

[Maike Fischer]

Public bug reported:

no further information

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: texlive-base 2019.20200218-1
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Dec  5 17:35:59 2020
ErrorMessage: Versuch, »/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf« zu 
überschreiben, welches auch in Paket texlive-plain-generic 2017.20180305-2 ist
InstallationDate: Installed on 2019-08-09 (483 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: texlive-base
Title: package texlive-base 2019.20200218-1 failed to install/upgrade: Versuch, 
»/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf« zu überschreiben, welches 
auch in Paket texlive-plain-generic 2017.20180305-2 ist
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package texlive-base 2019.20200218-1 failed to install/upgrade:
  Versuch, »/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf« zu
  überschreiben, welches auch in Paket texlive-plain-generic
  2017.20180305-2 ist

Status in texlive-base package in Ubuntu:
  New

Bug description:
  no further information

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: texlive-base 2019.20200218-1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Dec  5 17:35:59 2020
  ErrorMessage: Versuch, »/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf« 
zu überschreiben, welches auch in Paket texlive-plain-generic 2017.20180305-2 
ist
  InstallationDate: Installed on 2019-08-09 (483 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: texlive-base
  Title: package texlive-base 2019.20200218-1 failed to install/upgrade: 
Versuch, »/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf« zu überschreiben, 
welches auch in Paket texlive-plain-generic 2017.20180305-2 ist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1906945/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[Gordon Lack]

> If you don't want to this fuse fs to be created

I probably don't, but have no idea want it actually does.

> then either remove xdg-desktop-portal package or mask xdg-document-
portal.service with:

Thanks. The masking worked fine.

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

Title:
  df: /run/user/1000/doc: Operation not permitted

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

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Nikke]

It seems that on Ubuntu 20.10 it is fixed by installing pulseaudio-
modules-bt (which also uninstalls pulseaudio-module-bluetooth) from this
ppa: https://launchpad.net/~berglh/+archive/ubuntu/pulseaudio-a2dp

Then: 
> sudo systemctl restart pulseaudio
> pulseaudio -k

Did just a few tests with Google Duo with my Jabra Elite Active 65t
buds, and the sound is a LOT better both on my and the other end!

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

[Gunnar Hjalmarsson]

Ok, Matthias, added a gobject-introspection bug task.

** Also affects: gobject-introspection (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gobject-introspection (Ubuntu)
   Status: New => Confirmed

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

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in GObject Introspection:
  Unknown
Status in appstream package in Ubuntu:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Confirmed
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1903574/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[Julian Andres Klode]

> I probably don't, but have no idea want it actually does.

It provides safe access to files on your disk to snaps or flatpaks.

> You can silence this with "df -x fuse.portal"

Odd, when I tried it didn't work for me, maybe I made a typo.

Added a task for coreutils - we should ignore fuse.portal in any case,
regardless of whether the portal code gets fixed or not, because it's
not a real file system that has an actual size.

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

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

Title:
  df: /run/user/1000/doc: Operation not permitted

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

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1766230] Re: Strange window matching behaviour between Slack and Chrome

[Daniel Tharp]

Seeing the same on a fresh 20.04.1 install with snap Slack and deb
Vivaldi (chromium-based). However, if I close Slack and Vivaldi both,
and reopen Vivaldi (`ps aux | grep slack` is empty), it shows up under
the Slack context anyway.

Actual usability is not impacted, just a confusing user experience.

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

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[Julian Andres Klode]

** Changed in: coreutils (Ubuntu)
   Status: New => In Progress

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

Title:
  df: /run/user/1000/doc: Operation not permitted

Status in coreutils package in Ubuntu:
  In Progress
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Mike Boruta]

Hello Coiby,

Hmm, as far as I can tell the proper module is being used since I
executed the same steps for both the 5.7.19 and 5.8 kernels. I also
confirmed this by running `modinfo pinctrl_amd` and verifying that it is
no longer signed. I understand what you are saying regarding 0x51bc8,
maybe a different code path is being executed? Perhaps it would be best
for someone to independently confirm this before digging in further; I
have run through these steps a few times so I don't think I made a silly
mistake but anything is possible.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassi

[Desktop-packages] [Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted

[Julian Andres Klode]

Just to note, a huge number of other file systems don't show:

$ grep fuse /proc/mounts 
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0
https://sd2dav.1und1.de/ /media/jak/smartdrive fuse 
rw,nosuid,nodev,noexec,relatime,user_id=1000,group_id=1000,allow_other,max_read=16384
 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse 
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
portal /run/user/1000/doc fuse.portal 
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
keybase-redirector /keybase fuse 
ro,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/fuse /run/user/1000/keybase/kbfs fuse 
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
$ /usr/bin/df  -T | grep fuse
/usr/bin/df: /run/user/1000/doc: Operation not permitted
https://sd2dav.1und1.de/  fuse  12 8 53332  61% 
/media/jak/smartdrive
/dev/fuse fuse   262144000 1 262144000   1% 
/run/user/1000/keybase/kbfs

Looking at some of them:

$ stat -f /keybase/
  File: "/keybase/"
ID: 0Namelen: 0   Type: fuseblk
Block size: 0  Fundamental block size: 0
Blocks: Total: 0  Free: 0  Available: 0
Inodes: Total: 0  Free: 0

$ stat -f /run/user/1000/gvfs
  File: "/run/user/1000/gvfs"
ID: 0Namelen: 1024Type: fuseblk
Block size: 4096   Fundamental block size: 4096
Blocks: Total: 0  Free: 0  Available: 0
Inodes: Total: 0  Free: 0

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

Title:
  df: /run/user/1000/doc: Operation not permitted

Status in coreutils package in Ubuntu:
  In Progress
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  /run/user/1000/doc is a fuse.portal mount point, but statfs() return
  EPERM, hence df produces an error message. Maybe statfs() is not
  implemented, but it would be good to quieten this down (df even does
  not allow me to ignore it, probably because it looks at statfs to find
  out fs type, so my fs type ignoring doesn't work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1662244] Re: lightdm causes all greeters to fail to start

[Christophe Chisogne]

Upgrading to (K)Ubuntu 18.04.5 LTS basically broke the system as X was
not restarting correctly (black screen instead of lightdm display or
even infinite loop of X crashes based on BIOS/EFI config).

This is critical for non-savvy users as my parents.

The issue is the same as can be seen in
/var/log/lightdm/seat0-greeter.log with repeated messages like

**MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes 
(alignment: 2048)...
**MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes 
(alignment: 2048)...
**MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes 
(alignment: 2048)...

The workaround is indded updating the memlock limits as described above
(adding the 2 lines of the above comment to /etc/security/limits.con).

Thanks for the workaround :)

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

Title:
  lightdm causes all greeters to fail to start

Status in Light Display Manager:
  Invalid
Status in LightDM GTK+ Greeter:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  lightdm is failing to start. Best guess is because of unity-session-
  manager. This is from .xsession-errors.

  dbus-update-activation-environment: setting 
_=/usr/bin/dbus-update-activation-environment
  upstart: click-user-hooks main process (4028) terminated with status 1
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon main process ended, respawning
  upstart: unity-settings-daemon respawning too fast, stopped
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application main process ended, respawning
  upstart: indicator-application respawning too fast, stopped
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03a00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x03c00084 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  xbrlapi: window 0x0484 changed to NULL name
  upstart: dbus main process (4023) killed by TERM signal

  
  I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've 
reverted kernel versions and that didn't work. I've moved aside $HOME/.cache 
and that didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Feb  6 10:21:29 2017
  InstallationDate: Installed on 2015-07-20 (566 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1662244/+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 1292398] Re: Second screen position isn't saved from one session to another

[Nemanja V]

On Ubuntu 19.10 I'm experiencing the same thing as the comment above:

###
Jan B (hey-e) wrote on 2015-04-08: #143
I have a laptop and a monitor as secondary display
...
Every time I switch back from only using the monitor (laptop display disabled) 
to using the laptop display as a second screen – I need to rearrange the 
displays. By default they are side-by-side but I always want the monitor above 
the laptop display.
###

I don't have Ubuntu 20.x installed at the moment to confirm whether it
happens there, too.

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Mutter:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1906919] Re: Saving a file in gedit crashes desktop to login screen

[abcdef]

apport information

** Tags added: apport-collected groovy wayland-session

** Description changed:

  When saving a file in gedit (or whatever the default text editor is) it
  crashes my entire desktop, and I end up on the login screen.
  
  ubuntu 20.10
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: sddm
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-10-30 (36 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ NonfreeKernelModules: wl
+ Package: gnome-shell 3.38.1-1ubuntu1.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
+ RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
+ Tags:  wayland-session groovy
+ Uname: Linux 5.8.0-31-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/1906919/+attachment/5441352/+files/Dependencies.txt

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-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/1906919/+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 1906919] ShellJournal.txt

[abcdef]

apport information

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

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-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/1906919/+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 1906919] ProcCpuinfoMinimal.txt

[abcdef]

apport information

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

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-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/1906919/+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 1906919] monitors.xml.txt

[abcdef]

apport information

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

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-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/1906919/+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 1906919] GsettingsChanges.txt

[abcdef]

apport information

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

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

Title:
  Saving a file in gedit crashes desktop to login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When saving a file in gedit (or whatever the default text editor is)
  it crashes my entire desktop, and I end up on the login screen.

  ubuntu 20.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: sddm
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-30 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.38.1-1ubuntu1.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  Tags:  wayland-session groovy
  Uname: Linux 5.8.0-31-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/1906919/+subscriptions

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

Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Coiby Xu]

Hi Mike,

On Sat, Dec 05, 2020 at 09:09:35PM -, Mike Boruta wrote:
>Hello Coiby,
>
>Hmm, as far as I can tell the proper module is being used since I
>executed the same steps for both the 5.7.19 and 5.8 kernels. I also
>confirmed this by running `modinfo pinctrl_amd` and verifying that it is
>no longer signed. I understand what you are saying regarding 0x51bc8,
>maybe a different code path is being executed? Perhaps it would be best
>for someone to independently confirm this before digging in further; I
>have run through these steps a few times so I don't think I made a silly
>mistake but anything is possible.

Could you insert some pr_alert code to verify the updated module has
been loaded?

pr_alert("amd_gpio reg_val=%x, pin=%lu (LEVEL_LOW)",
pin_reg, d->hwirq);

You can also use the repo
https://github.com/coiby/standalone_pinctrl_amd/tree/debug_for_Mike.

And after the system getting rebooted, paste the result of `journalctl
-k|grep amd_gpio` here?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   lin

[Desktop-packages] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

[Tim Wetzel]

Another wrinkle since this week's kernel update in 20.04.1 (from
5.4.0.54.57 to 5.4.0.56.59: on every second or third startup in the
UltraDock and with the external HDMI display as primary (which is where
this suspend on login password problem occurs), the system now goes into
never-never land instead of suspending. The external display stays
active (doesn't go into power standby) but remains black; if I open the
lid of the docked laptop it also usually remains black; the soft reboot
(Alt+Prtscrn followed by REISUB) does nothing; so the only option is a
hard power down.

Wait 10-15 seconds and restart, and it's back to the usual suspend on
entry of the login password.

Please fix again, this bug affects every Ubuntu system here. All
20.04 and ThinkPads from T440 through T480 series; so older to
practically new.

Thanks.

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

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04's software updater just applied quite a few updates
  affecting grub and nvidia. The modules should show in the report just
  submitted. Also, updates to initramfs had just installed a few days
  ago. Kudos in that these updates fixed two login/startup issues: I'd
  been affected by the compression change for initramfs and had started
  getting the spinning ubuntu circle on the logon splash screen,
  apparently due to an nvidia driver conflict. I'd turned the splash
  screen to nosplash, and have now been able to set it back to splash.
  Both of those issues now appear to be fixed.

  BUT now when I start Ubuntu with the T570 laptop docked, lid closed,
  external display and keyboard via the dock: as soon as I enter the
  login password and press enter, the system goes into suspend. If I
  then press the dock power button again, the system will resume and
  proceed normally.

  It seems that the new startup modules don't realize that the machine
  is docked; and/or that it erroneously now "detects" the closed lid as
  a change in lid state during startup, triggering suspend. Prior to
  today's updates, this was not an issue.

  I would appreciate seeing this corrected. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 24 18:15:31 2020
  InstallationDate: Installed on 2020-06-22 (94 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Logan]

I can confirm Mike's result.  However, I'm on Fedora 33 and kernel
5.8.15.

[root@lappy-the-laptop ~]#  dmesg | grep -i amd_g
[root@lappy-the-laptop ~]# journalctl -k | grep -i amd_gpio
[root@lappy-the-laptop ~]# modinfo pinctrl-amd 
filename:   
/lib/modules/5.8.15-301.fc33.x86_64/kernel/drivers/pinctrl/pinctrl-amd.ko.xz
description:AMD GPIO pinctrl driver
author: Ken Xue , Jeff Wu 
license:GPL v2
alias:  acpi*:AMDI0030:*
alias:  acpi*:AMD0030:*
depends:
retpoline:  Y
name:   pinctrl_amd
vermagic:   5.8.15-301.fc33.x86_64 SMP mod_unload 
[root@lappy-the-laptop ~]# uname -r
5.8.15-301.fc33.x86_64

The pinctrl module I'm using is from the github repo

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19W

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Logan]

The output Coiby requested
[root@lappy-the-laptop ~]# journalctl -k | grep -i amd_
Dec 05 15:55:13 lappy-the-laptop kernel: amd_uncore: AMD NB counters detected
Dec 05 15:55:13 lappy-the-laptop kernel: amd_uncore: AMD LLC counters detected
Dec 05 15:55:13 lappy-the-laptop kernel: amd_gpio reg_val=500e8, pin=130 
(before set_type)
Dec 05 15:55:13 lappy-the-laptop kernel: amd_gpio reg_val=50388, pin=130 
(LEVEL_LOW)
Dec 05 15:55:13 lappy-the-laptop kernel: amd_gpio reg_val=503c8, pin=130 
(before set_type)
Dec 05 15:55:13 lappy-the-laptop kernel: amd_gpio reg_val=50388, pin=130 
(LEVEL_LOW)

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709

[Desktop-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)

[Bryan J Smalley]

I think I was supposed to mark each item in the affects column as
confirmed, but I neglected to do that on 'linux (ubuntu)'.  I've now
marked that as confirmed as well.  Apologies if this was not what I was
supposed to do.  Thanks again to all!

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[16