[Desktop-packages] [Bug 1891733] Re: Support better Arabic font

[Gunnar Hjalmarsson]

** Also affects: ubuntu-translations/focal
   Importance: Undecided
   Status: New

** Also affects: ubuntu-translations/groovy
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-translations/groovy

** Project changed: ubuntu-translations => ubuntu-seeds

** No longer affects: ubuntu-translations/focal

** Also affects: language-selector (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: language-selector (Ubuntu Groovy)
   Importance: Undecided => Wishlist

** Changed in: language-selector (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: language-selector (Ubuntu Groovy)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: language-selector (Ubuntu Focal)
   Importance: Undecided => Wishlist

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

Title:
  Support better Arabic font

Status in Ubuntu Seeds:
  New
Status in language-selector package in Ubuntu:
  In Progress
Status in language-selector source package in Focal:
  New
Status in language-selector source package in Groovy:
  In Progress

Bug description:
  As per the  discussion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1891733/+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 1891733] [NEW] Support better Arabic font

[Gunnar Hjalmarsson]

Public bug reported:

As per the  discussion.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-docs
   Importance: Undecided
   Status: New

** Project changed: ubuntu-docs => ubuntu-translations

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

Title:
  Support better Arabic font

Status in Ubuntu Translations:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  As per the  discussion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1891733/+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 1245534] Re: gnome archive manager incorrect handling of jar repositories

[Launchpad Bug Tracker]

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

** Changed in: file-roller (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gnome archive manager incorrect handling of jar repositories

Status in file-roller package in Ubuntu:
  Expired

Bug description:
  I found out archive manager deals incorrectly with jar archives, by
  incorrectly I found out these two bugs:

  1. archive manager permits duplicate jar files while a jar with a duplicate 
file returns the error: duplicate entry: some/class.class
  2. if you open two jar files and copy a folder with many class files into the 
other jar, some files won't get copied.

  I realize the above is a little too generic however I have a simple
  way to reproduce the error: download the jgroups jar library from
  sourceforge (jgroups-3.3.0.Alpha2.jar), extract the jar file into a
  folder, recompress the jar file into a new jar file
  jgroups-3.3.0.Alpha2_new.jar now do a md5sum of the two files and they
  will be different.

  If you analyze the two archives file per file you'll see gnome
  archiver will have missed some files and duplicated some others.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1245534/+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 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-440 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

Status in nvidia-graphics-drivers package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9

  ---

  I observed the following on Eoan as well with nvidia drivers older
  than 440.

  1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
  QXL + SPICE:

  
    
    
  
  
    
    
  

  2) When a host is booted with `prime-select intel` observing guest
  video output works fine with both virt-viewer (over SPICE) and remmina
  (over RDP);

  3) With `prime-select nvidia` Xorg crashes as described in
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1)
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 13 20:16:07 2020
  DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   nvidia, 440.59, 5.4.0-12-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1579009393
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755]
  InstallationDate: Installed on 2018-05-13 (641 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Razer Blade
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcCwd: /home/dima
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ 
button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   System ()
   ()
   ()
   ()
    () at /lib/x86_64-linux-gnu/libpthread.so.0
  Title: Xorg crashed with SIGABRT in System()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 4.02
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.sku: RZ09-01953E72
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  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 

[Desktop-packages] [Bug 1767505] Re: Rhythmbox Radio - Internal Data Stream Error

[Launchpad Bug Tracker]

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

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

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

Title:
  Rhythmbox Radio - Internal Data Stream Error

Status in rhythmbox package in Ubuntu:
  Expired

Bug description:
  When trying to play any radio station, I get a dialog that states
  after about 20 seconds of playing:

  Couldn't start playback

  Internal data stream error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1767505/+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 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

Status in nvidia-graphics-drivers package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9

  ---

  I observed the following on Eoan as well with nvidia drivers older
  than 440.

  1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
  QXL + SPICE:

  
    
    
  
  
    
    
  

  2) When a host is booted with `prime-select intel` observing guest
  video output works fine with both virt-viewer (over SPICE) and remmina
  (over RDP);

  3) With `prime-select nvidia` Xorg crashes as described in
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1)
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 13 20:16:07 2020
  DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   nvidia, 440.59, 5.4.0-12-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1579009393
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755]
  InstallationDate: Installed on 2018-05-13 (641 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Razer Blade
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcCwd: /home/dima
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ 
button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   System ()
   ()
   ()
   ()
    () at /lib/x86_64-linux-gnu/libpthread.so.0
  Title: Xorg crashed with SIGABRT in System()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 4.02
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.sku: RZ09-01953E72
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  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+git20190815-1
  

[Desktop-packages] [Bug 1883580] Re: [modeset+nvidia] frame drop issue

[Launchpad Bug Tracker]

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

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

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

Title:
  [modeset+nvidia] frame drop issue

Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  i have severe graphical drop frames however my hardware is nvidia gtx
  850 4 gigs and intel graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-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.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun 15 21:30:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd]
  InstallationDate: Installed on 2020-06-10 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. N550JK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=ebd465fe-6414-4b7d-a0c0-ec4fdbd2aaa5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JK.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JK
  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.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  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.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-shell/+bug/1883580/+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 1883580] Re: [modeset+nvidia] frame drop issue

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [modeset+nvidia] frame drop issue

Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  i have severe graphical drop frames however my hardware is nvidia gtx
  850 4 gigs and intel graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-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.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun 15 21:30:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd]
  InstallationDate: Installed on 2020-06-10 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. N550JK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=ebd465fe-6414-4b7d-a0c0-ec4fdbd2aaa5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JK.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JK
  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.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  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.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-shell/+bug/1883580/+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 1883393] Re: Calendar events from time zone different from local time displayed wrongly

[Launchpad Bug Tracker]

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

** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Calendar events from time zone different from local time displayed
  wrongly

Status in gnome-calendar package in Ubuntu:
  Expired

Bug description:
  Events from time zones other than the local one are displayed wrongly:
  The clock time shows the correct local time, but in week view, the
  event is drawn at the time of the other time zone.

  This greatly disturbs the layout and leads to events being drawn
  overlapped.

  Effect was showing with a Google calendar.

  To reproduce:

  - Subscribe to a Google calendar.
  - In that Google calendar, create an event in a time zone with some hours 
difference to your time zone.
  - Watch the event appear in the calendar at the wrong position.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1883393/+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 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)

Status in nvidia-graphics-drivers package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9

  ---

  I observed the following on Eoan as well with nvidia drivers older
  than 440.

  1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
  QXL + SPICE:

  
    
    
  
  
    
    
  

  2) When a host is booted with `prime-select intel` observing guest
  video output works fine with both virt-viewer (over SPICE) and remmina
  (over RDP);

  3) With `prime-select nvidia` Xorg crashes as described in
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1)
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 13 20:16:07 2020
  DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   nvidia, 440.59, 5.4.0-12-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1579009393
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755]
  InstallationDate: Installed on 2018-05-13 (641 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Razer Blade
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcCwd: /home/dima
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ 
button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   System ()
   ()
   ()
   ()
    () at /lib/x86_64-linux-gnu/libpthread.so.0
  Title: Xorg crashed with SIGABRT in System()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 4.02
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.sku: RZ09-01953E72
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  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+git20190815-1
  

[Desktop-packages] [Bug 1883456] Re: Video lag while in Discord

[Launchpad Bug Tracker]

[Expired for gnome-shell-extension-appindicator (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Video lag while in Discord

Status in gnome-shell package in Ubuntu:
  Expired
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Expired

Bug description:
  Installed the newest update and restarted the computer. Since then,
  every video is freezing every 10 seconds for like 1 second. Youtube,
  vlc as examples. But it's not a performance problem. CPU and RAM usage
  stay low during this lag. I'm a noob, sry for my eventually bad
  description.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 14 22:50:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5051]
  InstallationDate: Installed on 2020-06-06 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20FU001RMZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=469e2bc9-c16c-49fe-9b3c-7ddf2ec744f0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 02/04/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R08ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FU001RMZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET35W(1.09):bd02/04/2016:svnLENOVO:pn20FU001RMZ:pvrThinkPadL460:rvnLENOVO:rn20FU001RMZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L460
  dmi.product.name: 20FU001RMZ
  dmi.product.sku: LENOVO_MT_20FU_BU_Think_FM_ThinkPad L460
  dmi.product.version: ThinkPad L460
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-shell/+bug/1883456/+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 1883456] Re: Video lag while in Discord

[Launchpad Bug Tracker]

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

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

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

Title:
  Video lag while in Discord

Status in gnome-shell package in Ubuntu:
  Expired
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Expired

Bug description:
  Installed the newest update and restarted the computer. Since then,
  every video is freezing every 10 seconds for like 1 second. Youtube,
  vlc as examples. But it's not a performance problem. CPU and RAM usage
  stay low during this lag. I'm a noob, sry for my eventually bad
  description.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 14 22:50:31 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5051]
  InstallationDate: Installed on 2020-06-06 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20FU001RMZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=469e2bc9-c16c-49fe-9b3c-7ddf2ec744f0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 02/04/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R08ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FU001RMZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET35W(1.09):bd02/04/2016:svnLENOVO:pn20FU001RMZ:pvrThinkPadL460:rvnLENOVO:rn20FU001RMZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L460
  dmi.product.name: 20FU001RMZ
  dmi.product.sku: LENOVO_MT_20FU_BU_Think_FM_ThinkPad L460
  dmi.product.version: ThinkPad L460
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-shell/+bug/1883456/+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 1883596] Re: Gnome-shell acting very poorly under stress

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome-shell acting very poorly under stress

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  How to reproduce:
  * in Gnome-shell, starts VLC.  Drag and drop a .str file into VLC (without 
providing it any video file).
  * A bug in VLC will make it use 100% CPU for quite a long time.
  * Meanwhile, in a terminal, type “top”.
  * Gnome-shell will appear as one of the programs taking a lot of resources.
  * Shortly after, the whole Gnome-shell will freeze and no longer respond.  
This is a stressful situation for the user: not only is the computer burning 
hot, but the window manager is no longer responding.
  * Ctrl+Alt+F3 to open a TTY, kill -9 
  * Gnome-shell restarts, enabling you to interact with the windows, but 
shortly afterwards, everything will freeze again.

  In this situation, the system is under huge stress because of VLC.
  However, this should not be an excuse to let the whole system stop
  responding altogether.  There is clearly an issue in VLC here, but
  this kind of gnome-shell freeze appears with a variety of system-
  stresses on my computer, not just VLC.  It may be that VLC is causing
  a lot of system calls that are caught by Gnome-shell?  I am not sure
  what exactly is happening.

  I am not sure even whether this is really an issue with Gnome-shell:
  it may be an issue with its parent process, or whatever.

  System stress is not an ideal situation, and I fully understand that
  it can be difficult to deal with.  I just feel that Gnome-shell could
  handle it slightly better.

  I would understand that this bug report might be too subjective and be
  marked as invalid.  Anyway, I just wanted to share my frustration.  If
  I can help in any way, please tell me how ☺

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-1081.91-oem 4.15.18
  Uname: Linux 4.15.0-1081-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 20:51:24 2020
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-28 (291 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883596/+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 1876991] Re: Touchpad started appearing both as a touchpad and as a mouse input devices after upgrade to 20.04

[Jerome Droniou]

I have a very similar problem with the touchscreen not working (most of
the time) on my DELL Latitude 7400 2-in-1, except that when it does not
work, it does not even work on the login screen. Closing the lid or
restarting does not help. Then, from time to time, the screen works
again...

My touchpad is also recognised as both mouse and touchpad, but that does
not prevent it from working properly. The problem is solely with the
touchscreen, which is simply unreactive (most of the time) although it
does properly appear in xinput:


Virtual core pointerid=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ DELL08AF:00 044E:1225 Mouse   id=13   [slave  pointer  (2)]
⎜   ↳ DELL08AF:00 044E:1225 Touchpadid=14   [slave  pointer  (2)]
⎜   ↳ PS/2 Generic Mouseid=20   [slave  pointer  (2)]
⎜   ↳ Wacom HID 48CA Finger touch   id=12   [slave  pointer  (2)]
⎜   ↳ Wacom HID 48CA Pen stylus id=11   [slave  pointer  (2)]
⎜   ↳ Wacom HID 48CA Pen eraser id=21   [slave  pointer  (2)]

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

Title:
  Touchpad started appearing both as a touchpad and as a mouse input
  devices after upgrade to 20.04

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  It was working perfectly on 18.04 with 5.3 kernel but after upgrade to
  20.04 it's becoming disabled because there is a "mouse" attached which
  is the same touchpad detected incorrectly, xinput --list showing both

  ⎜   ↳ MSFT0001:00 06CB:7E7E Mouse   id=11   [slave  pointer  (2)]
  ⎜   ↳ MSFT0001:00 06CB:7E7E Touchpadid=12   [slave  pointer  (2)]

  The first line was definitely not present before, I know it because I
  use it when in openbox session.

  There is also a number of questions on AskUbuntu that look like results of 
the same problem at first glance:
  https://askubuntu.com/q/1231873/20275
  https://askubuntu.com/q/1235067/20275
  https://askubuntu.com/q/1234975/20275

  and two global search results for the same touchpad model ("MSFT0001:00 
06CB:7E7E Mouse") that show the same problem in unrelated contexts:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953405
  https://bbs.archlinux.org/viewtopic.php?id=240723

  I also have these errors in kernel log, may be related, weren't present 
previously:
  psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
  psmouse serio1: Failed to enable mouse on isa0060/serio1
  psmouse serio1: Failed to disable mouse on isa0060/serio1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed May  6 00:09:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 5471
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ocz-root ro quiet libata.force=1.00:noncq 
resume=/dev/mapper/ocz-swap_1 crashkernel=384M-2G:128M,2G-:256M
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 05F5VX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: Zahoriya
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd07/25/2018:svnDellInc.:pnVostro5471:pvr:rvnDellInc.:rn05F5VX:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5471
  dmi.product.sku: 0830
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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:

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Willy Nolan]

Daniel van Vugt: @vanvugt: 
It is safe to say that, when using Nvidia drivers, the fractional scaling is 
completely broken.

- You can't set the scale differently on different monitors (basic 
functionality)
- The fractional scaling doesn't work at all (even if you set it to be the same 
for both or multiple monitors)

There are several (almost 50) different hardware configurations having
this issue and there are several "workarounds" all of which have their
own issues.

This is an extremely basic functionality and something that is needed as
I have read that *the most common* way to work right now is a laptop
with one external display.  If using Nvidia drivers, that setup does not
work.

Can you tell me how to get involved or what I can do to get this
working? It has been several months and I'd like to solve this problem.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  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-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1889322] Re: nvidia gforce

[Seth Arnold]

Hello snapd folks, this package logged over a thousand DENIED messages
in about ten minutes. This can't be good for system responsiveness,
battery life, drive health, filesystem free space, etc.

Thanks

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

Title:
  nvidia gforce

Status in snapd package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  fonctionne  a ne pas se connecter pour mise a jour

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Jul 28 19:52:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710] 
[19da:7326]
  InstallationDate: Installed on 2020-07-25 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   PATH=(custom, no user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=08d4bac1-d829-450c-ae55-3b06a793cd85 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/23/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-GR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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
  xserver.bootTime: Tue Jul 28 18:36:06 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputEee PC WMI hotkeys   KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1889322/+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 1889322] Re: nvidia gforce

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  nvidia gforce

Status in snapd package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  fonctionne  a ne pas se connecter pour mise a jour

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Jul 28 19:52:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710] 
[19da:7326]
  InstallationDate: Installed on 2020-07-25 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   PATH=(custom, no user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=08d4bac1-d829-450c-ae55-3b06a793cd85 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-G R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/23/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-GR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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
  xserver.bootTime: Tue Jul 28 18:36:06 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputEee PC WMI hotkeys   KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1889322/+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 1889373] Re: Mozilla Firefox 78.x ESR Multiple Vulnerabilities

[Seth Arnold]

Hello, Ubuntu doesn't ship the ESR Firefox. We addressed these issues
in: https://ubuntu.com/security/notices/USN-4443-1

Thanks

** Information type changed from Private Security to Public Security

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

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

Title:
  Mozilla Firefox 78.x ESR Multiple Vulnerabilities

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Hi Ubuntu Team,

  Ubuntu 18 is affected by the following vulnerabilities.

  Multiple vulnerabilities have been reported in Mozilla Firefox ESR,
  which can be exploited by malicious people to conduct spoofing
  attacks, disclose sensitive information, bypass certain security
  restrictions, and compromise a vulnerable system.

  Reference: https://www.mozilla.org/en-
  US/security/advisories/mfsa2020-32

  Solution: Update to version 78.1.

  Further info: Please also note that also Firefox 68.x versions are
  affected by some vulnerabilities (see https://www.mozilla.org/en-
  US/security/advisories/mfsa2020-31/), but I do not know if they are
  used in any version of Ubuntu.

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1889373/+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 1889927] Re: [HP EliteBook 840 G3, Conexant CX20724, Speaker, Internal] No sound at all , no sound from internal speaker but using a headset there is

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  [HP EliteBook 840 G3, Conexant CX20724, Speaker, Internal] No sound at
  all , no sound from internal speaker but using a headset there is

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Fresh installation
  No sound
  There is sound via the headset

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lamis  8934 F pulseaudio
   /dev/snd/pcmC0D0c:   lamis  8934 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lamis  8934 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 31 21:04:09 2020
  InstallationDate: Installed on 2020-07-26 (5 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1144 F pulseaudio
lamis  8934 F pulseaudio
   /dev/snd/pcmC0D0c:   lamis  8934 F...m pulseaudio
   /dev/snd/pcmC0D0p:   lamis  8934 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G3, Conexant CX20724, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.09
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.09:bd07/05/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6A:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: L3C65AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-07-31T20:55:08.699674

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889927/+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 1891725] [NEW] Cannot log in xorg, wayland works fine

[Mehant Kumar]

Public bug reported:

stuck on login loop on ubuntu xorg ,but wayland works fine

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 15 06:50:39 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:17e1]
InstallationDate: Installed on 2020-08-14 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X412FA_X412FA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ec70f2f9-cfb4-4af6-9a61-2573df2b0483 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X412FA.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X412FA
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.:bvrX412FA.304:bd08/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX412FA_X412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X412FA_X412FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ubuntu wayland-session

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

Title:
  Cannot log in xorg, wayland works fine

Status in xorg package in Ubuntu:
  New

Bug description:
  stuck on login loop on ubuntu xorg ,but wayland works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 15 06:50:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) 
[1043:17e1]
  InstallationDate: Installed on 2020-08-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X412FA_X412FA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=ec70f2f9-cfb4-4af6-9a61-2573df2b0483 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X412FA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X412FA
  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.:bvrX412FA.304:bd08/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX412FA_X412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X412FA_X412FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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
  

[Desktop-packages] [Bug 1890012] Re: Could not install 'systemd-shim'

[Seth Arnold]

Hello Andreas, this bug is filed against xorg, but the text description
looks like systemd-shim was involved.

Should this be an xorg bug or a systemd-shim bug? Or something else?

Thanks

** Information type changed from Private Security to Public

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

Title:
  Could not install 'systemd-shim'

Status in xorg package in Ubuntu:
  New

Bug description:
  The upgrade will continue but the 'systemd-shim' package may not be in
  a working state. Please consider submitting a bug report about it.

  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  
  Could not install the upgrades

  
  The upgrade has aborted. Your system could be in an unusable state. A 
recovery will run now (dpkg --configure -a).

  
  Upgrade complete

  
  The upgrade has completed but there were errors during the upgrade process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Aug  2 01:05:32 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
  InstallationDate: Installed on 2020-07-17 (15 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-78LMT-USB3 R2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: sex
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 R2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jul 18 01:11:31 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input  USB Keyboard   KEYBOARD, id 8
   input  USB Keyboard   KEYBOARD, id 9
   inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890012/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Alexandre Speltri]

@david-hlacik Well, until a month ago, yes. I had enabled the Experimental 
features and it just worked.
Some update broke that, so I had to manually add a simple command to "Startup 
Applications", which was: xrandr --output eDP-1-1 --scale 1.5x1.5

To complete the setup, I let the display scalling (from gnome settings)
to 2x (200%).

There you go! It worked

For more info, see (https://wiki.archlinux.org/index.php/HiDPI)

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  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-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1890930] Re: Xorg freeze

[Seth Arnold]

** Information type changed from Private Security to Public

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu freeze randomly 
  My laptop is AMD ryzen 5 2500U 
  GPU TADEON VEGA GRAPHIC

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  9 13:37:02 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [103c:84ae]
  InstallationDate: Installed on 2020-04-25 (105 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Laptop 15-db0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8fad8780-5a61-47b5-8c26-63fbc3a59d18 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84AE
  dmi.board.vendor: HP
  dmi.board.version: 86.20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/31/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-db0xxx
  dmi.product.sku: 4PC77PA#AKL
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1890930/+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 1890957] Re: [nvidia] My Night Light doesn't work at all.

[Seth Arnold]

** Information type changed from Public Security to Public

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

Title:
  [nvidia] My Night Light doesn't work at all.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  So I don't see my Night Light... I just notice today. A few days ago all 
worked fine. Sometimes it blinks that warm light then after a second I still 
have a normal blue light. I am adding a screenshot below to prove. I am 
expecting to fix this problem as fast as possible. Thanks for your time.
  _
  Release: 20.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  9 21:10:27 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890957/+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 1891712] Re: nautilus takes ages to start up when not already running

[Tessa]

gdb output from nautilus after startup has completed.

** Attachment added: "gdb-nautilus-2020-08-14.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+attachment/5401585/+files/gdb-nautilus-2020-08-14.txt

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

Title:
  nautilus takes ages to start up when not already running

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I'm filing this bug separately because it appears to be distinct from
  #1063282, but the root cause may be similar.

  when I start nautilus and it's not already running, it can take an
  extremely long time to start, up to even 2m before a file browser
  appears. as well, opening certainly locations (like the trash, or
  network shares) can also take another huge span of time before they
  complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
  Uname: Linux 5.4.0-42-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:21:04 2020
  InstallationDate: Installed on 2020-07-15 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+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 1891712] Re: nautilus takes ages to start up when not already running

[Tessa]

Alright, just tested this. ran date before starting nautilus, got "Fri
14 Aug 2020 05:02:02 PM PDT", ran it once the window appeared, got "Fri
14 Aug 2020 05:03:02 PM PDT", so pretty much a full minute to the
second. and here's what I see from journalctl during that period:

Aug 14 17:02:36 boxxy pulseaudio[2703]: D: [pulseaudio] module-udev-detect.c: 
/dev/snd/controlC2 is accessible: no
Aug 14 17:02:36 boxxy pulseaudio[2703]: D: [pulseaudio] module-udev-detect.c: 
Suspending all sinks and sources of card alsa_card.pci-_01_00.1.
Aug 14 17:02:53 boxxy dbus-daemon[2064]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.326' (uid=1>
Aug 14 17:02:53 boxxy systemd[1]: Starting Hostname Service...
Aug 14 17:02:53 boxxy gnome-shell[4717]: ERROR: Error getting parameter! Can 
not get config by name locations.Org.gnome.Nautilus defaulting to false'value 
is undefined
Aug 14 17:02:53 boxxy systemd-resolved[2043]: Server returned error NXDOMAIN, 
mitigating potential DNS violation DVE-2018-0001, retrying transaction with 
reduced feature level UDP.
Aug 14 17:02:53 boxxy dbus-daemon[2064]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Aug 14 17:02:53 boxxy systemd[1]: Started Hostname Service.
Aug 14 17:03:23 boxxy systemd[1]: systemd-hostnamed.service: Succeeded.

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

Title:
  nautilus takes ages to start up when not already running

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I'm filing this bug separately because it appears to be distinct from
  #1063282, but the root cause may be similar.

  when I start nautilus and it's not already running, it can take an
  extremely long time to start, up to even 2m before a file browser
  appears. as well, opening certainly locations (like the trash, or
  network shares) can also take another huge span of time before they
  complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
  Uname: Linux 5.4.0-42-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:21:04 2020
  InstallationDate: Installed on 2020-07-15 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+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 1891588] Re: HP Device Manager buggy

[David Liell]

Clicking on the link supplied gives the following message.

Lost something?

This page does not exist, or you may not have permission to see it.

If you have been to this page before, it is possible it has been
removed.

Check that you are logged in with the correct account, or that you entered
the address correctly, or search for it:


   - Return to the Launchpad front page 


The package with the bug is 'hp-toolbox'.

On Sat, 15 Aug 2020 at 00:30, Brian Murray <1891...@bugs.launchpad.net>
wrote:

> ** Package changed: ubuntu => hplip (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891588
>
> Title:
>   HP Device Manager buggy
>
> Status in hplip package in Ubuntu:
>   New
>
> Bug description:
>   I am using hplip Toolbox on Linux mint 19.1 attempting to install HP
>   Envy 5034 as a wifi device. Toolbox cannot find device. However, using
>   hp-setup  it installs correctly.
>
>   Also, after installing, two 5034s appear in Device manager, one with a
>   red X. Clicking the other icon causes the red X to move to the second
>   printer. By fiddling around, I eventually find the correct printer.
>
>   These problems don't appear in the W10 version.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1891588/+subscriptions
>

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

Title:
  HP Device Manager buggy

Status in hplip package in Ubuntu:
  New

Bug description:
  I am using hplip Toolbox on Linux mint 19.1 attempting to install HP
  Envy 5034 as a wifi device. Toolbox cannot find device. However, using
  hp-setup  it installs correctly.

  Also, after installing, two 5034s appear in Device manager, one with a
  red X. Clicking the other icon causes the red X to move to the second
  printer. By fiddling around, I eventually find the correct printer.

  These problems don't appear in the W10 version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1891588/+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 1891712] Re: nautilus takes ages to start up when not already running

[Sebastien Bacher]

Thank you for your bug report. Could you add your 'journalctl -b 0' log
after getting the issue and indicate the times where you started
nautilus and saw it displayed?

Could you use gdb while it's doing nothing to get a backtrace as
explained on https://wiki.ubuntu.com/Backtrace ?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  nautilus takes ages to start up when not already running

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I'm filing this bug separately because it appears to be distinct from
  #1063282, but the root cause may be similar.

  when I start nautilus and it's not already running, it can take an
  extremely long time to start, up to even 2m before a file browser
  appears. as well, opening certainly locations (like the trash, or
  network shares) can also take another huge span of time before they
  complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
  Uname: Linux 5.4.0-42-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:21:04 2020
  InstallationDate: Installed on 2020-07-15 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+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 1887793] Re: [snap] chromium unable to launch

[Spr Base]

Snap packages don't have any debug symbols.

You could install the chromium deb and dbgsym, then reproduce and share
the gdb backtrace from your core file?

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1887793] Re: [snap] chromium unable to launch

[Spr Base]

The message "Kernel has no file descriptor comparison support" comes from mesa
src/mesa/drivers/dri/i965/brw_bufmgr.c

https://cgit.freedesktop.org/mesa/mesa/commit/?id=57e4d0aa1c16d3be36ccee4065c55901cb6fad43

Also this bug mentions
https://bugs.chromium.org/p/chromium/issues/detail?id=1112162

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

Title:
  [snap] chromium unable to launch

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Updated the chromium snap yesterday, latest/stable (1229). Today from
  a fresh boot, it won't launch.

  ```
  mattias@cerebus:~$ chromium
  Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module"
  Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module"
  Trace/breakpoint trap (core dumped)
  ```

  Using snap revert it goes back to latest/stable (1213), and works
  perfectly.

  Refreshing back to 1229 reproduces the issue.

  OS: Ubuntu 20.04 LTS x86_64 
  Kernel: 5.4.0-40-generic 
  Uptime: 1 hour, 43 mins 
  Packages: 2233 (dpkg), 86 (snap) 
  Shell: bash 5.0.16 
  Resolution: 2560x1440, 2560x1440 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Yaru [GTK2/3] 
  Icons: Yaru [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-4770K (8) @ 3.900GHz 
  GPU: NVIDIA GeForce GTX 970 
  Memory: 8251MiB / 15945MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+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 1054458] Re: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'

[Bill (franksmcb)]

This is occurring on Ubuntu MATE 20.10 daily with nvidia 390.138

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

Title:
  nvidia-detector crashed with ValueError in __get_value_from_name():
  invalid literal for int() with base 10: 'experimental-304'

Status in nvidia-common package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-common source package in Precise:
  Fix Released
Status in ubuntu-drivers-common source package in Precise:
  Invalid
Status in nvidia-common source package in Quantal:
  Invalid
Status in ubuntu-drivers-common source package in Quantal:
  Fix Released
Status in nvidia-common source package in Bionic:
  Invalid
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  If other people report this at the current level with xorg/nvidia it
  might be a bug. It is also possible the error stems from a bad
  combination of free and proprietary material. Further details will be
  provided as necessary/available.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: ubuntu-drivers-common 1:0.2.69
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  Date: Fri Sep 21 22:48:18 2012
  ExecutablePath: /usr/bin/nvidia-detector
  InterpreterPath: /usr/bin/python3.2mu
  ProcCmdline: /usr/bin/python3.2 /usr/bin/nvidia-detector
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   LANGUAGE=de_CH:de
  PythonArgs: ['/usr/bin/nvidia-detector']
  SourcePackage: ubuntu-drivers-common
  Title: nvidia-detector crashed with ValueError in __get_value_from_name(): 
invalid literal for int() with base 10: 'experimental-304'
  UpgradeStatus: Upgraded to quantal on 2012-07-31 (52 days ago)
  UserGroups: audio pulse pulse-access video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1054458/+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 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2

[Bug Watch Updater]

** Changed in: libcdio (Debian)
   Status: New => Fix Released

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

Title:
  program 'cd-paranoia' is missing from package in 1.0.0-2

Status in libcdio package in Ubuntu:
  Invalid
Status in libcdio-paranoia package in Ubuntu:
  Confirmed
Status in libcdio package in Debian:
  Fix Released

Bug description:
  apt show libcdio-utils:

  Description: sample applications based on the CDIO libraries
   This package contains a collection of small libcdio-based tools:
* cd-drive  show CD-ROM drive characteristics
* cd-info   show information about a CD or CD-image
* cd-paranoia   an audio CD ripper
* cd-read   read information from a CD or CD-image
* cdda-player   a simple curses-based audio CD player
* iso-info  show information about an ISO 9660 image
* iso-read  read portions of an ISO 9660 image
* mmc-tool  issue low-level commands to a CD drive

  cd-paranoia is missing from package. This breaks abcde 'optional'
  functionality which is in fact the most common used, since the
  original cdparanoia (separate program) is abandoned since 10 years.

  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  libcdio-utils:
Installiert:   1.0.0-2
Installationskandidat: 1.0.0-2
Versionstabelle:
   *** 1.0.0-2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcdio-utils 1.0.0-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sun Feb 18 18:18:55 2018
  ProcEnviron:
   TERM=qterminal
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libcdio
  UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+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 1891715] [NEW] [System Product Name, VIA VT1708S, Green Headphone Out, Front] No sound at all

[Michael Scofield]

Public bug reported:

It doesn't work from the fresh install of Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bloo   5334 F pulseaudio
 /dev/snd/controlC0:  bloo   5334 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 22:41:36 2020
InstallationDate: Installed on 2020-08-08 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1083 F pulseaudio
  bloo   5334 F pulseaudio
 /dev/snd/controlC0:  gdm1083 F pulseaudio
  bloo   5334 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [System Product Name, VIA VT1708S, Green Headphone Out, Front] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX3 R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd08/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  [System Product Name, VIA VT1708S, Green Headphone Out, Front] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It doesn't work from the fresh install of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bloo   5334 F pulseaudio
   /dev/snd/controlC0:  bloo   5334 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 22:41:36 2020
  InstallationDate: Installed on 2020-08-08 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1083 F pulseaudio
bloo   5334 F pulseaudio
   /dev/snd/controlC0:  gdm1083 F pulseaudio
bloo   5334 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT1708S, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0608
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX3 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd08/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System 

[Desktop-packages] [Bug 1891713] [NEW] I am unable to resize windows by clicking on the tops of them and dragging after gnome-shell restarted due to low performance.

[Seija Kijin]

Public bug reported:

When I was saving a document, the computer froze, and so did the
desktop, and mouse cursor.

Eventually, the mouse cursor reset its position, and the screen flashed
black but then back to normal. However, I was then unable to move
windows around by clicking and dragging them. I had to manually minimize
and then maximize the window back.

This mostly happened to Visual Studio Code, which was running while I
was saving data in another Java application.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 16:26:29 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-07-06 (39 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2020-08-12T16:46:41.139091

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


** Tags: amd64 apport-bug focal

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

Title:
  I am unable to resize windows by clicking on the tops of them and
  dragging after gnome-shell restarted due to low performance.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I was saving a document, the computer froze, and so did the
  desktop, and mouse cursor.

  Eventually, the mouse cursor reset its position, and the screen
  flashed black but then back to normal. However, I was then unable to
  move windows around by clicking and dragging them. I had to manually
  minimize and then maximize the window back.

  This mostly happened to Visual Studio Code, which was running while I
  was saving data in another Java application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 16:26:29 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-06 (39 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2020-08-12T16:46:41.139091

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1891713/+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 1891712] [NEW] nautilus takes ages to start up when not already running

[Tessa]

Public bug reported:

I'm filing this bug separately because it appears to be distinct from
#1063282, but the root cause may be similar.

when I start nautilus and it's not already running, it can take an
extremely long time to start, up to even 2m before a file browser
appears. as well, opening certainly locations (like the trash, or
network shares) can also take another huge span of time before they
complete.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
Uname: Linux 5.4.0-42-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 13:21:04 2020
InstallationDate: Installed on 2020-07-15 (30 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  nautilus takes ages to start up when not already running

Status in nautilus package in Ubuntu:
  New

Bug description:
  I'm filing this bug separately because it appears to be distinct from
  #1063282, but the root cause may be similar.

  when I start nautilus and it's not already running, it can take an
  extremely long time to start, up to even 2m before a file browser
  appears. as well, opening certainly locations (like the trash, or
  network shares) can also take another huge span of time before they
  complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
  Uname: Linux 5.4.0-42-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:21:04 2020
  InstallationDate: Installed on 2020-07-15 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+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 1891696] [NEW] fingerprint does not recognize after enrollment almost like drivers are not loaded all the way at boot or something not sure

[Steven Christopher Lamer]

Public bug reported:

Using ASUS VivoBook,  When attempting to use fingerprint sensor after
enrollment it does not recognize any.  Have done enrollment through both
GUI and fprintd-enroll  have also done fprintd-verify and none of them
verify either.

I enrolled one finger of every type and it still wont recognize any of
them not sure what the problem is.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: fprintd 1.90.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 13:35:41 2020
InstallationDate: Installed on 2020-08-13 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: fprintd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  fingerprint does not recognize after enrollment almost like drivers
  are not loaded all the way at boot or something not sure

Status in fprintd package in Ubuntu:
  New

Bug description:
  Using ASUS VivoBook,  When attempting to use fingerprint sensor after
  enrollment it does not recognize any.  Have done enrollment through
  both GUI and fprintd-enroll  have also done fprintd-verify and none of
  them verify either.

  I enrolled one finger of every type and it still wont recognize any of
  them not sure what the problem is.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: fprintd 1.90.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:35:41 2020
  InstallationDate: Installed on 2020-08-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fprintd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1891696/+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 1888575] Re: Split motd-news config into a new package

[Andreas Hasenack]

** Description changed:

  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config
  
  Care must be taken to preserve a changed /etc/default/motd-news when the
  upgrade installs the new motd-news-config package. For example, on a
  server that has set ENABLED=0 in /etc/default/motd-news and upgrades to
  the new base-files and ubuntu-server, and gets the new motd-config-news
  package, ENABLED=0 must remain set.
  
  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled
  
  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification
  
  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled
  
  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled
  
  e) removing motd-news-config will also remove ubuntu-server (since it's
  a depends, and not a recommends)
  
  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files
  
  g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-
  news-server removes the /e/d/motd-news config file
  
  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0
  
  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled
+ 
+ j) Perform a release upgrade from the previous ubuntu release to the one
+ being tested while having ubuntu-server NOT installed (or use a desktop
+ install).
  
  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.
  
  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
  This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded and /e/d/motd-news was manually removed by the user, 
there will be a /e/d/motd-news.wasremoved leftover empty file (see "other info" 
below for details).
  
  In general, the regression risks here are:
  - have motd-news enabled again on a system where it was previously disabled. 
We tried to envision two ways it would have been disabled (set ENABLED=0, and 
remove the config file). There are probably others
  - differences in dpkg and/or debhelper behavior in older ubuntu releases 
leading to unexpected results (should be covered by the test cases from this 
SRU)
  - xenial in particular is trickier, because src:base-files there does NOT use 
debhelper, so many of the things we take for granted have to be done by hand
  - have some sort of dpkg postinst or dependency error because of unpredicted 
scenarios. Certain assumptions are being made, like the renames that 
dpkg-maintscript-helper does, 

[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Gunnar Hjalmarsson]

Thanks for confirming!

On 2020-08-14 15:01, Akbarkhon Variskhanov wrote:
> bug-existsUbuntu 18.10 cosmic
>   GNOME Shell 3.30.1 (=3.30.1-2ubuntu1)
>   gnome-control-center 3.30.1 (=1:3.30.1-1ubuntu2)
> 
> no-bugUbuntu 19.04 disco
>   GNOME Shell 3.32.0 (=3.32.0+git20190410-1ubuntu1)
>   gnome-control-center 3.32.1 (=1:3.32.1-1ubuntu4)

That info was helpful, since it limited the time frame for where to look
for a possible upstream fix. And the commit mentioned in comment #11 now
has proved to be it. :)

I have uploaded a gnome-shell fix to the bionic SRU queue.

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  In Progress

Bug description:
  [Impact]

  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  [Test Case]

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  Then install gnome-shell from bionic-proposed, reboot, and find that
  an added input source now is effective instantly without any of the
  mentioned workarounds.

  [Regression Potential]

  Minimal. The fix consists of a simple upstream commit which has been
  in use as from GNOME 3.32.

  [Other info]

  Screenshots are attached. The bug is easily reproduced as many times
  as possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1888575] Re: Split motd-news config into a new package

[Andreas Hasenack]

** Description changed:

  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config
  
  Care must be taken to preserve a changed /etc/default/motd-news when the
  upgrade installs the new motd-news-config package. For example, on a
  server that has set ENABLED=0 in /etc/default/motd-news and upgrades to
  the new base-files and ubuntu-server, and gets the new motd-config-news
  package, ENABLED=0 must remain set.
  
  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled
  
  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification
  
  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled
  
  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled
  
  e) removing motd-news-config will also remove ubuntu-server (since it's
  a depends, and not a recommends)
  
  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files
  
  g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-
  news-server removes the /e/d/motd-news config file
  
  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0
  
  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled
  
  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.
  
  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
  This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded and /e/d/motd-news was manually removed by the user, 
there will be a /e/d/motd-news.wasremoved leftover empty file (see "other info" 
below for details).
  
  In general, the regression risks here are:
  - have motd-news enabled again on a system where it was previously disabled. 
We tried to envision two ways it would have been disabled (set ENABLED=0, and 
remove the config file). There are probably others
  - differences in dpkg and/or debhelper behavior in older ubuntu releases 
leading to unexpected results (should be covered by the test cases from this 
SRU)
  - xenial in particular is trickier, because src:base-files there does NOT use 
debhelper, so many of the things we take for granted have to be done by hand
  - have some sort of dpkg postinst or dependency error because of unpredicted 
scenarios. Certain assumptions are being made, like the renames that 
dpkg-maintscript-helper does, and that the filename 
/etc/default/motd-news.wasremoved that I'm touching and verifying is really 
mine and not something that was there already.
  - the versions 

[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Akbarkhon Variskhanov]

Proposed package (https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-
shell/+packages) on https://launchpad.net/~gunnarhj/+archive/ubuntu
/gnome-shell fixes the bug.

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  In Progress

Bug description:
  [Impact]

  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  [Test Case]

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  Then install gnome-shell from bionic-proposed, reboot, and find that
  an added input source now is effective instantly without any of the
  mentioned workarounds.

  [Regression Potential]

  Minimal. The fix consists of a simple upstream commit which has been
  in use as from GNOME 3.32.

  [Other info]

  Screenshots are attached. The bug is easily reproduced as many times
  as possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1873429] Re: Problem with printing in 20.04 version

[Till Kamppeter]

Andrew Bell, Alex Tasin, please provide an error_log of CUPS in debug
mode of a failing job. see
https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log for
instructions. Also provide the PPD file of your printer (from
/etc/cups/ppd/).

Please attach the files on by one, do not compress them and do not
package them together. Thanks.

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

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

Title:
  Problem with printing in 20.04 version

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  In previous 19.10 my Epson Stylus CX3600 both prints & scans fine.

  In 20.04 it scans fine, but in print mode the process banners show the
  job is sent to the printer, then printing is complete. However there
  is no print output. I reinstalled the Epson print drivers but without
  success.

  I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the
  printing issue is solved. The Epson is recognised and my documents
  print and scan fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 10:59:10 2020
  InstallationDate: Installed on 2019-12-10 (128 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873429/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu9

---
pulseaudio (1:13.99.1-1ubuntu9) groovy; urgency=medium

  * d/p/0034-alsa-adjust-ucm-sink-source-priority-according-to-po.patch
  * d/p/0035-ucm-add-possibility-to-skip-the-UCM-card-completely-.patch
  * d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch
Make digital mic on the AMD Renoir machines work under gnome desktop
(LP: #1889217)

 -- Hui Wang   Sat, 08 Aug 2020 13:32:49 +0800

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Launchpad Bug Tracker]

** Merge proposal unlinked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/389300

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in base-files source package in Xenial:
  In Progress
Status in ubuntu-meta source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in ubuntu-meta source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress
Status in base-files source package in Groovy:
  Fix Released
Status in ubuntu-meta source package in Groovy:
  In Progress

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.

  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
  This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded and /e/d/motd-news was manually removed by the user, 
there will be a /e/d/motd-news.wasremoved leftover empty file (see "other info" 
below for details).

[Desktop-packages] [Bug 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing)

[Wirawan Purwanto]

While the data collection above is going on... here is a recap of the
previous X session (2020-07-05 thru 2020-08-10)

* Restarted X server with XFCE.
* Apps used almost all the time: mostly Firefox, MATE terminal
* Apps used sometimes: VLC, "xpra attach", geeqie
* Apps used rarely: libreoffice

I have collected a number of "ps fuxa" outputs which I distilled below
only to show the VSIZE and RSS for that Xorg xserver process:

~~~
2020-07-05 22:39:08 907048 88500
2020-07-05 22:42:24 950740129288libreoffice
2020-07-08 15:13:301199296250108libreoffice
2020-07-11 21:55:101227060277484libreoffice  (vlc started after 
this)
2020-07-13 12:16:531217636271656vlc
2020-07-15 12:40:251234728293524vlc
2020-07-17 23:24:011906196940544vlc(163655) (2GB mem usage, 
terminated)
2020-07-19 20:19:162217016   1046988vlc(357305)
2020-07-20 13:09:062235980   1071448vlc
2020-07-22 13:18:052296896819008vlc
2020-07-22 13:36:042292208862640
2020-07-22 13:36:472259436860288
2020-07-22 14:07:132201380923184
2020-07-30 00:53:512257172   1153128
2020-08-02 20:57:492213628   1178836
2020-08-03 11:54:582250960   1182832vlc(793990)
2020-08-08 10:35:372493120   1526196
~~~

Note: I also filed another bug originally against VLC--because where
you saw the large memory usage above, VLC also showed memory
explosion.

https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1888558

Since that time it was re-attributed to MESA driver.
Looking at the pattern above, there is a strong likelihood that
VLC/MESA is one of the culprits for large X memory consumption.

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

Title:
  Xorg server uses unacceptably large amounts of memory (and keep
  growing)

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Description: Xorg server uses unacceptably large amounts of memory
  (and keep growing)

  Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my
  laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I
  have been troubled by the way Xorg process uses memory.

  Here is an example of memory usage of Xorg as a function of time. I
  rebooted the laptop on June 17:

  Xorg-usage-20200617a.txt:root1224  1.9  0.8 948408 98848 tty7 
Rsl+ 10:38   0:05  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200617b.txt:root1224  2.2  0.8 978264 105180 tty7
Ssl+ 10:38   0:22  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200618a.txt:root1224  0.3  1.3 1143064 162584 tty7   
Ssl+ Jun17   3:15  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619a.txt:root1224  0.3  2.9 1432232 360700 tty7   
Ssl+ Jun17  12:30  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619b.txt:root1224  0.3  2.7 1313120 338656 tty7   
Ssl+ Jun17  12:39  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200623a.txt:root1224  0.3  6.0 1944364 738596 tty7   
Ssl+ Jun17  31:55  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  The filename indicates the date the "ps fuxa" command was run.
  Contrast this against the memory usage of another Xorg process run for XPRA:

  Xorg-usage-20200617b.txt:wirawan 4452  2.4  2.0 1106920 244984 ?  
Ssl  10:46   0:12  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200618a.txt:wirawan 4452  0.2  2.0 1108572 246616 ?  
Ssl  Jun17   2:25  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619a.txt:wirawan 4452  0.2  2.0 1112460 249516 ?  
Ssl  Jun17   8:34  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 

[Desktop-packages] [Bug 1885369] Re: Deja Dup won't start from GNOME applications menu

[Rachel Hoots]

The window just never appears, no error message that I can see

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

Title:
  Deja Dup won't start from GNOME applications menu

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Starting Deja Dup from the GNOME applications menu fails, but the
  program launches fine from the command line. I checked
  /usr/share/applications/org.gnome.DejaDup.desktop to see if the
  command being launched by GNOME was different, but I didn't find
  anything unusual; the exec was the same.

  Deja Dup still runs automatic backups successfully, as far as I can
  tell.

  System information: Ubuntu 20.04 LTS

  deja-dup  40.6-1ubuntu2
  duplicity 0.8.11.1612-1

  /tmp/deja-dup.log:
  org.gnome.DejaDup exclude-list ['/home/rachel/.local/share/Trash', 
'/home/rachel/Downloads', '/home/rachel/.steam', '/home/rachel/VirtualBox VMs', 
'/home/rachel/.cache/spotify/Storage', '/home/rachel/gPodder/Downloads']
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup prompt-check '2020-06-23T11:08:12+00'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run '2020-06-27T11:36:37+00'
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup last-backup '2020-06-27T11:36:37+00'
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup nag-check '2020-06-23T11:50:08+00'
  org.gnome.DejaDup.S3 folder 'Excelsia'
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.Rackspace container 'Excelsia'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack container 'Excelsia'
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.GCS folder 'Excelsia'
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.Local folder '/backup/deja5'
  org.gnome.DejaDup.Google folder 'Excelsia'
  org.gnome.DejaDup.GOA folder '$HOSTNAME'
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA type ''
  org.gnome.DejaDup.GOA migrated false
  org.gnome.DejaDup.Drive folder '$HOSTNAME'
  org.gnome.DejaDup.Drive uuid ''
  org.gnome.DejaDup.Drive name ''
  org.gnome.DejaDup.Drive icon ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.Remote folder 'Excelsia'
  org.gnome.DejaDup.Remote uri ''

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1885369/+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 1873429] Re: Problem with printing in 20.04 version

[Alex Tasin]

same with epson dx9400f

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

Title:
  Problem with printing in 20.04 version

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  In previous 19.10 my Epson Stylus CX3600 both prints & scans fine.

  In 20.04 it scans fine, but in print mode the process banners show the
  job is sent to the printer, then printing is complete. However there
  is no print output. I reinstalled the Epson print drivers but without
  success.

  I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the
  printing issue is solved. The Epson is recognised and my documents
  print and scan fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 10:59:10 2020
  InstallationDate: Installed on 2019-12-10 (128 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873429/+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 1885369] Re: Deja Dup won't start from GNOME applications menu

[Michael Terry]

Is there an error message that is visible or the window just never
appears?

** Project changed: deja-dup => deja-dup (Ubuntu)

** 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/1885369

Title:
  Deja Dup won't start from GNOME applications menu

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  Starting Deja Dup from the GNOME applications menu fails, but the
  program launches fine from the command line. I checked
  /usr/share/applications/org.gnome.DejaDup.desktop to see if the
  command being launched by GNOME was different, but I didn't find
  anything unusual; the exec was the same.

  Deja Dup still runs automatic backups successfully, as far as I can
  tell.

  System information: Ubuntu 20.04 LTS

  deja-dup  40.6-1ubuntu2
  duplicity 0.8.11.1612-1

  /tmp/deja-dup.log:
  org.gnome.DejaDup exclude-list ['/home/rachel/.local/share/Trash', 
'/home/rachel/Downloads', '/home/rachel/.steam', '/home/rachel/VirtualBox VMs', 
'/home/rachel/.cache/spotify/Storage', '/home/rachel/gPodder/Downloads']
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup prompt-check '2020-06-23T11:08:12+00'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup last-run '2020-06-27T11:36:37+00'
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup last-backup '2020-06-27T11:36:37+00'
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup nag-check '2020-06-23T11:50:08+00'
  org.gnome.DejaDup.S3 folder 'Excelsia'
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.Rackspace container 'Excelsia'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack container 'Excelsia'
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.GCS folder 'Excelsia'
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.Local folder '/backup/deja5'
  org.gnome.DejaDup.Google folder 'Excelsia'
  org.gnome.DejaDup.GOA folder '$HOSTNAME'
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA type ''
  org.gnome.DejaDup.GOA migrated false
  org.gnome.DejaDup.Drive folder '$HOSTNAME'
  org.gnome.DejaDup.Drive uuid ''
  org.gnome.DejaDup.Drive name ''
  org.gnome.DejaDup.Drive icon ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.Remote folder 'Excelsia'
  org.gnome.DejaDup.Remote uri ''

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1885369/+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 1866620] Re: deja-dup-monitor startup invalid path

[Michael Terry]

** Project changed: deja-dup => deja-dup (Ubuntu)

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

Title:
  deja-dup-monitor startup invalid path

Status in deja-dup package in Ubuntu:
  New

Bug description:
  deja-dup-monitor has the following paths in the file
  /etc/xdg/autostart/deja-dup-monitor.desktop, which are invalid:

  TryExec=/usr/lib/deja-dup/deja-dup-monitor
  Exec=/usr/lib/deja-dup/deja-dup-monitor

  This prevents deja-dup from making automatic back-ups.

  To resolve the situation, I had to manually update the paths to:

  TryExec=/usr/libexec/deja-dup/deja-dup-monitor
  Exec=/usr/libexec/deja-dup/deja-dup-monitor

  1. Distribution:
  Description:  Ubuntu Focal Fossa (development branch)

  2. Version:
  deja-dup  40.5-1
  duplicity 0.8.11.1596-1

  3. Settings:
  org.gnome.DejaDup exclude-list ['/home/wiktor/.local/share/Trash', 
'/home/wiktor/Downloads', '/home/wiktor/.android', '/home/wiktor/.android-sdk', 
'/home/wiktor/.programy', '/home/wiktor/.VirtualBoxVMs', '/home/wiktor/Music', 
'/home/wiktor/Videos', '/home/wiktor/.gradle', '/home/wiktor/.p2', 
'/home/wiktor/.package-manager', '/home/wiktor/.cache', 
'/home/wiktor/.pub-cache', '/home/wiktor/.local/share/Daedalus', 
'/home/wiktor/.daedalus']
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup periodic-period 1
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup prompt-check '2017-10-13T18:23:45.958383Z'
  org.gnome.DejaDup periodic true
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup last-restore '2020-02-16T11:22:29.255500Z'
  org.gnome.DejaDup last-run '2020-03-09T10:55:11+00'
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup last-backup '2020-03-09T10:55:11+00'
  org.gnome.DejaDup backend 'local'
  org.gnome.DejaDup nag-check '2020-01-26T01:18:25.016870Z'
  org.gnome.DejaDup.S3 folder 'wiktor'
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.Rackspace container 'wiktor'
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack container 'wiktor'
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.GCS folder 'wiktor'
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.Local folder '/mnt/iza/deja-dup'
  org.gnome.DejaDup.Google folder 'wiktor'
  org.gnome.DejaDup.GOA folder 'wiktor'
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA type 'owncloud'
  org.gnome.DejaDup.GOA migrated false
  org.gnome.DejaDup.Drive folder 'wiktor'
  org.gnome.DejaDup.Drive uuid ''
  org.gnome.DejaDup.Drive name ''
  org.gnome.DejaDup.Drive icon ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File relpath @ay []
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.Remote folder 'wiktor'
  org.gnome.DejaDup.Remote uri ''

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1866620/+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 1885369] [NEW] Deja Dup won't start from GNOME applications menu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Starting Deja Dup from the GNOME applications menu fails, but the
program launches fine from the command line. I checked
/usr/share/applications/org.gnome.DejaDup.desktop to see if the command
being launched by GNOME was different, but I didn't find anything
unusual; the exec was the same.

Deja Dup still runs automatic backups successfully, as far as I can
tell.

System information: Ubuntu 20.04 LTS

deja-dup40.6-1ubuntu2
duplicity   0.8.11.1612-1

/tmp/deja-dup.log:
org.gnome.DejaDup exclude-list ['/home/rachel/.local/share/Trash', 
'/home/rachel/Downloads', '/home/rachel/.steam', '/home/rachel/VirtualBox VMs', 
'/home/rachel/.cache/spotify/Storage', '/home/rachel/gPodder/Downloads']
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup prompt-check '2020-06-23T11:08:12+00'
org.gnome.DejaDup periodic true
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run '2020-06-27T11:36:37+00'
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup last-backup '2020-06-27T11:36:37+00'
org.gnome.DejaDup backend 'local'
org.gnome.DejaDup nag-check '2020-06-23T11:50:08+00'
org.gnome.DejaDup.S3 folder 'Excelsia'
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.Rackspace container 'Excelsia'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack container 'Excelsia'
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.GCS folder 'Excelsia'
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.Local folder '/backup/deja5'
org.gnome.DejaDup.Google folder 'Excelsia'
org.gnome.DejaDup.GOA folder '$HOSTNAME'
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA type ''
org.gnome.DejaDup.GOA migrated false
org.gnome.DejaDup.Drive folder '$HOSTNAME'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.Remote folder 'Excelsia'
org.gnome.DejaDup.Remote uri ''

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
Deja Dup won't start from GNOME applications menu
https://bugs.launchpad.net/bugs/1885369
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to deja-dup 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 1866620] [NEW] deja-dup-monitor startup invalid path

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

deja-dup-monitor has the following paths in the file /etc/xdg/autostart
/deja-dup-monitor.desktop, which are invalid:

TryExec=/usr/lib/deja-dup/deja-dup-monitor
Exec=/usr/lib/deja-dup/deja-dup-monitor

This prevents deja-dup from making automatic back-ups.

To resolve the situation, I had to manually update the paths to:

TryExec=/usr/libexec/deja-dup/deja-dup-monitor
Exec=/usr/libexec/deja-dup/deja-dup-monitor

1. Distribution:
Description:Ubuntu Focal Fossa (development branch)

2. Version:
deja-dup40.5-1
duplicity   0.8.11.1596-1

3. Settings:
org.gnome.DejaDup exclude-list ['/home/wiktor/.local/share/Trash', 
'/home/wiktor/Downloads', '/home/wiktor/.android', '/home/wiktor/.android-sdk', 
'/home/wiktor/.programy', '/home/wiktor/.VirtualBoxVMs', '/home/wiktor/Music', 
'/home/wiktor/Videos', '/home/wiktor/.gradle', '/home/wiktor/.p2', 
'/home/wiktor/.package-manager', '/home/wiktor/.cache', 
'/home/wiktor/.pub-cache', '/home/wiktor/.local/share/Daedalus', 
'/home/wiktor/.daedalus']
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup prompt-check '2017-10-13T18:23:45.958383Z'
org.gnome.DejaDup periodic true
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup last-restore '2020-02-16T11:22:29.255500Z'
org.gnome.DejaDup last-run '2020-03-09T10:55:11+00'
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup last-backup '2020-03-09T10:55:11+00'
org.gnome.DejaDup backend 'local'
org.gnome.DejaDup nag-check '2020-01-26T01:18:25.016870Z'
org.gnome.DejaDup.S3 folder 'wiktor'
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.Rackspace container 'wiktor'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack container 'wiktor'
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.GCS folder 'wiktor'
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.Local folder '/mnt/iza/deja-dup'
org.gnome.DejaDup.Google folder 'wiktor'
org.gnome.DejaDup.GOA folder 'wiktor'
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA type 'owncloud'
org.gnome.DejaDup.GOA migrated false
org.gnome.DejaDup.Drive folder 'wiktor'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.Remote folder 'wiktor'
org.gnome.DejaDup.Remote uri ''

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New

-- 
deja-dup-monitor startup invalid path
https://bugs.launchpad.net/bugs/1866620
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to deja-dup 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 1891684] [NEW] screen flickers

[Ryan]

Public bug reported:

when computer is coming out of suspension mode, i get terrible screen
flickers. Only way i have worked around this is a reboot.

This video card is from sapphire 
Nitro + SE 5700xt

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 12:16:42 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1da2:e410]
InstallationDate: Installed on 2020-06-08 (66 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2203
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ubuntu

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

Title:
  screen flickers

Status in xorg package in Ubuntu:
  New

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 12:16:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT 
/ 5700/5700 XT] [1da2:e410]
  InstallationDate: Installed on 2020-06-08 (66 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2203
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  

[Desktop-packages] [Bug 1881909] Re: Screen tearing with Nvidia Optimus

[Launchpad Bug Tracker]

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

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

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

Title:
  Screen tearing with Nvidia Optimus

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  I have screen tearing when using nvidia card with 390 driver, affect
  browsers such as firefox and chromium also desktop since I have screen
  tearing when moving window around.

  I have no such problem when using using 18.04.4 and nvidia card with
  390 driver. Intel graphic have no such problem weather in 18.04 or
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 21:18:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
  InstallationDate: Installed on 2020-06-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. K43SD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43SD
  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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K43SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  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.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/mutter/+bug/1881909/+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 1881909] Re: Screen tearing with Nvidia Optimus

[Mohammad Kazemi]

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

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

Title:
  Screen tearing with Nvidia Optimus

Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  I have screen tearing when using nvidia card with 390 driver, affect
  browsers such as firefox and chromium also desktop since I have screen
  tearing when moving window around.

  I have no such problem when using using 18.04.4 and nvidia card with
  390 driver. Intel graphic have no such problem weather in 18.04 or
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 21:18:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
  InstallationDate: Installed on 2020-06-01 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. K43SD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K43SD.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K43SD
  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.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K43SD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  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.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/mutter/+bug/1881909/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Gunnar Hjalmarsson]

** Description changed:

+ [Impact]
+ 
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.
+ 
+ [Test Case]
  
  Steps to reproduce this bug:
  
  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.
  
  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)
  
  or 5. Reboot or re-login (restarting gnome-shell works as well: killall
  -3 gnome-shell or Alt+F2 > r > Enter)
  
+ Then install gnome-shell from bionic-proposed, reboot, and find that an
+ added input source now is effective instantly without any of the
+ mentioned workarounds.
  
- Screenshots are attached. The bug is easily reproduced as many times as 
possible.
+ [Regression Potential]
+ 
+ Minimal. The fix consists of a simple upstream commit which has been in
+ use as from GNOME 3.32.
+ 
+ [Other info]
+ 
+ Screenshots are attached. The bug is easily reproduced as many times as
+ possible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

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

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

** Changed in: gnome-shell (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gnome-shell (Ubuntu Bionic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  In Progress

Bug description:
  [Impact]

  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  [Test Case]

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  Then install gnome-shell from bionic-proposed, reboot, and find that
  an added input source now is effective instantly without any of the
  mentioned workarounds.

  [Regression Potential]

  Minimal. The fix consists of a simple upstream commit which has been
  in use as from GNOME 3.32.

  [Other info]

  Screenshots are attached. The bug is easily reproduced as many times
  as possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

To manage 

[Desktop-packages] [Bug 1838965] Re: Screen tearing in Firefox on Wayland

[Launchpad Bug Tracker]

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

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

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

Title:
  Screen tearing in Firefox on Wayland

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 68.0.1+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190719083815
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 13:36:32 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.0.1/20190719083815 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1838965/+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 1891613] Re: libraspberrypi0 not installable

[Launchpad Bug Tracker]

This bug was fixed in the package raspberrypi-userland -
0~20200520+git2fe4ca3-0ubuntu2

---
raspberrypi-userland (0~20200520+git2fe4ca3-0ubuntu2) groovy; urgency=medium

  * Don't build libGL/EGL/GLES/etc. libraries with names conflicting with the
mesa copies (LP: #1891613)
  * Tidied up some lintian warnings in armhf build

 -- Dave Jones   Fri, 14 Aug 2020 12:50:20
+0100

** Changed in: raspberrypi-userland (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  libraspberrypi0 not installable

Status in libglvnd package in Ubuntu:
  Invalid
Status in raspberrypi-userland package in Ubuntu:
  Fix Released

Bug description:
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IzpqYj/460-libraspberrypi0_0~20200520+git2fe4ca3-0ubuntu1_armhf.deb
 (--unpack):
  trying to overwrite '/usr/lib/arm-linux-gnueabihf/libEGL.so', which is also 
in package libegl-dev:armhf 1.3.2-1
  (mythtv fails to build on armhf) ^^

  I uploaded a 2:31.0+fixes.20200323.9579662cdc-0ubuntu5 version without that 
libraspberrypi-dev [armhf] | hello 
  dependency, so we can progress with x265 transition.

  Please have a look, and declare breaks/replaces or stop shipping that
  library!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1891613/+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 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing)

[Wirawan Purwanto]

Brief comment. Have restarted X server 3 days ago to run pretty much
just Firefox + MATE terminal. Will let you know later how this goes. So
far the X server memory usage (RSS) is about 125-130MB. Which is high,
but not super terrible. Usually it takes a few more days before the
usage swells.

Another comment, xfwm4 is using quite a bit of X pixmap memory (50-54 MB
as reported by xrestop). I have 4 desktops, and the laptop display ix
FHD 1920x1080. I wonder if window image caching is what causing this.
When it started it measured already at 30MB.

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

Title:
  Xorg server uses unacceptably large amounts of memory (and keep
  growing)

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Description: Xorg server uses unacceptably large amounts of memory
  (and keep growing)

  Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my
  laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I
  have been troubled by the way Xorg process uses memory.

  Here is an example of memory usage of Xorg as a function of time. I
  rebooted the laptop on June 17:

  Xorg-usage-20200617a.txt:root1224  1.9  0.8 948408 98848 tty7 
Rsl+ 10:38   0:05  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200617b.txt:root1224  2.2  0.8 978264 105180 tty7
Ssl+ 10:38   0:22  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200618a.txt:root1224  0.3  1.3 1143064 162584 tty7   
Ssl+ Jun17   3:15  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619a.txt:root1224  0.3  2.9 1432232 360700 tty7   
Ssl+ Jun17  12:30  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619b.txt:root1224  0.3  2.7 1313120 338656 tty7   
Ssl+ Jun17  12:39  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200623a.txt:root1224  0.3  6.0 1944364 738596 tty7   
Ssl+ Jun17  31:55  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  The filename indicates the date the "ps fuxa" command was run.
  Contrast this against the memory usage of another Xorg process run for XPRA:

  Xorg-usage-20200617b.txt:wirawan 4452  2.4  2.0 1106920 244984 ?  
Ssl  10:46   0:12  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200618a.txt:wirawan 4452  0.2  2.0 1108572 246616 ?  
Ssl  Jun17   2:25  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619a.txt:wirawan 4452  0.2  2.0 1112460 249516 ?  
Ssl  Jun17   8:34  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619b.txt:wirawan 4452  0.2  2.0 1112964 250020 ?  
Ssl  Jun17   8:40  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200623a.txt:wirawan 4452  0.1  2.0 1113092 250544 ?  
Ssl  Jun17  11:22  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100

  My desktop usage pattern:

  * MATE desktop
  * 4-desktop setting (standard default MATE when shipped)
  * GNUCASH
  * about 3 windows of terminal (each about 5-10 tabs)
  * XPRA running Firefox web browser (to isolate web browser pixmap memory 
usage, if that was the culprit)
  * LibreOffice (several windows open at any time)
  * using "redshift" to change the desktop color to red at night

[Desktop-packages] [Bug 1871733] Re: [20.04 Focal Fossa] Light menus when dark mode is active

[igi]

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

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

Title:
  [20.04 Focal Fossa] Light menus when dark mode is active

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  See screenshot.
  It happens also with application menus.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.447
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 01:36:27 2020
  InstallationDate: Installed on 2020-02-23 (45 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1871733/+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 1882034] Re: cannot start X session with NIS account

[Balint Reczey]

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

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

Title:
  cannot start X session with NIS account

Status in gdm3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When login with a NIS account, X does not start, or more precisely it
  starts and exits immediately.

  Only errors in logs is:
   (EE) systemd-logind: failed to get session: PID 4335 does not belong to any 
known session

  X11/gdm login works fine with local accounts.

  SSH/terminal console login with NIS accounts works fine.

  /etc/X11/Xwrapper.config:
allowed_users=anybody

  I've seen several reports of such problems under other versions (eg
  19.10), but no working solutions was found. It seems that the problem
  is the same with lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  4 08:59:25 2020
  InstallationDate: Installed on 2019-11-26 (190 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+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 1891662] [NEW] [80SY, Realtek ALC236, Mic, Internal] No sound at all

[Hadi Najafi]

Public bug reported:

The internal microphone and Headset/Headphone microphones doesn't work
at all. tried multiple headphones and none of them works.

I changed the input config by converting Stereo input, to mono input via 
Pavucontrol app.
Microphone starts working after one sleep. I don't know why after sleep the bug 
disappears.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hadi   2030 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 18:59:09 2020
InstallationDate: Installed on 2019-12-10 (247 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hadi   2030 F pulseaudio
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [80SY, Realtek ALC236, Mic, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 0ZCN52WW
dmi.board.asset.tag: No Asset Tag
dmi.board.vendor: LENOVO
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvr0ZCN52WW:bd12/11/2019:svnLENOVO:pn80SY:pvrLenovoV310-15ISK:rvnLENOVO:rn:rvr:cvnLENOVO:ct10:cvr:
dmi.product.family: IDEAPAD
dmi.product.name: 80SY
dmi.product.sku: LENOVO_MT_80SY_BU_idea_FM_IDEAPAD
dmi.product.version: Lenovo V310-15ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  [80SY, Realtek ALC236, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The internal microphone and Headset/Headphone microphones doesn't work
  at all. tried multiple headphones and none of them works.

  I changed the input config by converting Stereo input, to mono input via 
Pavucontrol app.
  Microphone starts working after one sleep. I don't know why after sleep the 
bug disappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadi   2030 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 18:59:09 2020
  InstallationDate: Installed on 2019-12-10 (247 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadi   2030 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [80SY, Realtek ALC236, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0ZCN52WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.vendor: LENOVO
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvr0ZCN52WW:bd12/11/2019:svnLENOVO:pn80SY:pvrLenovoV310-15ISK:rvnLENOVO:rn:rvr:cvnLENOVO:ct10:cvr:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80SY
  dmi.product.sku: LENOVO_MT_80SY_BU_idea_FM_IDEAPAD
  dmi.product.version: Lenovo V310-15ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1891662/+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 1769936] Re: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

[Hadi Najafi]

I can resolve the issue by 'suspending' the Laptop, and resume using it again.
The microphone works great after one suspend.

P.S: I used "pavucontrol" to config the microphone from Stereo to Mono.

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  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.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1769936/+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 1782629] Re: mutter is ignoring wl_shell_surface_move and wl_shell_surface_resize

[Christian Rauch]

To clarify, the original issue (not being able to move subsurface) is
still present on an up-to-date Ubuntu 16.04. The patch is for the
original debian source package at
http://archive.ubuntu.com/ubuntu/pool/universe/m/mutter/mutter_3.18.3.orig.tar.xz
and is also still valid.

@vanvugt What do you mean with the code is different? The reference for
the patch is still the same, but the code very likely changed between
major mutter versions. I also submitted the patch to GNOME beforehand (2
years ago) but it was rejected because the "old" version 3.18 wasn't
maintained anymore.

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

Title:
  mutter is ignoring wl_shell_surface_move and wl_shell_surface_resize

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter (wayland) is ignoring wl_shell_surface_move and
  wl_shell_surface_resize request, which prevents the use of subsurfaces
  window decorations (example:
  http://github.com/christianrauch/wayland_window_decoration_example).
  The same example works on weston.

  The fault is in the method "meta_wayland_pointer_can_grab_surface"
  where "pointer->focus_surface == surface" does not hold for
  subsurfaces. The attached patch removes the test for the focused
  surface and allows resizing and moving of the wl_shell surface in the
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mutter 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 19 18:51:14 2018
  InstallationDate: Installed on 2016-04-26 (813 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1782629/+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 1891588] Re: HP Device Manager buggy

[Brian Murray]

** Package changed: ubuntu => hplip (Ubuntu)

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

Title:
  HP Device Manager buggy

Status in hplip package in Ubuntu:
  New

Bug description:
  I am using hplip Toolbox on Linux mint 19.1 attempting to install HP
  Envy 5034 as a wifi device. Toolbox cannot find device. However, using
  hp-setup  it installs correctly.

  Also, after installing, two 5034s appear in Device manager, one with a
  red X. Clicking the other icon causes the red X to move to the second
  printer. By fiddling around, I eventually find the correct printer.

  These problems don't appear in the W10 version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1891588/+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 1891588] [NEW] HP Device Manager buggy

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I am using hplip Toolbox on Linux mint 19.1 attempting to install HP
Envy 5034 as a wifi device. Toolbox cannot find device. However, using
hp-setup  it installs correctly.

Also, after installing, two 5034s appear in Device manager, one with a
red X. Clicking the other icon causes the red X to move to the second
printer. By fiddling around, I eventually find the correct printer.

These problems don't appear in the W10 version.

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


** Tags: bot-comment
-- 
HP Device Manager buggy
https://bugs.launchpad.net/bugs/1891588
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to hplip 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 1879479] Re: Saving doc/docx document with formula in table removes this formula

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: In Progress => Fix Released

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

Title:
  Saving doc/docx document with formula in table removes this formula

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

Bug description:
  Description:
  Formula handling inside tables is broken in Microsoft Office DOC or DOCX file 
formats.

  Steps to Reproduce:
  1. Open LibreOffice Writer
  2. Insert table of any size - for example 4x4
  3. Enter some numbers in the table cells
  4. Go to the last (right bottom) cell, hit "=", enter "=sum()"
  5. Save the document as Microsoft Office DOC or DOCX and close document
  6. Open just saved DOC/DOCX document and change some numbers in table (try 
pressing F9 for sure)

  Actual Results:
  * the formula in the table is not saved, the user is unable to calculate with 
it after saving file as DOC / DOCX

  Expected Results:
  * the formula in the table is saved, the user is able to calculate with it 
after saving file as DOC / DOCX

  Notes: the same happens if original document is DOC / DOCX. Saving
  table with formula removes the formula on next open. Test ODT document
  is in attachment.

  The almost latest LO 6.4.3.2 as in Ubuntu 20.04 LTS is also affected
  by this bug:

  Version: 6.4.3.2
  Build ID: 1:6.4.3-0ubuntu0.20.04.1
  CPU threads: 1; OS: Linux 5.4; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue May 19 13:37:57 2020
  InstallationDate: Installed on 2020-04-23 (25 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1879479/+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 1782629] Re: mutter is ignoring wl_shell_surface_move and wl_shell_surface_resize

[Christian Rauch]

Well the patch is for mutter 3.18.3, so it will still be needed on this
version.

However, this issue and patch are now more than 2 years old (without any
response during this time). It has been fixed in newer mutter versions
as used in Ubuntu 18.04 or 20.04.

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

Title:
  mutter is ignoring wl_shell_surface_move and wl_shell_surface_resize

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter (wayland) is ignoring wl_shell_surface_move and
  wl_shell_surface_resize request, which prevents the use of subsurfaces
  window decorations (example:
  http://github.com/christianrauch/wayland_window_decoration_example).
  The same example works on weston.

  The fault is in the method "meta_wayland_pointer_can_grab_surface"
  where "pointer->focus_surface == surface" does not hold for
  subsurfaces. The attached patch removes the test for the focused
  surface and allows resizing and moving of the wl_shell surface in the
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mutter 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul 19 18:51:14 2018
  InstallationDate: Installed on 2016-04-26 (813 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1782629/+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 1879479]

[Libreoffice-commits]

László Németh committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/cf596c43315bb96b5e7256a82256f1ccb8c9c4d0

tdf#133163 DOCX: export formula cells

It will be available in 7.1.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  Saving doc/docx document with formula in table removes this formula

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

Bug description:
  Description:
  Formula handling inside tables is broken in Microsoft Office DOC or DOCX file 
formats.

  Steps to Reproduce:
  1. Open LibreOffice Writer
  2. Insert table of any size - for example 4x4
  3. Enter some numbers in the table cells
  4. Go to the last (right bottom) cell, hit "=", enter "=sum()"
  5. Save the document as Microsoft Office DOC or DOCX and close document
  6. Open just saved DOC/DOCX document and change some numbers in table (try 
pressing F9 for sure)

  Actual Results:
  * the formula in the table is not saved, the user is unable to calculate with 
it after saving file as DOC / DOCX

  Expected Results:
  * the formula in the table is saved, the user is able to calculate with it 
after saving file as DOC / DOCX

  Notes: the same happens if original document is DOC / DOCX. Saving
  table with formula removes the formula on next open. Test ODT document
  is in attachment.

  The almost latest LO 6.4.3.2 as in Ubuntu 20.04 LTS is also affected
  by this bug:

  Version: 6.4.3.2
  Build ID: 1:6.4.3-0ubuntu0.20.04.1
  CPU threads: 1; OS: Linux 5.4; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue May 19 13:37:57 2020
  InstallationDate: Installed on 2020-04-23 (25 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1879479/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Gunnar Hjalmarsson]

I found an older upstream gnome-shell issue which seems to have been
fixed through this commit:

https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/b405ed64

May be worth a test.

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  
  Screenshots are attached. The bug is easily reproduced as many times as 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Gunnar Hjalmarsson]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #691
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/691

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3061 => 
gitlab.gnome.org/GNOME/gnome-shell/-/issues #691

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  
  Screenshots are attached. The bug is easily reproduced as many times as 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Siegfried]

3.36.5 has the fix included and just appeared on Debian sid. Hopefully
it lands in Ubuntu soon.

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

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

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1879968/+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 1891649] [NEW] [snap] Gnome dash window tracking is broken when using chromium snap

[Aljoscha Vollmerhaus]

Public bug reported:

I've created a custom chromium launcher for an internal website, starting 
chromium in --app mode.
The launcher should get it's own Gnome dash icon.

To match the created windows to the dash icon, I've taken the following 
measures:
- include "StartupWMClass=myfoo" in the myfoo.desktop file
- gave chromium the "--class=myfoo" parameter to make it set it's WM_CLASS to 
myfoo

I've verified the WM_CLASS to be properly set to myfoo using xprop.
However, this does not work when chromium is launched via snap.
All windows get attributed to the chromium dash icon no matter what their 
WM_CLASS is.

Bypassing snap and launching chromium via /snap/chromium/current/usr/lib
/chromium-browser/chrome fixes the problem.

Here are the full chromium exec lines:
Broken:
Exec=chromium --class=myfoo --no-first-run --app=https://internal.example.com/
Working:
Exec=/snap/chromium/current/usr/lib/chromium-browser/chrome --class=myfoo 
--no-first-run --app=https://internal.example.com/

This is on a fully patched 20.04 system.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  I've created a custom chromium launcher for an internal website, starting 
chromium in --app mode.
  The launcher should get it's own Gnome dash icon.
  
  To match the created windows to the dash icon, I've taken the following 
measures:
  - include "StartupWMClass=myfoo" in the myfoo.desktop file
  - gave chromium the "--class=myfoo" parameter to make it set it's WM_CLASS to 
myfoo
  
  I've verified the WM_CLASS to be properly set to myfoo using xprop.
  However, this does not work when chromium is launched via snap.
  All windows get attributed to the chromium dash icon no matter what their 
WM_CLASS is.
  
  Bypassing snap and launching chromium via /snap/chromium/current/usr/lib
  /chromium-browser/chrome fixes the problem.
  
  Here are the full chromium exec lines:
  Broken:
  Exec=chromium --class=myfoo --no-first-run --app=https://internal.example.com/
  Working:
  Exec=/snap/chromium/current/usr/lib/chromium-browser/chrome --class=myfoo 
--no-first-run --app=https://internal.example.com/
+ 
+ This is on a fully patched 20.04 system.

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

Title:
  [snap] Gnome dash window tracking is broken when using chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I've created a custom chromium launcher for an internal website, starting 
chromium in --app mode.
  The launcher should get it's own Gnome dash icon.

  To match the created windows to the dash icon, I've taken the following 
measures:
  - include "StartupWMClass=myfoo" in the myfoo.desktop file
  - gave chromium the "--class=myfoo" parameter to make it set it's WM_CLASS to 
myfoo

  I've verified the WM_CLASS to be properly set to myfoo using xprop.
  However, this does not work when chromium is launched via snap.
  All windows get attributed to the chromium dash icon no matter what their 
WM_CLASS is.

  Bypassing snap and launching chromium via
  /snap/chromium/current/usr/lib/chromium-browser/chrome fixes the
  problem.

  Here are the full chromium exec lines:
  Broken:
  Exec=chromium --class=myfoo --no-first-run --app=https://internal.example.com/
  Working:
  Exec=/snap/chromium/current/usr/lib/chromium-browser/chrome --class=myfoo 
--no-first-run --app=https://internal.example.com/

  This is on a fully patched 20.04 system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1891649/+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 1891648] [NEW] Cannot switch to A2DP profile w/o restarting bluetooth.service

[Kirill Bogdanenko]

Public bug reported:

When connecting to any Bluetooth device, PulseAudio fails to change its
profile to A2DP (and leaves it in HSP/HFP).

The following is appended to /var/log/syslog when trying to change
profile in pavucontrol:

Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile to
a2dp_sink: Not connected

I'm currently using patched pulseaudio-modules-bt from here:
https://github.com/EHfive/pulseaudio-modules-bt. But the problem
persists with both packages.

The working workaround I found is:

  sudo systemctl restart bluetooth.service
  bluetoothctl

# list device MACs
devices

# use a MAC from the list above
connect 

After doing this, it is possible to switch to A2DP profile in
pavucontrol. But such restart is required each time device is connected.

I'm using
Kubuntu 20.10 (development branch)
pulseaudio: 1:13.99.1-1ubuntu8
pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
  but also reproducible with 1:13.99.1-1ubuntu8

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.1-1ubuntu8
ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
Uname: Linux 5.4.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu44
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kyrboh19544 F pulseaudio
 /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
 /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Aug 14 15:06:43 2020
InstallationDate: Installed on 2020-08-07 (6 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
dmi.bios.date: 05/22/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.2
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

To manage 

[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Akbarkhon Variskhanov]

bug-exists  Ubuntu 18.04.5 LTS bionic
GNOME Shell 3.28.4 (=3.28.4-0ubuntu18.04.3)
gnome-control-center 3.28.2 (=1:3.28.2-0ubuntu0.18.04.6)

bug-exists  Ubuntu 18.10 cosmic
GNOME Shell 3.30.1 (=3.30.1-2ubuntu1)
gnome-control-center 3.30.1 (=1:3.30.1-1ubuntu2)

no-bug  Ubuntu 19.04 disco
GNOME Shell 3.32.0 (=3.32.0+git20190410-1ubuntu1)
gnome-control-center 3.32.1 (=1:3.32.1-1ubuntu4)

Tested on various versions of Ubuntu running on a virtual machine.

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  
  Screenshots are attached. The bug is easily reproduced as many times as 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1891613] Re: libraspberrypi0 not installable

[Dave Jones]

Looks like the armhf version of the package builds two (identical)
copies of various GL-related libs (EGL, GLESv2, etc): one with "mesa-
like" names (e.g. libEGL.so) and one with broadcom-specific names (e.g.
libbrcmEGL.so).

In either case, the produced libraries are for use with the "legacy"
graphics stack supported on the Pi 0 thru 3. The Pi 4 and beyond only
support the mesa graphics stack (which is why these aren't built on
arm64 as the Pi Foundation only (officially) support arm64 on the Pi 4).

I've added a patch to a build here which should suppress the production
of the "mesa-like" libs while leaving the broadcom-specific named copies
(as they seem to be in use by several groups), and tidied up the lintian
warnings on the armhf build.

Will upload a copy to my userland PPA shortly.

** Patch added: "Add a patch to prevent building the mesa-named libs on armhf"
   
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1891613/+attachment/5401473/+files/dont-build-mesa-libs.debdiff

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

Title:
  libraspberrypi0 not installable

Status in libglvnd package in Ubuntu:
  Invalid
Status in raspberrypi-userland package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IzpqYj/460-libraspberrypi0_0~20200520+git2fe4ca3-0ubuntu1_armhf.deb
 (--unpack):
  trying to overwrite '/usr/lib/arm-linux-gnueabihf/libEGL.so', which is also 
in package libegl-dev:armhf 1.3.2-1
  (mythtv fails to build on armhf) ^^

  I uploaded a 2:31.0+fixes.20200323.9579662cdc-0ubuntu5 version without that 
libraspberrypi-dev [armhf] | hello 
  dependency, so we can progress with x265 transition.

  Please have a look, and declare breaks/replaces or stop shipping that
  library!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1891613/+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 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Rinse Meijer]

I'am sorry, I tried to update the Mutter with the normal Update Procedures...
I'am not capable to Compile or install the Mutter 3.37.4 as you mention/refer 
to...
Instead (as I do not believe that I'am the only person) I installed:
Kubuntu 20.04, KDE Plasma 5.18.5 etc. etc,
Copy & Paste with LibreOffice works Fine...   
Even the lay-out and overall the User-Interface has some advantages (of course 
very personal) but I will be using this Plasma version in the mean time...

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

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

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1879968/+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 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

Hey, I installed Linux kernal 5.8.1-050801-generic But the problem still
persists.

On Aug 14, 2020 3:33 PM, "Anupam Jayaraj"  wrote:

> (Reading database ... 274517 files and directories currently installed.)
> Preparing to unpack 
> linux-image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb 
> ...
> Unpacking linux-image-unsigned-5.8.1-050801-generic 
> (5.8.1-050801.202008111432) over (5.8.1-050801.202008111432) ...
> dpkg: dependency problems prevent configuration of 
> linux-image-unsigned-5.8.1-050801-generic:
>  linux-image-unsigned-5.8.1-050801-generic depends on 
> linux-modules-5.8.1-050801-generic; however:
>   Package linux-modules-5.8.1-050801-generic is not installed.
>
> dpkg: error processing package linux-image-unsigned-5.8.1-050801-generic 
> (--install):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  linux-image-unsigned-5.8.1-050801-generic
>
>
>
> On Aug 14, 2020 3:18 PM, "Anupam Jayaraj"  wrote:
>
>> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/
>> linux-image-unsigned-5.8.1-050801-generic_5.8.1-050801.
>> 202008111432_amd64.deb
>> * This file cannot be installed because of unmet dependencies*
>>
>> On Aug 14, 2020 2:55 PM, "Daniel van Vugt" <1891...@bugs.launchpad.net>
>> wrote:
>>
>>> To upgrade the kernel you need to download these files:
>>>
>>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>>> headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>>> 
>>>
>>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>>> headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb
>>> 
>>>
>>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>>> image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>>> 
>>>
>>> and then in a Terminal window run:
>>>
>>>   cd ~/Downloads
>>>   sudo dpkg -i linux*.deb
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1891470
>>>
>>> Title:
>>>   [amdgpu] White screen on resume from suspend
>>>
>>> Status in linux package in Ubuntu:
>>>   Incomplete
>>> Status in mutter package in Ubuntu:
>>>   Incomplete
>>>
>>> Bug description:
>>>   The PC usually shows a Butter milk like screen when it wakes up from
>>> suspension.my laptop is set to lid close to undergo suspension.when I open
>>> the lid a paper white or Butter milk screen is shown.the only solution is
>>> to force power of by long pressing power button. this issue is also
>>> observed when the Ubuntu 20.04 OS starts.My PC is in dual boot. I play
>>> videos from Windows then shutdown Windows.On the next boot I select Ubuntu
>>> from boot options.At that time some texts are shown and after a couple of
>>> seconds this Butter milk like screen could be observed.It maybe graphics
>>> issue.
>>>   ---
>>>   ProblemType: Bug
>>>   ApportVersion: 2.20.11-0ubuntu27.6
>>>   Architecture: amd64
>>>   CasperMD5CheckResult: skip
>>>   CurrentDesktop: ubuntu:GNOME
>>>   DistroRelease: Ubuntu 20.04
>>>   InstallationDate: Installed on 2020-06-20 (54 days ago)
>>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>>> (20200423)
>>>   Package: mutter 3.36.3-0ubuntu0.20.04.1
>>>   PackageArchitecture: amd64
>>>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>>>   Tags: third-party-packages focal wayland-session
>>>   Uname: Linux 5.4.0-42-generic x86_64
>>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>>   UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
>>> video
>>>   _MarkForUpload: True
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470
>>> /+subscriptions
>>>
>>

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

Title:
  [amdgpu] White screen on resume from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At 

[Desktop-packages] [Bug 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

[Sebastien Bacher]

Going to reassigning to debconf, while it's gtk not handling when
loaders are not configured that's during-update issue where the system
is in inconsistent state and I'm unsure GTK itself is where to fix the
problem

it had been discussed a bit on  https://irclogs.ubuntu.com/2020/04/21
/%23ubuntu-release.html#t16:15

debconf handles GTK failing, but that's not a clear failure case, the
error is hit when trying to load icons ... one way to address this would
perhaps be to make debconf try to do that and fallback as well if it's
failing. Reassigning to foundation and tagging rls-ff-incoming since
that's a common case of upgrade failure

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Tags added: rls-ff-incoming

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

Title:
  Debconf crash due to assertion failure in ensure_surface_for_gicon
  [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

Status in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
  https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383

  ---

  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1627564/+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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[Leon Liao]

** Description changed:

- In some cases, the wow is not configured and the
+ [Impact]
+ 
+  In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).
  
- The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit. 
- But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. 
- So, the management of wake-on-LAN still is done by NetworkManager.
+  The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
+  But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
+  So, the management of wake-on-LAN still is done by NetworkManager.
+ 
+ [Test Case]
+ 
+  On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
+  Step 1. Enter suspend (s2idle)
+  Setp 2. Resume from suspend
+ 
+  After resume from suspend, the Wi-Fi functiall still is normal.
+ 
+  You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
+  https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
+ 
+ [Regression Potential]
+ 
+  * No potential regressions.
+ 
+ [Other Info]
+  
+  * None

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1891636] [NEW] After recent updates Xorg crashes whenever entering Display Settings

[Tuomas Heino]

Public bug reported:

AssertionMessage Xort: ../../../../../../include/privates.h:121:
dixGetPrivateAddr: Assertion `key-initialized' failed.

Also affected by apport bug #1891634 making filling more information
here somewhat tedious.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 13:08:34 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2020-04-10 (125 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

Status in xorg-server package in Ubuntu:
  New

Bug description:
  AssertionMessage Xort: ../../../../../../include/privates.h:121:
  dixGetPrivateAddr: Assertion `key-initialized' failed.

  Also affected by apport bug #1891634 making filling more information
  here somewhat tedious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:08:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  

[Desktop-packages] [Bug 1891632] [NEW] The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[Leon Liao]

Public bug reported:

In some cases, the wow is not configured and the
NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
management of wake-on-LAN in NetworkManager).

The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. 
But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. 
So, the management of wake-on-LAN still is done by NetworkManager.

** Affects: oem-priority
 Importance: Critical
 Assignee: Leon Liao (lihow731)
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Information type changed from Proprietary to Public

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Leon Liao (lihow731)

** Merge proposal linked:
   
https://code.launchpad.net/~lihow731/network-manager/+git/network-manager/+merge/388865

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

  The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit. 
  But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. 
  So, the management of wake-on-LAN still is done by NetworkManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1775447] Re: Mines counts bombs wrong on edge

[Launchpad Bug Tracker]

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

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

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

Title:
  Mines counts bombs wrong on edge

Status in gnome-mines package in Ubuntu:
  Confirmed

Bug description:
  A square on the edge can count neighboring bombs incorrectly as shown
  in the image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1775447/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[David Hlacik]

@alexandreporks hows that possible? I am using Pop_OS 20.04 since it release 
date, and fractional scaling does not work , same as Ubuntu 20.04. 
Could you please provide me with the steps? Did you just enable fractional 
scaling with gsettings set org.gnome.mutter experimental-features 
"['x11-randr-fractional-scaling']"
 and it worked??

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  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-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1888698] Re: package grub-pc 2.04-1ubuntu26 failed to install/upgrade: installed grub-pc package post-installation script subprocess was killed by signal (Aborted)

[Julian Andres Klode]

Reassigning to gtk+3.0 though I don't really know what to do here, we
need gtk operational during upgrades to show prompts.

(frontend:10148): Gtk-WARNING **: 16:28:16.133: Could not 
load a pixbuf fro icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.

Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/usr/share/icons/Adwaita/48x48/status/image-missing.png: Formato del file di 
immagine non riconosciuto (gdk-pixbuf-error-quark, 3)
Bail out! 
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/usr/share/icons/Adwaita/48x48/status/image-missing.png: Formato del file di 
immagine non riconosciuto (gdk-pixbuf-error-quark, 3)

** Package changed: grub2 (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  package grub-pc 2.04-1ubuntu26 failed to install/upgrade: installed
  grub-pc package post-installation script subprocess was killed by
  signal (Aborted)

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Replaced hard disk

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: grub-pc 2.04-1ubuntu26
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jul 23 16:32:19 2020
  ErrorMessage: installed grub-pc package post-installation script subprocess 
was killed by signal (Aborted)
  InstallationDate: Installed on 2016-10-06 (1386 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=c8f897e7-37ef-480d-8cad-8171d126799c ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: grub2
  Title: package grub-pc 2.04-1ubuntu26 failed to install/upgrade: installed 
grub-pc package post-installation script subprocess was killed by signal 
(Aborted)
  UpgradeStatus: Upgraded to focal on 2020-07-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1888698/+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 1888698] [NEW] package grub-pc 2.04-1ubuntu26 failed to install/upgrade: installed grub-pc package post-installation script subprocess was killed by signal (Aborted)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Replaced hard disk

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-pc 2.04-1ubuntu26
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jul 23 16:32:19 2020
ErrorMessage: installed grub-pc package post-installation script subprocess was 
killed by signal (Aborted)
InstallationDate: Installed on 2016-10-06 (1386 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=c8f897e7-37ef-480d-8cad-8171d126799c ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: grub2
Title: package grub-pc 2.04-1ubuntu26 failed to install/upgrade: installed 
grub-pc package post-installation script subprocess was killed by signal 
(Aborted)
UpgradeStatus: Upgraded to focal on 2020-07-23 (0 days ago)

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


** Tags: amd64 apport-package focal
-- 
package grub-pc 2.04-1ubuntu26 failed to install/upgrade: installed grub-pc 
package post-installation script subprocess was killed by signal (Aborted)
https://bugs.launchpad.net/bugs/1888698
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Vincent Gerris]

I had this issue with an internal FHD screen on a Dell laptop with Nvidia 
MX150/ intel 620 using Nvidia driver 440 and an external 4k screen on HDMI.
When I switched to the Nouveau driver it worked as expected with the external 
monitor at 150% and the laptop at 100%.

So a valid workaround for me, perhaps for others.
It's nice to see other workarounds too, I hope this bug will be fixed in a way 
that this works without any application/terminal settings or hacks, so with 
proprietary driver and fractional scaling.
I don't want to change font size, multiple settings across apps and such, just 
have a single point to change that works, just like in other major OSes :)

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  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-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

(Reading database ... 274517 files and directories currently installed.)
Preparing to unpack
linux-image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
...
Unpacking linux-image-unsigned-5.8.1-050801-generic
(5.8.1-050801.202008111432) over (5.8.1-050801.202008111432) ...
dpkg: dependency problems prevent configuration of
linux-image-unsigned-5.8.1-050801-generic:
 linux-image-unsigned-5.8.1-050801-generic depends on
linux-modules-5.8.1-050801-generic; however:
  Package linux-modules-5.8.1-050801-generic is not installed.

dpkg: error processing package
linux-image-unsigned-5.8.1-050801-generic (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-unsigned-5.8.1-050801-generic


On Aug 14, 2020 3:18 PM, "Anupam Jayaraj"  wrote:

> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/
> amd64/linux-image-unsigned-5.8.1-050801-generic_5.8.1-
> 050801.202008111432_amd64.deb
> * This file cannot be installed because of unmet dependencies*
>
> On Aug 14, 2020 2:55 PM, "Daniel van Vugt" <1891...@bugs.launchpad.net>
> wrote:
>
>> To upgrade the kernel you need to download these files:
>>
>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>> headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>> 
>>
>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>> headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb
>> 
>>
>>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
>> image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>> 
>>
>> and then in a Terminal window run:
>>
>>   cd ~/Downloads
>>   sudo dpkg -i linux*.deb
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1891470
>>
>> Title:
>>   [amdgpu] White screen on resume from suspend
>>
>> Status in linux package in Ubuntu:
>>   Incomplete
>> Status in mutter package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   The PC usually shows a Butter milk like screen when it wakes up from
>> suspension.my laptop is set to lid close to undergo suspension.when I open
>> the lid a paper white or Butter milk screen is shown.the only solution is
>> to force power of by long pressing power button. this issue is also
>> observed when the Ubuntu 20.04 OS starts.My PC is in dual boot. I play
>> videos from Windows then shutdown Windows.On the next boot I select Ubuntu
>> from boot options.At that time some texts are shown and after a couple of
>> seconds this Butter milk like screen could be observed.It maybe graphics
>> issue.
>>   ---
>>   ProblemType: Bug
>>   ApportVersion: 2.20.11-0ubuntu27.6
>>   Architecture: amd64
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: ubuntu:GNOME
>>   DistroRelease: Ubuntu 20.04
>>   InstallationDate: Installed on 2020-06-20 (54 days ago)
>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>>   Package: mutter 3.36.3-0ubuntu0.20.04.1
>>   PackageArchitecture: amd64
>>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>>   Tags: third-party-packages focal wayland-session
>>   Uname: Linux 5.4.0-42-generic x86_64
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
>> video
>>   _MarkForUpload: True
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470
>> /+subscriptions
>>
>

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

Title:
  [amdgpu] White screen on resume from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  

[Desktop-packages] [Bug 1857383] Re: Fractional scaling applies to both monitors when you only want it on one

[Vincent Gerris]

I had this issue with an internal FHD screen on a Dell laptop with Nvidia 
MX150/ intel 620 using Nvidia driver 440 and an external 4k screen on HDMI.
When I switched to the Nouveau driver it worked as expected with the external 
monitor at 150% and the laptop at 100%.

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

Title:
  Fractional scaling applies to both monitors when you only want it on
  one

Status in Mutter:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single
  motive that has fractional scalling) and when activating fractional
  scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04
  (laptop warranty issue) on same hardware but using the latest Ubuntu
  20.04 version and now when i activate fractional scalling it does not
  work anymore.

  The issue is that it basically zooms both the displays, i can explain
  best by attaching the printscreens and a picture with my phone on the
  same thing.You will see in the photo taken with the phone how it
  actually scales now and how the screenshots are taken...

  Let me know what logs/commands etc is needed to pinpoint this which i
  think is a regression.

  The monitor on which i want to scale is 4k and is connecting through DELL 
DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock 
WD19 but same issue).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges: b'org.gnome.mutter' b'experimental-features' 
b"['scale-monitor-framebuffer']"
  InstallationDate: Installed on 2019-12-18 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1
  Tags:  focal
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1857383/+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 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-image-
unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb

* This file cannot be installed because of unmet dependencies*

On Aug 14, 2020 2:55 PM, "Daniel van Vugt" <1891...@bugs.launchpad.net>
wrote:

> To upgrade the kernel you need to download these files:
>
>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
> headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>
>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
> headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb
>
>   https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
> image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb
>
> and then in a Terminal window run:
>
>   cd ~/Downloads
>   sudo dpkg -i linux*.deb
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891470
>
> Title:
>   [amdgpu] White screen on resume from suspend
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The PC usually shows a Butter milk like screen when it wakes up from
> suspension.my laptop is set to lid close to undergo suspension.when I open
> the lid a paper white or Butter milk screen is shown.the only solution is
> to force power of by long pressing power button. this issue is also
> observed when the Ubuntu 20.04 OS starts.My PC is in dual boot. I play
> videos from Windows then shutdown Windows.On the next boot I select Ubuntu
> from boot options.At that time some texts are shown and after a couple of
> seconds this Butter milk like screen could be observed.It maybe graphics
> issue.
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27.6
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 20.04
>   InstallationDate: Installed on 2020-06-20 (54 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   Package: mutter 3.36.3-0ubuntu0.20.04.1
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>   Tags: third-party-packages focal wayland-session
>   Uname: Linux 5.4.0-42-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1891470/+subscriptions
>

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

Title:
  [amdgpu] White screen on resume from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470/+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 1891470] Re: [amdgpu] White screen on resume from suspend

[Daniel van Vugt]

To upgrade the kernel you need to download these files:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
headers-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
headers-5.8.1-050801_5.8.1-050801.202008111432_all.deb

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/amd64/linux-
image-unsigned-5.8.1-050801-generic_5.8.1-050801.202008111432_amd64.deb

and then in a Terminal window run:

  cd ~/Downloads
  sudo dpkg -i linux*.deb

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

Title:
  [amdgpu] White screen on resume from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470/+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 1891470] Re: [amdgpu] White screen on resume from suspend

[Daniel van Vugt]

Those are separate commands that do not print any output. You need to
run them on separate lines:

  journalctl -b-1 > prevboot.txt
  lspci -k > lspcik.txt
  dpkg -l > packages.txt

and then attach the text files they created here.

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

Title:
  [amdgpu] White screen on resume from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470/+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 1891470] Re: [amdgpu] White screen on resume from suspend

[Anupam Jayaraj]

I have run both commands *journalctl -b-1 > prevboot.txt > lspci -k >
lspci.txt*

*And*
dpkg -l > packages.txt

But no output has been given.


*Please teach me to upgrade kernel. I have poor technical knowledge:(

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

Title:
  [amdgpu] White screen on resume from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The PC usually shows a Butter milk like screen when it wakes up from 
suspension.my laptop is set to lid close to undergo suspension.when I open the 
lid a paper white or Butter milk screen is shown.the only solution is to force 
power of by long pressing power button. this issue is also observed when the 
Ubuntu 20.04 OS starts.My PC is in dual boot. I play videos from Windows then 
shutdown Windows.On the next boot I select Ubuntu from boot options.At that 
time some texts are shown and after a couple of seconds this Butter milk like 
screen could be observed.It maybe graphics issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-20 (54 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages focal wayland-session
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891470/+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 1891614] Re: [snap] password store issue, plus keepassxc integration fail

[Martin Weis]

Bug #1741074 is related, explains the snap issues

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

Title:
  [snap] password store issue, plus  keepassxc integration fail

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since switching to 20.04 I see a lot of problems with my standard
  browser (chromium-browser), which seem to be related to snap.

  Problem can be described as: Password management impossible
  * chromium does not remember passwords and cannot import from csv
  * chromium does not allow integration of keepassxc as a workaround to broken 
internal storage

  * after migration from 18.04 the pw storage format seemed to have changed, so 
I needed to create new profiles, old password dbs were broken/inaccessible.
  * the following applies to fresh profiles, too (without addons and other 
config)
  * Chromiums internal password store does not store any passwords any more, 
none are shown in the list, none get stored, none imported

  Settings:
  chrome://settings/passwords
  [x] Offer to save passwords
  [x] Auto Sign-in
  [ ] google account

  [enabled] chrome://flags/#PasswordImport

  Saved passwords
  > Saved passwords will appear here
  [none saved]

  * import from csv does not work
  * fill in passwords does not work
  * save credentials does not work, 
  * sometimes a user list can appear (autofill of username fields)

  I tried to switch to an external password manager (keepassxc), but failed, 
since
  * chromium cannot connect to keepassxc (seems to be a snap issue), while 
firefox in parallel can
  * Extension "KeePassXC-Browser" needed 
(https://chrome.google.com/webstore/detail/keepassxc-browser/oboonakemofpalcgghocfoadofidjkkk)

  The keepass helper script denies snap installs:
  https://raw.githubusercontent.com/keepassxreboot/keepassxc/master/utils
  /keepassxc-snap-helper.sh

  ```
  askBrowserSnap() {
  if (whiptail --title "Snap Choice" --defaultno \
  --yesno "Is this browser installed as a snap (usually NO)?" 8 
60); then
  # BASE_DIR="$1"
  whiptail --title "Snap Choice" --msgbox "Sorry, browsers installed as 
snaps are not supported at this time" 8 50
  exit 0
  fi
  }
  ```

  Is there any workaround

  Version:
  Version 84.0.4147.105 (Official Build) snap (64-bit)

  apt-cache policy chromium-browser
  chromium-browser:
Installed: 83.0.4103.97-0ubuntu0.20.04.1

  snap list
  Name   Version Rev   Tracking Publisher   
Notes
  chromium   84.0.4147.105   1260  latest/stablecanonical✓  -

  Additional questions
  The snap install of a central component like a browser is an annoyance, 
breaking other stuff, too (e.g. access to files): are there proper packages for 
apt somewhere?
  I spent hours already to try finding what is going on with $browser.
  Can snap be completely deactivated?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1891614/+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 1891338] Re: apparmor misconfigured for envice

[Sebastien Bacher]

/etc/apparmor.d/abstractions/ubuntu-browsers.d/ubuntu-integration:
/usr/lib/@{multiarch}/xfce4/exo-1/exo-helper-1 ixr,

/etc/apparmor.d/usr.bin.evince:  /usr/lib/@{multiarch}/xfce4/exo-1/exo-
helper-1 ixr,

looks like those needs to be adapted to include the new exo revision?

** Package changed: evince (Ubuntu) => apparmor (Ubuntu)

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

Title:
  apparmor misconfigured for envice

Status in apparmor package in Ubuntu:
  New

Bug description:
  On a fully up to date xubuntu 20-04 system, when i run evince and
  click on a link, it fails to follow that link in my browser. This kind
  of thing happens when you are reading a technical paper and want to
  follow one of the references and click on the doi or url.

  When i click on the link i get a box that i cannot copy from that says:
  Failed to launch preferred application for category "WebBrowser".

  Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-2
  /exo-helper-2"(Permission denied).

  Did I say that it is annoying that i could not copy the text in this
  box!!

  The output of the ldd command you asked for is attached.

  I should also point out that this worked fine under xubuntu 18.04.

  I had originally posted this as an additional comment on
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159?comments=all
  but https://launchpad.net/~seb128 said that I should submit this as a
  separate bug because this is likely an apparmor configuration problem
  that is similar to the ancient bug
  https://bugs.launchpad.net/bugs/987578.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1891338/+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 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu

[Sebastien Bacher]

Thank you for your bug report could you get a 'journalctl -b 0 >
nmdebug' log after getting the issue and add the file to the report?

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
  better uninstall ubuntu

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.

  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter

  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
   DeviceName: Realtek PCIe FE Family Controller
   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
   Kernel driver in use: r8169
   Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
   Kernel driver in use: rtl8723be
   Kernel modules: rtl8723be

  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change has made (IPv6 disabled through settings)
  Only one SSID is in use: Dialog 4G

  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+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 1825585] Re: Application / Document search does not close when the "Put Windows" extension is installed

[Szigyarto Mihaly]

I don't use any of the listed extensions, but still happens. Quite a
shame that it's marked as invalid if multiple previously working
extensions can suddenly brake the UI ...

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

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

Title:
  Application / Document search does not close when the "Put Windows"
  extension is installed

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Pressing the super key, or clicking on `Show Applications` will
  display the application / Document search.

  I'm unable to then close the search, or it hangs around having stolen
  focus.

  Attempted to close by pressing:

  * Escape
  * Super
  * Alt+F4

  Meaning that:

  * already open applications cannot be interacted with
  * switching virtual desktops does not work

  I have to right click on applications in the dock and select quit to
  close each one.

  Then have to log out and back in.

  This is the only way to have the system be usable again.

  FYI, I have upgraded from Ubuntu 18.10 to 19.04 rather than this being
  a fresh install.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 23:07:14 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825585/+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 1891614] [NEW] [snap] password store issue, plus keepassxc integration fail

[Martin Weis]

Public bug reported:

Since switching to 20.04 I see a lot of problems with my standard
browser (chromium-browser), which seem to be related to snap.

Problem can be described as: Password management impossible
* chromium does not remember passwords and cannot import from csv
* chromium does not allow integration of keepassxc as a workaround to broken 
internal storage

* after migration from 18.04 the pw storage format seemed to have changed, so I 
needed to create new profiles, old password dbs were broken/inaccessible.
* the following applies to fresh profiles, too (without addons and other config)
* Chromiums internal password store does not store any passwords any more, none 
are shown in the list, none get stored, none imported

Settings:
chrome://settings/passwords
[x] Offer to save passwords
[x] Auto Sign-in
[ ] google account

[enabled] chrome://flags/#PasswordImport

Saved passwords
> Saved passwords will appear here
[none saved]

* import from csv does not work
* fill in passwords does not work
* save credentials does not work, 
* sometimes a user list can appear (autofill of username fields)

I tried to switch to an external password manager (keepassxc), but failed, since
* chromium cannot connect to keepassxc (seems to be a snap issue), while 
firefox in parallel can
* Extension "KeePassXC-Browser" needed 
(https://chrome.google.com/webstore/detail/keepassxc-browser/oboonakemofpalcgghocfoadofidjkkk)

The keepass helper script denies snap installs:
https://raw.githubusercontent.com/keepassxreboot/keepassxc/master/utils
/keepassxc-snap-helper.sh

```
askBrowserSnap() {
if (whiptail --title "Snap Choice" --defaultno \
--yesno "Is this browser installed as a snap (usually NO)?" 8 60); 
then
# BASE_DIR="$1"
whiptail --title "Snap Choice" --msgbox "Sorry, browsers installed as 
snaps are not supported at this time" 8 50
exit 0
fi
}
```

Is there any workaround

Version:
Version 84.0.4147.105 (Official Build) snap (64-bit)

apt-cache policy chromium-browser
chromium-browser:
  Installed: 83.0.4103.97-0ubuntu0.20.04.1

snap list
Name   Version Rev   Tracking Publisher   Notes
chromium   84.0.4147.105   1260  latest/stablecanonical✓  -

Additional questions
The snap install of a central component like a browser is an annoyance, 
breaking other stuff, too (e.g. access to files): are there proper packages for 
apt somewhere?
I spent hours already to try finding what is going on with $browser.
Can snap be completely deactivated?

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [snap] password store issue, plus  keepassxc integration fail

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since switching to 20.04 I see a lot of problems with my standard
  browser (chromium-browser), which seem to be related to snap.

  Problem can be described as: Password management impossible
  * chromium does not remember passwords and cannot import from csv
  * chromium does not allow integration of keepassxc as a workaround to broken 
internal storage

  * after migration from 18.04 the pw storage format seemed to have changed, so 
I needed to create new profiles, old password dbs were broken/inaccessible.
  * the following applies to fresh profiles, too (without addons and other 
config)
  * Chromiums internal password store does not store any passwords any more, 
none are shown in the list, none get stored, none imported

  Settings:
  chrome://settings/passwords
  [x] Offer to save passwords
  [x] Auto Sign-in
  [ ] google account

  [enabled] chrome://flags/#PasswordImport

  Saved passwords
  > Saved passwords will appear here
  [none saved]

  * import from csv does not work
  * fill in passwords does not work
  * save credentials does not work, 
  * sometimes a user list can appear (autofill of username fields)

  I tried to switch to an external password manager (keepassxc), but failed, 
since
  * chromium cannot connect to keepassxc (seems to be a snap issue), while 
firefox in parallel can
  * Extension "KeePassXC-Browser" needed 
(https://chrome.google.com/webstore/detail/keepassxc-browser/oboonakemofpalcgghocfoadofidjkkk)

  The keepass helper script denies snap installs:
  https://raw.githubusercontent.com/keepassxreboot/keepassxc/master/utils
  /keepassxc-snap-helper.sh

  ```
  askBrowserSnap() {
  if (whiptail --title "Snap Choice" --defaultno \
  --yesno "Is this browser installed as a snap (usually NO)?" 8 
60); then
  # BASE_DIR="$1"
  whiptail --title "Snap Choice" --msgbox "Sorry, browsers installed as 
snaps are not supported at this time" 8 50
  exit 0
  fi
  }
  ```

  Is there any workaround

  Version:
  

[Desktop-packages] [Bug 1884846] Re: Can't connect to internet if second user session

[Sebastien Bacher]

not needed, I'm reassigning this one to wpa now

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

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

Title:
  Can't connect to internet if second user session

Status in wpa package in Ubuntu:
  New

Bug description:
  My kid was using the laptop, connected to internet in his user
  session.

  I switched to my user (but his session was still active), and
  NetworkManager couldn't connect to internet.

  Error from syslog:

  Jun 23 19:30:15 tanquita NetworkManager[854]: 
  [1592951415.1979] audit: op="connection-activate" uuid="a52379fa-
  0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000
  result="fail" reason="Private connection already active on the device:
  uid 1000 has no permission to perform this operation"

  (uid 1000 is myself)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Jun 23 19:40:19 2020
  InstallationDate: Installed on 2020-06-20 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 
metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1884846/+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 1891613] Re: libraspberrypi0 not installable

[Timo Aaltonen]

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

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

Title:
  libraspberrypi0 not installable

Status in libglvnd package in Ubuntu:
  Invalid
Status in raspberrypi-userland package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IzpqYj/460-libraspberrypi0_0~20200520+git2fe4ca3-0ubuntu1_armhf.deb
 (--unpack):
  trying to overwrite '/usr/lib/arm-linux-gnueabihf/libEGL.so', which is also 
in package libegl-dev:armhf 1.3.2-1
  (mythtv fails to build on armhf) ^^

  I uploaded a 2:31.0+fixes.20200323.9579662cdc-0ubuntu5 version without that 
libraspberrypi-dev [armhf] | hello 
  dependency, so we can progress with x265 transition.

  Please have a look, and declare breaks/replaces or stop shipping that
  library!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1891613/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

I did... LP: #1891518.

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  New
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1891613] [NEW] libraspberrypi0 not installable

[Gianfranco Costamagna]

Public bug reported:

dpkg: error processing archive 
/tmp/apt-dpkg-install-IzpqYj/460-libraspberrypi0_0~20200520+git2fe4ca3-0ubuntu1_armhf.deb
 (--unpack):
trying to overwrite '/usr/lib/arm-linux-gnueabihf/libEGL.so', which is also in 
package libegl-dev:armhf 1.3.2-1
(mythtv fails to build on armhf) ^^

I uploaded a 2:31.0+fixes.20200323.9579662cdc-0ubuntu5 version without that 
libraspberrypi-dev [armhf] | hello 
dependency, so we can progress with x265 transition.

Please have a look, and declare breaks/replaces or stop shipping that
library!

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

** Affects: raspberrypi-userland (Ubuntu)
 Importance: High
 Assignee: Dave Jones (waveform)
 Status: Confirmed

** Changed in: raspberrypi-userland (Ubuntu)
   Status: New => Confirmed

** Changed in: raspberrypi-userland (Ubuntu)
   Importance: Undecided => High

** Changed in: raspberrypi-userland (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

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

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

Title:
  libraspberrypi0 not installable

Status in libglvnd package in Ubuntu:
  Invalid
Status in raspberrypi-userland package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IzpqYj/460-libraspberrypi0_0~20200520+git2fe4ca3-0ubuntu1_armhf.deb
 (--unpack):
  trying to overwrite '/usr/lib/arm-linux-gnueabihf/libEGL.so', which is also 
in package libegl-dev:armhf 1.3.2-1
  (mythtv fails to build on armhf) ^^

  I uploaded a 2:31.0+fixes.20200323.9579662cdc-0ubuntu5 version without that 
libraspberrypi-dev [armhf] | hello 
  dependency, so we can progress with x265 transition.

  Please have a look, and declare breaks/replaces or stop shipping that
  library!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1891613/+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