date:20200612

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

** Changed in: nvidia-graphics-drivers-435 (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/1870637

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

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

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  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.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

[Desktop-packages] [Bug 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[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/1870637

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

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

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  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.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

[Desktop-packages] [Bug 1872110] Re: [Samsung 100NZA] No sound

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

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

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

Title:
  [Samsung 100NZA] No sound

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  tengo instalado ubuntu 18.04 de 32 bits y no hay forma de que pueda
  hacer funcionar el sonido, ya probe reinstalando alsa y pulseaudio y
  no hay forma, necesito una ayuda para poder quedarme con este sistema
  operativo, muchas gracias.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-97.98-generic 4.15.18
  Uname: Linux 4.15.0-97-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr 10 14:00:24 2020
  DistUpgraded: 2020-04-10 10:09:39,450 WARNING no activity on terminal for 300 
seconds (printer-driver-foo2zjs (i386) instalado)
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be1] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller [144d:c664]
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 100NZA
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-97-generic 
root=UUID=0e55513e-8acd-4784-affc-3ae8ec7bd17d ro splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 00OT
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD
  dmi.board.version: 0.1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr00OT:bd10/07/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn100NZA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD:rnIntelpoweredclassmatePC:rvr0.1:cvnSAMSUNGELECTRONICSCO.,LTD:ct9:cvr0.1:
  dmi.product.family: CedarTrail System
  dmi.product.name: 100NZA
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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: Fri Apr 10 13:45:55 2020
  xserver.configfile: default
  xserver.errors:
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.4
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1870637] Re: Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 300000KHz

[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/1870637

Title:
  Nvidia+modeset: Can't set 4K@60Hz: HDMI max TMDS frequency 30KHz

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

Bug description:
  When i do get it to work, on reboot it'll be back to fullhd.
  this happens on nvidia 440, 435 and 390.

  On X.Org X server it does work.

  Graphics card: nVidia GT1030
  Amp: Onkyo TX-NR646

  On 19.10 there are no problems.
  A couple of weeks ago i tested a daily build and there were no troubles also, 
so this is new.

  My favourite setting: 3840x2160 200% 60hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..10.00.0: Error: [Errno 21] Is een map: 
'/proc/driver/nvidia/gpus/:10: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 01:02:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=99bd1cce-b30c-44fb-8ead-90317474c33f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.D0:bd12/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2(MS-7B84):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  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.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/nvidia-graphics-drivers-435/+bug/1870637/+subscriptions

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

[Desktop-packages] [Bug 1883235] Re: freez when using

2020-06-12 Thread Abir

System hang many times.

** Attachment added: "System hang"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883235/+attachment/5383410/+files/VID-20200613-WA.mp4

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

Title:
  freez when using

Status in xorg package in Ubuntu:
  New

Bug description:
  when i am using my computer for long time then there is a problem many
  time like when i am open activities then again back to home screen
  then start  hanging problem ,but mouser pointer work but when i am
  going to open an application it gives the option but its shows in
  activities ,i can not open it.then i was turned off my computer.now i
  dont have  that video,but when problems occurs again, i will show in
  it video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 12 15:51:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1883334] [NEW] Xorg freezes after Lock (win+L or via Menu>Lock)

2020-06-12 Thread Marcos R. Tosetti

Public bug reported:

This started to happen after installing the last update last week. If I
lock the screen (using either Win+L or opening the menu and clicking
Lock) the screen turns to black and it doesn't come back anymore. I know
the system is still operational since the NumLock button still responds
(turns on and off If I press it) and the HotSpot still works on my
phone, but the screen just doesn't come back from black. This wasn't an
issue before the update, it is very recent. Thank you very much!

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: Fri Jun 12 22:51:13 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last week or two
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0640]
   Subsystem: Dell Radeon R7 M260/M265 [1028:0640]
MachineType: Dell Inc. Inspiron 5447
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=45c56570-89cf-4b2d-8f15-ee1ce0d54f68 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0MHP6R
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A05
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/12/2014:svnDellInc.:pnInspiron5447:pvrA05:rvnDellInc.:rn0MHP6R:rvrA01:cvnDellInc.:ct8:cvrA05:
dmi.product.family: 00
dmi.product.name: Inspiron 5447
dmi.product.sku: Inspiron 5447
dmi.product.version: A05
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102+git2006051830.5ab603~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2006110730.27b7b8~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2006110730.27b7b8~oibaf~f
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

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


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

** Description changed:

- This started to happen after I install the last update last week, at
- first it would occur a few times, but now is every time. If I lock the
- screen (using either Win+L or opening the menu e click Lock) the screen
- turns to black and it doesn't come back anymore. I know the system is
- still operational since the NumLock button still responds (turns on and
- off If I press it) and the HotSpot still works on my phone, but the
- screen just doesn't come back from black. This wasn't an issue before
- the update, it is very recent. Thank you very much!
+ This started to happen after installing the last update last week. If I
+ lock the screen (using either Win+L or opening the menu and clicking
+ Lock) the screen turns to black and it doesn't come back anymore. I know
+ the system is still operational since the NumLock button still responds
+ (turns on and off If I press it) and the HotSpot still works on my
+ phone, but the screen just doesn't come back from black. This wasn't an
+ issue before the update, it is very recent. Thank you very much!
  
  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: Fri Jun 12 22:51:13 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
-  virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed
+  virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed
+  virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency:

[Desktop-packages] [Bug 1883330] [NEW] package desktop-file-utils 0.24-1ubuntu3 failed to install/upgrade: end of file on stdin at conffile prompt

2020-06-12 Thread James Melvin

Public bug reported:

I have no further details. This report was generated automatically.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: desktop-file-utils 0.24-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jun 11 21:11:15 2020
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2020-06-07 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: desktop-file-utils
Title: package desktop-file-utils 0.24-1ubuntu3 failed to install/upgrade: end 
of file on stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gnome.defaults.list: 2020-06-10T07:12:26.122647

** Affects: desktop-file-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package desktop-file-utils 0.24-1ubuntu3 failed to install/upgrade:
  end of file on stdin at conffile prompt

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

Bug description:
  I have no further details. This report was generated automatically.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: desktop-file-utils 0.24-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jun 11 21:11:15 2020
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2020-06-07 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: desktop-file-utils
  Title: package desktop-file-utils 0.24-1ubuntu3 failed to install/upgrade: 
end of file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gnome.defaults.list: 2020-06-10T07:12:26.122647

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1883330/+subscriptions

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2020-06-12 Thread Erich Eickmeyer

** No longer affects: ubuntustudio-default-settings (Ubuntu)

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Released
Status in Boot-Repair:
  Fix Released
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in OS-Uninstaller:
  Fix Released
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list:

Re: [Desktop-packages] [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection

2020-06-12 Thread mike Bernson

that fixes the --no-sandbox but still needs the
QT_X11_NO_MITSHM=1

also the --no-xshm works now.

This whole bug report shows my big problem with snaps.

In production I have a pin a version of chromium that works so that I can use
webdriver to access a number of site that I need to submit data to.

Once snap become in place I do not see any way to lock/pin a version of 
chromium that
works while the bug get fix.

How can problems like this be dealt with ?

On 6/12/20 10:52 AM, Olivier Tilloy wrote:
> https://bugs.chromium.org/p/chromium/issues/detail?id=1039560#c14
> suggests that this should be fixed in the latest 83 stable update.
>
> Would you mind testing that update from https://launchpad.net
> /~canonical-chromium-builds/+archive/ubuntu/stage and reporting whether
> the issue persists?
>
> I'd recommend disabling that PPA after the test, the updates will
> eventually be available in the Ubuntu archive.
>

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

Title:
  Chromium 81.0.4044.122 crashes on remote ssh connection

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium crash on a ssh x forwarding connection

  It crashes on both 18.04 and 16.04 with the same message.
  The X forwarding is working for other programs just fine.

  It was working until last update.

  Here is the message from the console on the crash

  [22765:22781:0506/144206.193243:FATAL:gpu_data_manager_impl_private.cc(439)] 
GPU process isn't usable. Goodbye.
  Trace/breakpoint trap (core dumped)

  Steps to repeat:
  ssh ltcd-prod
  chromum-browser

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 81.0.4044.122-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c cpuid veth iptable_filter bpfilter bridge 
stp llc binfmt_misc intel_powerclamp coretemp kvm_intel kvm irqbypass zfs 
zunicode zavl icp ipmi_ssif gpio_ich crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel zcommon znvpair spl zlua aesni_intel aes_x86_64 crypto_simd 
cryptd glue_helper intel_cstate ast drm_vram_helper ttm drm_kms_helper lpc_ich 
drm joydev input_leds fb_sys_fops syscopyarea sysfillrect sysimgblt ipmi_si 
ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel lp parport nfsd auth_rpcgss 
nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic igb uas 
usbhid ahci i2c_algo_bit hid libahci usb_storage dca i2c_ismt
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768 800x600 800x600 640x480
  Date: Wed May  6 14:37:46 2020
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstalledPlugins:

  Load-Avg-1min: 0.55
  Load-Processes-Running-Percent:   0.1%
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb'
  MachineType: Supermicro A1SAi
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic 
root=UUID=c75e8c2a-b85d-444e-b278-16fd90c327e7 ro 
usb_storage.quirks=0bc2:331a:u,0bc2:ab31:u,0bc2:ab34:u
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.1a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A1SRi
  dmi.board.vendor: Supermicro
  dmi.board.version: 123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 18
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1a:bd08/27/2015:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SRi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.:
  dmi.product.family: SMC X10
  dmi.product.name: A1SAi
  dmi.product.sku: 081315D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877173/+subscriptions

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

[Desktop-packages] [Bug 1883235] Re: freez when using

2020-06-12 Thread 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/1883235

Title:
  freez when using

Status in xorg package in Ubuntu:
  New

Bug description:
  when i am using my computer for long time then there is a problem many
  time like when i am open activities then again back to home screen
  then start  hanging problem ,but mouser pointer work but when i am
  going to open an application it gives the option but its shows in
  activities ,i can not open it.then i was turned off my computer.now i
  dont have  that video,but when problems occurs again, i will show in
  it video .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 12 15:51:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2020-06-12 Thread Sean Davis

** No longer affects: lightdm-gtk-greeter-settings

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Released
Status in Boot-Repair:
  Fix Released
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in OS-Uninstaller:
  Fix Released
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1881912] Re: SRU 1.64.3 to focal

2020-06-12 Thread Steve Langasek

Hello Marco, or anyone else affected,

Accepted gjs into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gjs/1.64.3-1~ubuntu20.04.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gjs (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU 1.64.3 to focal

Status in gjs package in Ubuntu:
  In Progress
Status in gjs source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.3

  [ Test case ]

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

  GNOME Shell and its components should continue working, as well other
  gjs based apps like polari

  [ Regression potential ]

  Update fixed various memory leaks and errors, updates to Gtk to work
  with GTK4, so gtk3 apps should continue working properly, and string
  operations should not be affected by some GLib overrides changes.

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

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

[Desktop-packages] [Bug 1881923] Re: No icons in file picker

2020-06-12 Thread AllesMeins

Thanks, this has solved it!

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

Title:
  No icons in file picker

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I installed chromium via snap on Ubuntu 20.04. When the file picker is
  opend (for example to upload some files) all icons are missing. Files
  and folders have no icon (see attached screenshot).

  Ubuntu 20.04 LTS
  Chromium Version 83.0.4103.61 (Official Build) snap (64-bit)

  Maybe it is a problem with the apparmor-profile?

  [27780.715573] audit: type=1400 audit(1591194917.741:3258): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=5553 
comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [27780.737385] audit: type=1400 audit(1591194917.761:3259): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" 
pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [27781.003139] audit: type=1400 audit(1591194918.029:3260): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" 
pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [27781.012869] audit: type=1107 audit(1591194918.037:3261): pid=1073 uid=100 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/hostname1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.285" pid=5553 label="snap.chromium.chromium" peer_pid=156208 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=100 hostname=? addr=? 
terminal=?'
  [27784.173782] audit: type=1400 audit(1591194921.197:3262): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" 
pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881923/+subscriptions

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

[Desktop-packages] [Bug 1882402] Re: Ubuntu-drivers allows installation of (nvidia-340) drivers, which are broken/break things (Kubuntu 20.04)

Re: updated logs - I did a fresh Kubuntu 20.04 install to USB stick
(NOTE: 'Download Updates' and 'Install Third Party Drivers' selected via
installer), rebooted, and was greeted by black screen, as per original
bug issue.

The Nvidia drivers were again installed that have issues.

So possibly buggy/incomplete nvidia drivers, but ubuntu-drivers was
still 'aware' of issues:

"
root@xxxubuntu-drivers list
ERROR:root:No "nvidia-dkms-340" can be found.
nvidia-340
"

I also did "apt-get update && apt-get upgrade" which upgraded a lot of
things, but reboot has no change to black screen.

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?

  "
  root@XXX# ubuntu-drivers 

  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "

  Reproduction:
  ===
  1) ubuntu-drivers list

  2) which shows:

  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340

  "
  3) ubuntu-drivers install nvidia-340

  4) Reboot ==> black screen, no login screen


  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-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/ubuntu/+source/ubuntu-drivers-common/+bug/1882402/+subscriptions

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

[Desktop-packages] [Bug 1882402] UbuntuDriversDebug.txt

apport information

** Attachment added: "UbuntuDriversDebug.txt"
   
https://bugs.launchpad.net/bugs/1882402/+attachment/5383377/+files/UbuntuDriversDebug.txt

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?

  "
  root@XXX# ubuntu-drivers 

  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "

  Reproduction:
  ===
  1) ubuntu-drivers list

  2) which shows:

  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340

  "
  3) ubuntu-drivers install nvidia-340

  4) Reboot ==> black screen, no login screen


  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-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/ubuntu/+source/ubuntu-drivers-common/+bug/1882402/+subscriptions

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

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

apport information

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

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?

  "
  root@XXX# ubuntu-drivers 

  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "

  Reproduction:
  ===
  1) ubuntu-drivers list

  2) which shows:

  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340

  "
  3) ubuntu-drivers install nvidia-340

  4) Reboot ==> black screen, no login screen


  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-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/ubuntu/+source/ubuntu-drivers-common/+bug/1882402/+subscriptions

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

[Desktop-packages] [Bug 1881007] Re: [SRU] libreoffice 6.4.4 for focal

I think libreoffice does meet pretty well the requirements for
microrelease exception. The only point I'm not sure about is whether the
tests cover API/ABI stability, this should be researched and confirmed.

As stated in the description, upstream runs both automated and manual
testing for each new micro release (and the corresponding release
candidates).
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests has some
information. Additionally the autopkgtests for the package are pretty
extensive.

We have a long history of SRUing libreoffice microreleases to LTSes,
predating my taking over the maintenance of this package in 2017.

I'll let Heather comment on the impact of bug #1869561 (its importance
is set to High, if that's any indication).

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

Title:
  [SRU] libreoffice 6.4.4 for focal

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Focal:
  Incomplete

Bug description:
  [Impact]

   * LibreOffice 6.4.4 is in its fourth bugfix release of the 6.4 line. Version 
6.4.4 is currently in focal.
 For a list of fixed bugs compared to 6.4.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.4/RC2#List_of_fixed_bugs
 (that's a total of 98 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 98 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

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

apport information

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

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?

  "
  root@XXX# ubuntu-drivers 

  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "

  Reproduction:
  ===
  1) ubuntu-drivers list

  2) which shows:

  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340

  "
  3) ubuntu-drivers install nvidia-340

  4) Reboot ==> black screen, no login screen


  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-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/ubuntu/+source/ubuntu-drivers-common/+bug/1882402/+subscriptions

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

[Desktop-packages] [Bug 1882402] Re: Ubuntu-drivers allows installation of (nvidia-340) drivers, which are broken/break things (Kubuntu 20.04)

apport information

** Description changed:

  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.
  
  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.
  
  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34
  
  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0
  
  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)
  
  
  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "
  
  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.
  
  2) Improvements - I had access to terminal (Ctrl-Alt Fxxx).
  Why is there not an 'uninstall' option for ubuntu-drivers?
  
  "
  root@XXX# ubuntu-drivers 
  
  Available commands:
 list: Show all driver packages which apply to the current system.
 list-oem: Show all OEM enablement packages which apply to this system
 devices: Show all devices which need drivers, and which packages apply to 
them.
 install: Install drivers that are appropriate for your hardware.
 debug: Print all available information and debug data about drivers.
  "
  
  Reproduction:
  ===
  1) ubuntu-drivers list
  
  2) which shows:
  
  "
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  
  "
  3) ubuntu-drivers install nvidia-340
  
  4) Reboot ==> black screen, no login screen
  
  
  Solved problem by reinstall (later research showed that " apt-get purge 
*nvidia* " may have rolled-back changes, however 
  " ubuntu-drivers uninstall nvidia-340 " would be a LOT more user-friendly).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-drivers-common 1:0.8.1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-06-12 (0 days ago)
+ InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ NonfreeKernelModules: nvidia
+ Package: ubuntu-drivers-common 1:0.8.1.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
+ Tags:  focal
+ Uname: Linux 5.4.0-37-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

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

Title:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things (Kubuntu 20.04)

Status in ubuntu-drivers-common package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu-drivers allows installation of (nvidia-340) drivers, which are
  broken/break things.

  Allowing ( :-P ) ubuntu-drivers to install nvidia-340 results in no GUI on 
reboot, only console available.
  X does appear to be running, but only a black screen.

  
  Kernel: 
  
  5.4.0-33.37-generic 5.4.34

  CPU:
  =
  processor   : 3
  vendor_id   : AuthenticAMD
  cpu family  : 23
  model   : 17
  model name  : AMD Ryzen 3 2200G with Radeon Vega Graphics
  stepping: 0

  GPU:
  ==
  01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] 
(rev a1)
  0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)


  Error:
  
  "
  root@X# ubuntu-drivers list
  ERROR:root:No "nvidia-dkms-340" can be found.
  nvidia-340
  "

  1) Expected action - running 'ubuntu-drivers' lists NO drivers being
  available, as allowing drivers to be installed that the installer
  seems(?) to know are broken/will break things, is illogical.

  2) Improvements - I had access

[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled

2020-06-12 Thread Florian 'rephlex' Panzer

Some background: rechargeable batteries have 1.2V nominal (compared to
1.5V nominal for regular battteries). Any mouse will report levels
around 10%, although the batteries will run for *many* months.

So users of rechargeable batteries will experience notifications about
low levels basically after a few days of using a rechargeable battery.

Although you might very wel argue that "it's a hardware problem",
notifications about low mouse / keyboard battery should be optional, not
forced upon the user.

I have no way to disable the mouse / battery level alarm. (that is BUG
#1)

Furthermore, if i use DND (which i don't really want to use, but just
assumed), the mouse/keyboard alarms are the ONLY alarms that OVERRIDE
DND, to "using DND" is not a solution, and DND does in fact disturb in
some cases, which is BUG #2.

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

Title:
“Mouse battery low” notification can't be disabled

Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed

Bug description:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108

---

I have a wireless mouse powered by non-rechargeable battery. The mouse
works absolutely fine even with low battery level. Problem is, Ubuntu
gives notifications about the battery level all the time.

I have had this issue for almost two months now, and mouse is working
perfectly. I had to click away the notification almost every time I
moved the mouse. I was then able to make the notifications appear less
frequently, but the notification still always appear after some
interval, and always after I log in.

Here are some specific things I have tried, they have not helped.

https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
low-notification-in-ubuntu-18-04

1)
Description: Ubuntu 18.04.1 LTS
Release: 18.04

2)
I assume the packet in question is notify-osd, not sure.
notify-osd:
Installed: (none)
Candidate: 0.9.35+16.04.20160415-0ubuntu2
Version table:
0.9.35+16.04.20160415-0ubuntu2 500
500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

3) I expected that no notifications would appear when notifications
are set to off

4) Mouse battery low - notification always appears
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio
/dev/snd/controlC0: ohto 2927 F pulseaudio
/dev/snd/controlC1: ohto 2927 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-07-28 (79 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77X-UP5 TH-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled

2020-06-12 Thread Florian 'rephlex' Panzer

Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0
  native-path:  hidpp_battery_0
  model:MX Keys Wireless Keyboard
  serial:   408a-9b-b6-52-57
  power supply: no
  updated:  Fr 12 Jun 2020 22:39:07 CEST (8 seconds ago)
  has history:  yes
  has statistics:   yes
  mouse
present: yes
rechargeable:yes
state:   discharging
warning-level:   low
battery-level:   low
percentage:  10% (should be ignored)
icon-name:  'battery-caution-symbolic'


** Attachment added: "Screenshot of the notification"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+attachment/5383373/+files/Bildschirmfoto%20von%202020-06-12%2022-38-51.png

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

Title:
  “Mouse battery low” notification can't be disabled

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108

  ---

  I have a wireless mouse powered by non-rechargeable battery. The mouse
  works absolutely fine even with low battery level. Problem is, Ubuntu
  gives notifications about the battery level all the time.

  I have had this issue for almost two months now, and mouse is working
  perfectly. I had to click away the notification almost every time I
  moved the mouse. I was then able to make the notifications appear less
  frequently, but the notification still always appear after some
  interval, and always after I log in.

  Here are some specific things I have tried, they have not helped.

  https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery-
  low-notification-in-ubuntu-18-04

  1)
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2)
  I assume the packet in question is notify-osd, not sure.
  notify-osd:
    Installed: (none)
    Candidate: 0.9.35+16.04.20160415-0ubuntu2
    Version table:
   0.9.35+16.04.20160415-0ubuntu2 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) I expected that no notifications would appear when notifications
  are set to off

  4) Mouse battery low - notification always appears
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ohto   2927 F...m pulseaudio
   /dev/snd/controlC0:  ohto   2927 F pulseaudio
   /dev/snd/controlC1:  ohto   2927 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-07-28 (79 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1
  ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UP5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1825593] Re: Display scale not remembered when X11 Fractional Scaling is enabled

2020-06-12 Thread Cas

I don't think this is quite fixed.

I have my laptop display set to 2048x1152 and it connects fine to an
external monitor via thunderbolt running the full 2560x1440 resolution
but when disconnecting the display would reset to default 2560x1440
resolution with 200% scaling.

After reading this bug report about fractional scaling, I disabled the
option and now disconnecting the display from the laptop it returns to
my preferred 2048x1152 with 100% scaling.

I am using the latest mutter version:

dpkg -s libmutter-6-0 | grep Version
Version: 3.36.2-1ubuntu1~20.04.1

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

Title:
  Display scale not remembered when X11 Fractional Scaling is enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

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

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

[Desktop-packages] [Bug 1881007] Re: [SRU] libreoffice 6.4.4 for focal

2020-06-12 Thread Steve Langasek

libreoffice is not a package that has been identified as having a
microrelease exception according to
.
And the Test case listed here seems rather aspirational - "bugs fixed
upstream hopefully come with unit/regression tests".  Please speak
directly to how this update meets the standard for microrelease updates.

Also, it would help in terms of the justification of an SRU to have
clarity around what the bugs are that are worth fixing.  The only one
that I see referenced is LP: #1869561 - do you beileve this bug in
particular justifies taking the new upstream version?

** Changed in: libreoffice (Ubuntu Focal)
   Status: In Progress => Incomplete

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

Title:
  [SRU] libreoffice 6.4.4 for focal

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Focal:
  Incomplete

Bug description:
  [Impact]

   * LibreOffice 6.4.4 is in its fourth bugfix release of the 6.4 line. Version 
6.4.4 is currently in focal.
 For a list of fixed bugs compared to 6.4.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.4/RC2#List_of_fixed_bugs
 (that's a total of 98 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 98 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer

2020-06-12 Thread Stefano Dall'Agata

I tried to follow the proposed advice, but the installation process
loops.

-
| PLUG-IN INSTALLATION FOR HPLIP 3.20.3 |
-

The driver plugin for HPLIP 3.20.3 appears to already be installed.
Do you wish to download and re-install the plug-in? (y=yes*, n=no, q=quit) ? n
hp-plugin[5778]: debug: Unlocking: /home/stefano/.hplip/hp-plugin.lock
The program exited via sys.exit(). Exit status: 0
> /usr/share/hplip/plugin.py(23)()
-> __version__ = '2.1'
(Pdb) cont

(Note: Defaults for each question are maked with a '*'. Press  to
accept the default.)


-
| PLUG-IN INSTALLATION FOR HPLIP 3.20.3 |
-

The driver plugin for HPLIP 3.20.3 appears to already be installed.
Do you wish to download and re-install the plug-in? (y=yes*, n=no, q=quit) ?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  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: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

2020-06-12 Thread Ian Johnson

Also just to clarify, we will regenerate fontconfig cache's on any snap
refresh/install during the link-snap task.

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  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:

[Desktop-packages] [Bug 1883192] Re: [nouveau] Video mode 1600x1200 is missing

2020-06-12 Thread Karim BAKKAL

in /usr/share/X11/xorg.conf.d, there is only : 
10-amdgpu.conf
10-quirks.conf
10-radeon.conf
40-libinput.conf
51-synaptics-quirks.conf
70-synaptics.conf
70-wacom.conf

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

Title:
  [nouveau] Video mode 1600x1200 is missing

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  Video mode 1600x1200 is not present.

  In the file Xorglog.txt, we can see that it's extracted from the EDID
  but not present in the list of "modeline".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic i686
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: i386
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Jun 12 02:17:29 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c]
  InstallationDate: Installed on 2020-04-17 (55 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  MachineType: FUJITSU SIEMENS Amilo M3438 Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=f910d7c1-f499-455a-ade2-472c22149dcd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2005
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10C
  dmi.board.name: P71EN0
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10C:bd10/05/2005:svnFUJITSUSIEMENS:pnAmiloM3438Series:pvr:rvn:rnP71EN0:rvr:cvnFUJITSUSIEMENS:ct10:cvr:
  dmi.product.name: Amilo M3438 Series
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1883192/+subscriptions

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

[Desktop-packages] [Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s

2020-06-12 Thread Bug Watch Updater

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1882966] Re: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04

2020-06-12 Thread Samuel thibault

I guess this is due to the following change in at-spi2-atk:

* Meson: don't hard-code shared_library (!19).

which made meson emit a lot of new libraries in Requires.private of atk-
bridge-2.0.pc, and thus the -dev package now has to add them in Depends.

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

Title:
  Recent updates to some packages make it impossible to build an Orca
  Master in Ubuntu-MATE 20.04

Status in at-spi2-atk package in Ubuntu:
  Confirmed

Bug description:
  The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and
  libatk-adapter packages makes it impossible to build Orca Master in
  Ubuntu-MATE 20.04. Reproduction steps:

  1. You need to have Ubuntu-MATE 20.04 with the latest updates;

  2. Install the following packages:

  git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev
  libatspi2.0-dev libatk-bridge2.0-dev

  3. Clone the Orca repository:

  git clone https://gitlab.gnome.org/GNOME/orca.git

  4. Navigate to the cloned repository:

  cd orca

  5. Run the command:

  ./autogen.sh

  The command output ends with the following lines:

  checking for ATKBRIDGE... no
  configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:
  Package 'atk', required by 'atk-bridge-2.0', not found
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.
  Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS
  and ATKBRIDGE_LIBS to avoid the need to call pkg-config.
  See the pkg-config man page for more details.

  If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are
  forcibly downgraded to version 2.34.1-3, this error disappears.

  Many thanks for fixing this issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+subscriptions

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

[Desktop-packages] [Bug 1880806] Re: Statusbar preferences options aren't stored

2020-06-12 Thread Balazs Gyurak

Ah right makes sense! So I should have reported there in the first
place. The reason I was confused is I thought that *only* the status bar
problem concerned Gnome, not the preferences, but I see now that is not
the case.

Thanks!

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

Title:
  Statusbar preferences options aren't stored

Status in gedit:
  Unknown
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Hi,

  Since upgrading to Ubuntu 20.04, Gedit is unable to save preferences. By 
default, it came with the following:
  Display line numbers: on
  Display right margin: off
  Highlight current line: on
  Text wrapping: on

  I wanted to disable the first and third option, so I did. It works as
  long as gedit is open, but if I close and reopen it, the settings were
  reverted.

  Repro steps:
  1. Open gedit
  2. Toggle the "Highlight current line" preference
  3. Close gedit
  4. Open gedit again
  5. Observe that the "Highlight current line" preference is reverted to the 
original value

  Expected behavior
  Gedit persists preferences after closing & reopening

  Actual behavior:
  Gedit does not persist preferences after closing & reopening

  Workaround:
  Using gsettings seemed to do the trick. I've run:
  gsettings set org.gnome.gedit.preferences.editor highlight-current-line false
  gsettings set org.gnome.gedit.preferences.editor display-line-numbers false

  This persists the settings correctly, so I believe the bug is related
  to the UI.

  Additional information:
  OS: Ubuntu 20.04
  Package: /usr/bin/gedit
  Version: 3.36.2-0ubuntu1

  Thanks,
  Balazs

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 27 06:37:36 2020
  InstallationDate: Installed on 2018-11-05 (568 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to focal on 2020-05-22 (4 days ago)

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

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

[Desktop-packages] [Bug 1882966] Re: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04

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

** Changed in: at-spi2-atk (Ubuntu)
   Status: New => Confirmed

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

Title:
  Recent updates to some packages make it impossible to build an Orca
  Master in Ubuntu-MATE 20.04

Status in at-spi2-atk package in Ubuntu:
  Confirmed

Bug description:
  The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and
  libatk-adapter packages makes it impossible to build Orca Master in
  Ubuntu-MATE 20.04. Reproduction steps:

  1. You need to have Ubuntu-MATE 20.04 with the latest updates;

  2. Install the following packages:

  git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev
  libatspi2.0-dev libatk-bridge2.0-dev

  3. Clone the Orca repository:

  git clone https://gitlab.gnome.org/GNOME/orca.git

  4. Navigate to the cloned repository:

  cd orca

  5. Run the command:

  ./autogen.sh

  The command output ends with the following lines:

  checking for ATKBRIDGE... no
  configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:
  Package 'atk', required by 'atk-bridge-2.0', not found
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.
  Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS
  and ATKBRIDGE_LIBS to avoid the need to call pkg-config.
  See the pkg-config man page for more details.

  If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are
  forcibly downgraded to version 2.34.1-3, this error disappears.

  Many thanks for fixing this issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+subscriptions

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

[Desktop-packages] [Bug 1883306] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

2020-06-12 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: dpkg-
  deb --control subprocess returned error exit status 2

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  Pl check, what is problem?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  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
  CasperMD5CheckResult: skip
  Date: Fri Jun 12 10:19:54 2020
  DuplicateSignature:
   package:libjpeg-turbo8:2.0.3-0ubuntu1
   Unpacking libwinpr2-2:amd64 (2.1.1+dfsg1-0ubuntu0.20.04.1) over 
(2.0.0~git20190204.1.2693389a+dfsg1-2build2) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb'
 is not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883306/+subscriptions

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

[Desktop-packages] [Bug 1881966] Re: 1.22.10-1ubuntu2.1 Sporadic WiFi network disconnect after Ubuntu 18.04 -> 20.04

** Summary changed:

- 1.22.10-1ubuntu2.1 Sporadic WiFi network disconnect after upgrading from 
Ubuntu 18.04 to 20.04
+ 1.22.10-1ubuntu2.1 Sporadic WiFi network disconnect after Ubuntu 18.04 -> 
20.04

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

Title:
  1.22.10-1ubuntu2.1 Sporadic WiFi network disconnect after Ubuntu 18.04
  -> 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing, maintaining an
  ssh connection and simple tasks almost impossible. I find that the
  network disconnects and it does not re-connect until the successful
  finish of a wifi-scan. I don't know what triggers the initial
  disconnect, maybe the wpa_supplicant dbus performing a
  flush_object_timeout_handler. Fixing the BSSID does not seem to help
  since the disconnect is still triggered but the reconnect is not
  performed until a manual WiFi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi. I have tried reinstalling the drivers, but this has not
  helped.

  The network-manager package version: 1.22.10-1ubuntu2.1

  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/network-manager/+bug/1881966/+subscriptions

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

[Desktop-packages] [Bug 1883306] [NEW] package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

2020-06-12 Thread Siddique Akbar

Public bug reported:

Pl check, what is problem?

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libjpeg-turbo8 2.0.3-0ubuntu1
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
CasperMD5CheckResult: skip
Date: Fri Jun 12 10:19:54 2020
DuplicateSignature:
 package:libjpeg-turbo8:2.0.3-0ubuntu1
 Unpacking libwinpr2-2:amd64 (2.1.1+dfsg1-0ubuntu0.20.04.1) over 
(2.0.0~git20190204.1.2693389a+dfsg1-2build2) ...
 dpkg-deb: error: 
'/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb'
 is not a Debian format archive
 dpkg: error processing archive 
/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
  dpkg-deb --control subprocess returned error exit status 2
ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
InstallationDate: Installed on 2020-06-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: libjpeg-turbo
Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg-turbo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: dpkg-
  deb --control subprocess returned error exit status 2

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  Pl check, what is problem?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  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
  CasperMD5CheckResult: skip
  Date: Fri Jun 12 10:19:54 2020
  DuplicateSignature:
   package:libjpeg-turbo8:2.0.3-0ubuntu1
   Unpacking libwinpr2-2:amd64 (2.1.1+dfsg1-0ubuntu0.20.04.1) over 
(2.0.0~git20190204.1.2693389a+dfsg1-2build2) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb'
 is not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883306/+subscriptions

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

[Desktop-packages] [Bug 1881966] Re: 1.22.10-1ubuntu2.1 Sporadic WiFi network disconnect after upgrading from Ubuntu 18.04 to 20.04

** Summary changed:

- Sporadic WiFi network disconnect after upgrading from Ubuntu 18.04 to 20.04
+ 1.22.10-1ubuntu2.1 Sporadic WiFi network disconnect after upgrading from 
Ubuntu 18.04 to 20.04

** Description changed:

  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
- reconnects. It is so recurrent that it makes browsing and simple tasks
- almost impossible. My best guess is that this problem is a bug in the
- new NetworkManager, probably a blocking thread while network-manager
- performs a routine wifi-scan.
+ reconnects. It is so recurrent that it makes browsing, maintaining an
+ ssh connection and simple tasks almost impossible. I find that the
+ network disconnects and it does not re-connect until the successful
+ finish of a wifi-scan. I don't know what triggers the initial
+ disconnect, maybe the wpa_supplicant dbus performing a
+ flush_object_timeout_handler. Fixing the BSSID does not seem to help
+ since the disconnect is still triggered but the reconnect is not
+ performed until a manual WiFi-scan.
  
  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for
- WiFi.  Here is some information about the network.
+ WiFi. I have tried reinstalling the drivers, but this has not helped.
+ 
+ The network-manager package version: 1.22.10-1ubuntu2.1
+ 
+ Here is some information about the network.
  
  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --
  
  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--
  
  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.
  
  I am happy to provide any information necessary to resolve this issue. Thanks
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
-  [connection]
-  wifi.powersave = 2
+  [connection]
+  wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  1.22.10-1ubuntu2.1 Sporadic WiFi network disconnect after Ubuntu 18.04
  -> 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing, maintaining an
  ssh connection and simple tasks almost impossible. I find that the
  network disconnects and it does not re-connect until the successful
  finish of a wifi-scan. I don't know what triggers the initial
  disconnect, maybe the wpa_supplicant dbus performing a
  flush_object_timeout_handler. Fixing the BSSID does not seem to help
  since the disconnect is

[Desktop-packages] [Bug 1881966] Re: Sporadic WiFi network disconnect after upgrading from Ubuntu 18.04 to 20.04

** Summary changed:

- Sporadic network disconnect and re-connect during wifi-scan after upgrading 
from Ubuntu 18.04 to 20.04
+ Sporadic WiFi network disconnect after upgrading from Ubuntu 18.04 to 20.04

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

Title:
  Sporadic WiFi network disconnect after upgrading from Ubuntu 18.04 to
  20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/network-manager/+bug/1881966/+subscriptions

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

[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

2020-06-12 Thread Karl Meyer

Norbert, thank you for this list. Therein I found
https://askubuntu.com/a/1248018, which solved the issue for me to bring
my printer back to work with 20.04. Not a real solution, but for me a
practical workaround.

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

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Install HPLIP with `sudo apt-get install hplip-gui`
  3. Install all stuff to satisfy `hp-doctor` requirements by:

  sudo apt-get build-dep hplip
  sudo apt-get install build-essential libtool libtool-bin libcups2-dev 
cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2

  
  4. Run `hp-doctor` and `hp-check`

  Expected results:

  * `hp-doctor` ran successfully without errors 
  * `hp-check` ran successfully without errors

  Actual results:

  ```
  $ hp-doctor 

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Self Diagnse Utility and Healing Utility ver. 1.0
  ...
  Checking for Dependencies
  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
  ...
  --
  | PERMISSION |
  --

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing or 'cups' service is not running.
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 
  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 
  ...


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

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1
  ...
  ---
  | SUMMARY |
  ---

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing/incompatible 
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 

  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

  Total Errors: 3
  Total Warnings: 0

  
  Done.

  ```

  Note: many mentioned packages are already installed, Qt4 related
  packages are not installable:

  ```
  $ sudo apt-get install libcups2 libcups2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libcups2 is already the newest version (2.3.1-9ubuntu1.1).
  libcups2-dev is already the newest version (2.3.1-9ubuntu1.1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install gtk2-engines-pixbuf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install python3-pyqt4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-pyqt4

  $ sudo apt-get install python3-dbus.mainloop.qt
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-dbus.mainloop.qt
  E: Couldn't find any package by glob 'python3-dbus.mainloop.qt'
  E: Couldn't find any package by regex 'python3-dbus.mainloop.qt'
  ```

  Please consider to fix HPLIP package and support 20.04 LTS package
  base before 20.04.1 release!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May 30 12:25:39 2020
  InstallationDate: Installed on 2020-04-23 (36 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic

[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer

2020-06-12 Thread Karl Meyer

I managed to get my printer back to work in 20.04 by installing hplip
from ubuntu repo (3.20.3+dfsg0-2), and then following this hint to
install the hp-plugin:

https://askubuntu.com/a/1248018

I had to type "cont" and press return after the depicted command to
start the process.

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  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: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

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

2020-06-12 Thread Alexis

Public bug reported:

freeze on show applications menu.

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] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 12 11:34:08 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 605 [17aa:39fd]
InstallationDate: Installed on 2020-06-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:112b Acer, Inc EasyCamera
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81J2
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8dc8d3e5-254c-4aea-8f07-294a527b810c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 9HCN26WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32823WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad S130-14IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN26WW:bd07/09/2019:svnLENOVO:pn81J2:pvrLenovoideapadS130-14IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32823WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-14IGM:
dmi.product.family: ideapad S130-14IGM
dmi.product.name: 81J2
dmi.product.sku: LENOVO_MT_81J2_BU_idea_FM_ideapad S130-14IGM
dmi.product.version: Lenovo ideapad S130-14IGM
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

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


** Tags: amd64 apport-bug focal freeze 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/1883295

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  freeze on show applications menu.

  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] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 12 11:34:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 605 [17aa:39fd]
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:112b Acer, Inc EasyCamera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81J2
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=8dc8d3e5-254c-4aea-8f07-294a527b810c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2019
  dmi.bios.vendor: LENOVO

[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-12 Thread greg matthews

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

confirmed that I can't switch between the two modes HSP/HFP and A2DP
when using Sony CH-500 bluetooth headset.

Initially it was stuck at HSP/HFP but after some messing with
/etc/bluetooth/main.conf I got it to switch to A2DP but now it wont
switch back and the mic never shows up.

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

2020-06-12 Thread Ian Johnson

I can confirm I see the bug with seb128's reproducer. First I will
propose a spread test which demonstrates the issue so we don't see
regressions on this front, but also it's very curious to me that this
specific font:

fonts-noto-color-emoji

does not show up in the cache we generate but this font:

fonts-kiloji

do show up in the cache we generate. The spread test we have for this
functionality was using the latter so we didn't see this bug til now.

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

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Ian Johnson (anonymouse67)

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin

[Desktop-packages] [Bug 1883292] Re: Laptop not suspending on lid close after external monitors disconnected

2020-06-12 Thread Vadym Abramchuck

I'll try to keep my laptop in this state for few days in case I could
provide any further info.

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

Title:
  Laptop not suspending on lid close after external monitors
  disconnected

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9380 laptop with Type-C dock. There are two
  external monitors (DisplayPort) and USB mouse attached to the doc.

  Normally I disconnect the dock cable from the laptop, close the laptop lid 
and laptop suspends.
  However, sometimes it doesn't suspend.
  I can see the 'Lid closed.' message in systemd-logind log which is normally 
followed by a sleep.
  Once this happens, laptop no longer suspends on lid close until I restart 
Gnome session.
  Also, if I lock it, the screen goes black but the backlight does not turn off.

  I can put computer to a sleep from Gnome menu.

  I'm not sure if it's issue is specific to Type-C dock though. It
  happens rarely, maybe 1 of 20 times.

  It appears like gsd does not detect monitors disconnect event in some
  cases:

  abram@abram-laptop:~$ systemd-inhibit --list --mode=block 
  WHO   UID  USER  PID COMM   WHAT  
   WHY 
MODE 
  gdm   123  gdm   1977595 gsd-power  handle-lid-switch 
   External monitor attached or configuration changed recently 
block
  gdm   123  gdm   1977593 gsd-media-keys 
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling 
keypresses   block
  abram 1000 abram 779130  gsd-media-keys 
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling 
keypresses   block

  3 inhibitors listed.

  I've also seen a similar issue mentioned at askubuntu: 
https://askubuntu.com/questions/1196871/gnome-supend-on-laptop-lid-close-no-longer-works-since-19-10-upgrade
  The accepted answer involves killing gsd-power but that's more like a 
workaround than a fix; the same presumably happens when Gnome session is 
restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jun 12 19:19:35 2020
  InstallationDate: Installed on 2019-04-17 (421 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to focal on 2020-04-02 (70 days ago)

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

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

[Desktop-packages] [Bug 1883292] [NEW] Laptop not suspending on lid close after external monitors disconnected

2020-06-12 Thread Vadym Abramchuck

Public bug reported:

I have a Dell XPS 13 9380 laptop with Type-C dock. There are two
external monitors (DisplayPort) and USB mouse attached to the doc.

Normally I disconnect the dock cable from the laptop, close the laptop lid and 
laptop suspends.
However, sometimes it doesn't suspend.
I can see the 'Lid closed.' message in systemd-logind log which is normally 
followed by a sleep.
Once this happens, laptop no longer suspends on lid close until I restart Gnome 
session.
Also, if I lock it, the screen goes black but the backlight does not turn off.

I can put computer to a sleep from Gnome menu.

I'm not sure if it's issue is specific to Type-C dock though. It happens
rarely, maybe 1 of 20 times.

It appears like gsd does not detect monitors disconnect event in some
cases:

abram@abram-laptop:~$ systemd-inhibit --list --mode=block 
WHO   UID  USER  PID COMM   WHAT
 WHY 
MODE 
gdm   123  gdm   1977595 gsd-power  handle-lid-switch   
 External monitor attached or configuration changed recently 
block
gdm   123  gdm   1977593 gsd-media-keys 
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling 
keypresses   block
abram 1000 abram 779130  gsd-media-keys 
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling 
keypresses   block

3 inhibitors listed.

I've also seen a similar issue mentioned at askubuntu: 
https://askubuntu.com/questions/1196871/gnome-supend-on-laptop-lid-close-no-longer-works-since-19-10-upgrade
The accepted answer involves killing gsd-power but that's more like a 
workaround than a fix; the same presumably happens when Gnome session is 
restarted.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Jun 12 19:19:35 2020
InstallationDate: Installed on 2019-04-17 (421 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to focal on 2020-04-02 (70 days ago)

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

Title:
  Laptop not suspending on lid close after external monitors
  disconnected

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  I have a Dell XPS 13 9380 laptop with Type-C dock. There are two
  external monitors (DisplayPort) and USB mouse attached to the doc.

  Normally I disconnect the dock cable from the laptop, close the laptop lid 
and laptop suspends.
  However, sometimes it doesn't suspend.
  I can see the 'Lid closed.' message in systemd-logind log which is normally 
followed by a sleep.
  Once this happens, laptop no longer suspends on lid close until I restart 
Gnome session.
  Also, if I lock it, the screen goes black but the backlight does not turn off.

  I can put computer to a sleep from Gnome menu.

  I'm not sure if it's issue is specific to Type-C dock though. It
  happens rarely, maybe 1 of 20 times.

  It appears like gsd does not detect monitors disconnect event in some
  cases:

  abram@abram-laptop:~$ systemd-inhibit --list --mode=block 
  WHO   UID  USER  PID COMM   WHAT  
   WHY 
MODE 
  gdm   123  gdm   1977595 gsd-power  handle-lid-switch 
   External monitor attached or configuration changed recently 
block
  gdm   123  gdm   1977593 gsd-media-keys 
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling 
keypresses   block
  abram 1000 abram 779130  gsd-media-keys 
handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling 
keypresses   block

  3 inhibitors listed.

  I've also seen a similar issue mentioned at askubuntu: 
https://askubuntu.com/questions/1196871/gnome-supend-on-laptop-lid-close-no-longer-works-since-19-10-upgrade
  The accepted answer involves killing gsd-power but that's more like a 
workaround than a fix; the same presumably happens when Gnome session is 
restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64

[Desktop-packages] [Bug 1879776] Re: ubuntu 20 error mounting smb drive

2020-06-12 Thread Dan Streetman

fyi, this was an intentional upstream change, thanks @vtapia for
pointing me to the upstream wiki:

https://wiki.samba.org/index.php/Samba_4.11_Features_added/changed#SMB1_is_disabled_by_default

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

Title:
  ubuntu 20 error mounting smb drive

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  nautilus->other locations>windows network lists the shared disk I want
  to access. When I click on the name I get an errorbox: Unable to
  access location. Failed to mount windows share: Software caused
  connection abort.

  nautilus->other locations>Connect to server: smb://192.168.nnn.nnn
  gives the same errorbox.

  The shared disk is attached to my FritzBox router/modem.
  This works without problems in ubuntu 18 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 21:04:29 2020
  InstallationDate: Installed on 2020-04-20 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  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/1879776/+subscriptions

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

[Desktop-packages] [Bug 1881966] Re: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04

For troubleshooting, I have tried using a fixed BSSID, as proposed in
(https://blogs.gnome.org/dcbw/2016/05/16/networkmanager-and-wifi-
scans/), but the issue persists. While the BSSID is static, I still get
the sporadic disconnect, but there is no automatic re-connect. In fact,
there is no re-connect until I perform a manual wifi-scan, at which
point the network connection gets re-established.

I also tried disabling the NetworkManager as proposed here
(https://askubuntu.com/questions/230660/disabling-network-manager-gnome-
wireless-scanning-when-connected), but it did not help and just made the
desktop much buggier.

Please, let me know if there is any other information I should provide
to help resolve this bug. Thanks.

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

Title:
  Sporadic network disconnect and re-connect during wifi-scan after
  upgrading from Ubuntu 18.04 to 20.04

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi, I am getting this highly recurrent problem in which the network
  inadvertently 'disconnects' for a minute or two and then automatically
  reconnects. It is so recurrent that it makes browsing and simple tasks
  almost impossible. My best guess is that this problem is a bug in the
  new NetworkManager, probably a blocking thread while network-manager
  performs a routine wifi-scan.

  I'm using the r88x2bu network driver from the rtl88x2bu-dkms package
  for WiFi.  Here is some information about the network.

  $ nmcli c
  NAMEUUID  TYPE  DEVICE
  MIT SECURE  8b2ea417-ed65-4e36-a63e-a231344af87a  wifi  
wlx74ee2af4348b
  virbr0  96dd3046-b80c-4995-8b83-289b0fc363d9  bridgevirbr0
  MIT b2c5956d-b071-4d52-98c3-86852563d88e  wifi  --
  Wired connection 1  bfacd008-8aae-3219-b84f-6d5dc9f0d9fa  ethernet  --

  $ nmcli d
  DEVICE   TYPE  STATECONNECTION
  wlx74ee2af4348b  wifi  connectedMIT SECURE
  virbr0   bridgeconnectedvirbr0
  enp3s0   ethernet  unavailable  --
  lo   loopback  unmanaged--
  virbr0-nic   tun   unmanaged--

  I have attached the system logs, which have the NetworkManager and
  wpa_supplicant logging level set to DEBUG.

  I am happy to provide any information necessary to resolve this issue. Thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-02-01 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.22.10-1ubuntu2.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-27 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-05-28T00:00:40.294938
  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/network-manager/+bug/1881966/+subscriptions

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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

2020-06-12 Thread BloodyIron

But once I nicely kill the process, I not only can connect to the share,
I can still discover network shares. So, I don't really know how to
explain that.

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1881298] Re: Incorrect disk information is displayed after creating a new partition

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1641308, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1641308
   Partitions display wrong in gnome -disks - ok in gparted

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

Title:
  Incorrect disk information is displayed after creating a new partition

Status in GNOME Disks:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  After creating a new partition, GNOME Disks did not indicate whether
  or not the partition creation had succeeded. Instead, it indicated
  that several partitions had been destroyed, when this was not correct.

  I will describe the steps that lead to the issue:

  1. A disk divided into several ext4 and NTFS partitions existed.
  2. I shrank the last partition (NTFS) using Windows.
  3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space 
at the end of the disk.
  4. I instructed GNOME Disks to create a new ext4 logical partition using the 
dialog opened by the + symbol.
  5. The dialog disappeared without any indication of whether the operation had 
succeeded or not. At the same time, the disk graphic was updated (see 
screenshot in attachment). It said that the disk had only one partition (/) and 
the rest of the disk was free space. This implied that the operation had failed 
and all the other partitions had been destroyed.
  6. I tried closing and opening Disks, but it continued to indicate that most 
of the disk had been wiped.
  7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME 
System Monitor. The information there suggested that the existing partitions 
were intact and the new partition had been successfully created.
  8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new 
disk layout (see screenshot in attachment in comment below).

  I have not attempted to reproduce the issue as I cannot afford to risk
  damaging a hard disk in daily use.

  This behaviour is highly undesirable. Users who are informed that
  their hard disk has been wiped suffer greatly increased stress and in
  their panic may take irreversible actions in an attempt to remedy the
  situation.

  I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks
  utility itself does not seem to have a version number.

  I originally reported the issue upstream at GNOME
  (https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and
  they asked me to report the issue at Ubuntu instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1881298/+subscriptions

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

[Desktop-packages] [Bug 1878921] Re: USB 3 NVMe SSD dongle doesn't flip

@Cedric, any chance you would try the ppa build?

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

Title:
  USB 3 NVMe SSD dongle doesn't flip

Status in usb-modeswitch package in Ubuntu:
  In Progress

Bug description:
  I have a AM8180 AMicro adapter. It is an adapter for an M.2 SSD NVMe
  disk to USB 3. It works fine on Windows, but on Ubuntu, when I plug it
  in, the drive shows for a second then disappears. If I try to do fdisk
  or gparted, it seems to lock something and I can't shutdown the laptop
  (it is stuck on the Disk Management Unmounting step.

  My info:
  1) Release:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2) Package version:
  usb-modeswitch:
Installed: 2.5.2+repack0-2ubuntu3
Candidate: 2.5.2+repack0-2ubuntu3
Version table:
   *** 2.5.2+repack0-2ubuntu3 500
  500 http://th.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What I expect to happen:
  I expect the drive to stay mounted

  4) What happened instead:
  The disk is mounted then immediately unmount. Before I create the partitions 
in Windows, nothing mounted but the disk briefly appeared in the Disk Manager.

  
  Attached is my (filtered) syslog when I plug to the USB-C (notice the message 
advising to tell the developers about the model. Maybe it's just vendor info 
missing).

  I have modified 2 flags in /etc/usb_modeswitch.conf:
  - DisableSwitching=0 changed to 1
  - #SetStorageDelay=4 changed to un-commented
  then restarted. That didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1878921/+subscriptions

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

[Desktop-packages] [Bug 1863258] Re: [Snap] Install the widevine binary upon request in Chromium

I'm tentatively closing this bug, because despite the less-than-ideal
UX, the functionality is essentially already implemented upstream now.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

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

Title:
  [Snap] Install the widevine binary upon request in Chromium

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Use case :

  - Start a video on netflix.com ( with chrome/ubuntu user agent )
  - Get a mysterious Netflix Error saying your browser is not supported
  - Start Firefox and watch your video

  Solution :

  - Detects when browsing a website that may need widevine ( see how
  firefox team did )

  - ask user if he wants this non-free binary plugin

  - Run some script like
  https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
  would copy the widevine plugin in snap user directory

  Notes :

  To test if Widevine Works : https://bitmovin.com/demos/drm

  
  - Widevine versions and binary url from mozilla 
https://hg.mozilla.org/releases/mozilla-beta/file/default/toolkit/content/gmp-sources/widevinecdm.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863258/+subscriptions

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

[Desktop-packages] [Bug 1863258] Re: [Snap] Install the widevine binary upon request in Chromium

I can confirm chromium now automatically installs a local copy of
Widevine (in ~/.config/chromium/WidevineCdm), and this appears to work
both in the deb packages and in the snap. Only a restart is required to
enable the CDM. The version of Widevine can be checked by browsing to
chrome://components.

In my tests this works on amd64, but not on i386.

The UX isn't great because it's not discoverable, there's no user
feedback and a manual restart is required, as opposed to the way Firefox
handles it, but it's nevertheless a big step forward.

I wonder whether this might be a consequence of 
https://chromium.googlesource.com/chromium/src/+/b5e9a646f5ac2eee57fb0c8cc545f18aa50bd994
 ?
Although Michel you said it started happening with chromium 81 ?

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

Title:
  [Snap] Install the widevine binary upon request in Chromium

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Use case :

  - Start a video on netflix.com ( with chrome/ubuntu user agent )
  - Get a mysterious Netflix Error saying your browser is not supported
  - Start Firefox and watch your video

  Solution :

  - Detects when browsing a website that may need widevine ( see how
  firefox team did )

  - ask user if he wants this non-free binary plugin

  - Run some script like
  https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
  would copy the widevine plugin in snap user directory

  Notes :

  To test if Widevine Works : https://bitmovin.com/demos/drm

  
  - Widevine versions and binary url from mozilla 
https://hg.mozilla.org/releases/mozilla-beta/file/default/toolkit/content/gmp-sources/widevinecdm.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863258/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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

2020-06-12 Thread Dimitri John Ledkov

** Tags removed: md5sum

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

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 1327801] Re: Bightness and contrast settings have no effect

2020-06-12 Thread Michael Glaz

I have the CanonScan LiDE 60 Scanner which I've had for a very long
time. The SimpleScan software always worked great out of the box with
this scanner...until I upgraded to Ubuntu 20.04. And now, neither the
brightness nor the contrast sliders have any effects on my scans.

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

Title:
  Bightness and contrast settings have no effect

Status in simple-scan package in Ubuntu:
  Triaged

Bug description:
  Scanner: Canon, Inc. CanoScan N1240U/LiDE 30
  Ubuntu 14.04, Simple Scan version 3.12.1.

  Adjusting the settings of brightness and contrast has no effect.

  With the default for scanning in "text" mode being too bright, this makes 
"Simple Scan" in text mode unusable for me.
  Brightness and contrast settings don't work in "foto" mode, too. But the 
default of the foto mode is usable.

  Brightness setting does work in program "Skanlite".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions

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

[Desktop-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301

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

** Changed in: gnome-session (Ubuntu)
   Status: New => Triaged

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

Title:
  System shutdown directly by pressing power button and releasing
  immediately on Dell Vostro 5301

Status in OEM Priority Project:
  In Progress
Status in gnome-session package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)

2020-06-12 Thread haldrik

I have this same bug in my system even when I had Ubuntu 19.10, the
upgrade to Ubuntu 20.04 didn't resolved the problem.

My only clue is that this could be a problem with Dropbox, but I'm not
sure because I disabled libnautilus-dropbox.so.bak versions 2.0 and 3.0
renaming the file, that's made the Dropbox menu to disappear of
Nautilus, but the crash with SIGSEGV after a clean start of the computer
it's still happening.

SegvAnalysis and Strace: 
https://i.postimg.cc/FzpCG0Rp/Captura-de-pantalla-de-2020-06-12-09-47-13.png
https://i.postimg.cc/K8wq9GZ6/Captura-de-pantalla-de-2020-06-12-09-47-43.png
https://i.postimg.cc/k4djmTRw/Captura-de-pantalla-de-2020-06-12-09-48-22.png
https://i.postimg.cc/3JbnR8Dk/Captura-de-pantalla-de-2020-06-12-09-48-55.png

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

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  after turn on pc

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 25 01:52:06 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-12-22 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax
   PC (0x7f3fb437f962) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection

https://bugs.chromium.org/p/chromium/issues/detail?id=1039560#c14
suggests that this should be fixed in the latest 83 stable update.

Would you mind testing that update from https://launchpad.net
/~canonical-chromium-builds/+archive/ubuntu/stage and reporting whether
the issue persists?

I'd recommend disabling that PPA after the test, the updates will
eventually be available in the Ubuntu archive.

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

Title:
  Chromium 81.0.4044.122 crashes on remote ssh connection

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chromium crash on a ssh x forwarding connection

  It crashes on both 18.04 and 16.04 with the same message.
  The X forwarding is working for other programs just fine.

  It was working until last update.

  Here is the message from the console on the crash

  [22765:22781:0506/144206.193243:FATAL:gpu_data_manager_impl_private.cc(439)] 
GPU process isn't usable. Goodbye.
  Trace/breakpoint trap (core dumped)

  Steps to repeat:
  ssh ltcd-prod
  chromum-browser

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 81.0.4044.122-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs 
minix ntfs msdos jfs xfs libcrc32c cpuid veth iptable_filter bpfilter bridge 
stp llc binfmt_misc intel_powerclamp coretemp kvm_intel kvm irqbypass zfs 
zunicode zavl icp ipmi_ssif gpio_ich crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel zcommon znvpair spl zlua aesni_intel aes_x86_64 crypto_simd 
cryptd glue_helper intel_cstate ast drm_vram_helper ttm drm_kms_helper lpc_ich 
drm joydev input_leds fb_sys_fops syscopyarea sysfillrect sysimgblt ipmi_si 
ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel lp parport nfsd auth_rpcgss 
nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic igb uas 
usbhid ahci i2c_algo_bit hid libahci usb_storage dca i2c_ismt
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768 800x600 800x600 640x480
  Date: Wed May  6 14:37:46 2020
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstalledPlugins:
   
  Load-Avg-1min: 0.55
  Load-Processes-Running-Percent:   0.1%
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb'
  MachineType: Supermicro A1SAi
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic 
root=UUID=c75e8c2a-b85d-444e-b278-16fd90c327e7 ro 
usb_storage.quirks=0bc2:331a:u,0bc2:ab31:u,0bc2:ab34:u
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.1a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A1SRi
  dmi.board.vendor: Supermicro
  dmi.board.version: 123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 18
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1a:bd08/27/2015:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SRi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.:
  dmi.product.family: SMC X10
  dmi.product.name: A1SAi
  dmi.product.sku: 081315D9
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877173/+subscriptions

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

[Desktop-packages] [Bug 1881040] Re: [snap] chromedriver does not download where configured

I have managed to reproduce the problem, I'm attaching a test script
that attempts to download a file to a location that's not permitted by
snapd's strict confinement.

What happens is that the chromium snap is strictly confined, so it can't
write files anywhere on the filesystem. In my test I'm setting the
downloadPath to $HOME/.local, and the resulting apparmor denial is:

  juin 12 16:35:24 bribon audit[35815]: AVC apparmor="DENIED"
operation="mknod" profile="snap.chromium.chromedriver"
name="/home/osomon/.local/linux-5.7.2.tar.xz.crdownload" pid=35815
comm="ThreadPoolForeg" requested_mask="c" denied_mask="c" fsuid=1000
ouid=1000

I'm afraid you will need to update your tests to download files
somewhere they can be written (anywhere in your home directory that's
not a hidden folder, or under /media or /mnt, for example).

** Attachment added: "download-test.py"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881040/+attachment/5383275/+files/download-test.py

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [snap] chromedriver does not download where configured

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I've recently been forced to upgrade to the SNAP based chromium setup.
  After being required to work through reconfiguring my $HOME, learn of
  the need to set up $XAUTHORITY I just now discovered that none of my
  Selenium based download tests work because the SNAP setup insists on
  downloading to:

  /home/xxx/snap/chromium/1165/Downloads

  rather than where the chromederiver download settings have been
  configured. Is there a way to override this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881040/+subscriptions

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

[Desktop-packages] [Bug 1881918] Re: Update GNOME Software to 3.36.1 in Focal

2020-06-12 Thread Ken VanDine

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Update GNOME Software to 3.36.1 in Focal

Status in One Hundred Papercuts:
  New
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Please, consider updating the deb version of GNOME Software to 3.36.1
  in Ubuntu 20.04. The 3.36.1 release has some important bug fixes,
  translation updates and other things.

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

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

[Desktop-packages] [Bug 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

Confirmed by doing those steps on a focal system

($ sudo apt install fonts-noto-color-emoji
if you don't have it installed)

$ fc-cat /var/cache/fontconfig/* | grep NotoColorE
there is a result listed

"NotoColorEmoji.ttf" 0 "Noto Color
Emoji:familylang=en:style=Regular:stylelang=en:fullname=Noto Color ...

$ sudo rm -rf /var/cache/fontconfig/
$ sudo snap refresh --edge core
(there is probably a smarter way to trigger a fontconfig cache refresh from 
snapd but that did it)

$ fc-cat /var/cache/fontconfig/* | grep NotoColorE
-> not NotoColorEmoji.ttf result anymore

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo

[Desktop-packages] [Bug 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

** Tags added: rls-ff-incoming

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  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:bvrN2JET73W(1.51):bd07/18/2019:svnLENOVO:pn20Q0CTO1WW:pvrThinkPadX390:rvnLENOVO:rn20Q0CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family:

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

Upstream reference
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/294

@Hui, do you have any other pending changes for G-serie before we do an
upload?

There are also several fixes in the review queue for focal, do you think
we have enough to do another SRU round or do you have more fixes you are
working on? (also bionic is going to need an upload once bug #1881094 is
sorted out)

** Changed in: pulseaudio (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: pulseaudio (Ubuntu Groovy)
   Importance: Undecided => High

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

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  This bug originates from an OEM private bug #1875597, then ubuntu
  users reported 2 public bugs #1871329 and #1881659. The 2nd issue of
  #1871329 and the 1st issue of #1881659 have the same root cause as
  #1875597

  [Impact]
  On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.

  [Fix]
  The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.

  [Test Case]
  applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions

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

[Desktop-packages] [Bug 1883015] Re: [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

2020-06-12 Thread Ken VanDine

** Summary changed:

- [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2
+ [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Focal:
  Triaged
Status in vte2.91 source package in Focal:
  Triaged
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in vte2.91 source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

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

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

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

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

[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

2020-06-12 Thread Angela Piotrowski

** Tags added: rls-ff-incoming

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed

Bug description:
  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  
  When using the nouveau drivers, the orientation is applied correctly in gnome 
settings, and is persisted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ77
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: SZ77
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle 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
  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-control-center/+bug/1874567/+subscriptions

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

[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1

2020-06-12 Thread Andreas Hasenack

This will only get better once another discovery service is used, since
SMB1 won't come back.

https://github.com/christgau/wsdd is something we could look into

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

Title:
  gvfs can't list shares from smb servers that disabled SMB1

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  After bug #1778322 is fixed (just needs a gvfs rebuild with newer
  samba), samba machines will start to show up again in the "windows
  network" tab in nautilus. But if a server has disabled the SMB1
  protocol, nautilus will show an error when that server is clicked on,
  instead of showing the shares list.

  Even with SMB1 disabled, it should still be technically possible to
  get a share list, since smbclient can do it:

  andreas@nsnx:~$ nmblookup -A 192.168.122.101
  Looking up status of 192.168.122.101
D-NO-SMB1   <00> - B  
D-NO-SMB1   <03> - B  
D-NO-SMB1   <20> - B  
..__MSBROWSE__. <01> -  B  
WORKGROUP   <00> -  B  
WORKGROUP   <1d> - B  
WORKGROUP   <1e> -  B  

  MAC Address = 00-00-00-00-00-00

  andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
  WARNING: The "syslog" option is deprecated

Sharename   Type  Comment
-     ---
print$  Disk  Printer Drivers
pub_no_smb1 Disk  
IPC$IPC   IPC Service (d-no-smb1 server (Samba, Ubuntu))
  Reconnecting with SMB1 for workgroup listing.
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
  Failed to connect with SMB1 -- no workgroup available

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
NT1
  WARNING: The "syslog" option is deprecated
  protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE

  andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m 
SMB2
  WARNING: The "syslog" option is deprecated
  Try "help" to get a list of possible commands.
  smb: \> dir
.   D0  Fri May  3 18:16:38 2019
..  D0  Fri May  3 18:15:24 2019
hello.txt   N   21  Fri May  3 18:16:12 2019
hello-from-nsnx.txt A9  Fri May  3 18:16:38 2019

  20509264 blocks of size 1024. 13121800 blocks
  available

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

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

[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

** Changed in: pulseaudio (Ubuntu Groovy)
   Status: Incomplete => In Progress

** Changed in: pulseaudio (Ubuntu Focal)
   Status: Incomplete => In Progress

** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  In Progress

Bug description:
  This bug originates from an OEM private bug #1875597, then ubuntu
  users reported 2 public bugs #1871329 and #1881659. The 2nd issue of
  #1871329 and the 1st issue of #1881659 have the same root cause as
  #1875597

  [Impact]
  On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.

  [Fix]
  The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.

  [Test Case]
  applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions

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

[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

@Daniel, it would tell us if the users having the problem use xorg or
wayland and also having at least a journal log from someone who had the
issue would tell us if there is any warning printed at the time. Or do
you have an idea what the issue is? (in which case maybe dump some
details in the report?)

how often does it happen? how do you trigger it?

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

Title:
  Gnome Shell clock is truncated/corrupt on the right side

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When clock changes value, it doesn't displaying time properly

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

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

[Desktop-packages] [Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen

2020-06-12 Thread SchnippenSchnappen

The folder was completely empty (I checked with ls -lsah) but I deleted
it anyway and restarted.

gsettings list-recursively org.gnome.shell > settings.txt however still
produces the same output.

I guess that some of those "residue" gnome extensions might be causing
the bug I reported however I am now more concerned that there seemingly
extensions enabled that neither show up in the extensions settings nor
in the extensions folder. Also shouldn't the default extensions be
listed under "org.gnome.shell enabled-extensions" as well?

Do you know where gsettings is pulling the list of enabled extensions
from? Maybe I can dig down from there and get to the bottom of this.

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

Title:
  Ubuntu Dock and Top bar accessible from lockscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This is a very serious security issue:

  When I lock my desktop with SUPER (windows) + L my screen gets locked
  and goes to black. Sometimes when I return to my PC and move my mouse
  to turn my screen back on I notice that the Ubuntu Dock + the Top Bar
  are accessible from the lockscreen.

  I unfortunately can't remember if they were accessible from the moment
  I locked the screen or became accessible after returning from fade to
  black. (This is not the first time this issue happened.)

  I was able to open the settings menu from the top bar and use all
  indicators. You can actually start the programs in the Ubuntu Dock and
  give keyboard inputs to them. For example I was able to start the
  terminal emulator from the lock screen and run firefox and other
  applications. So an attacker could run arbitrary commands with user
  privileges from the lockscreen!

  The indicators drop down menus were fully visible on the lock screen
  while the Dock applications remained hidden "behind" the lockscreen
  (however still accessible via keyboard as described above).

  I have attached a screenshot of the bug. I unfortunately had no camera
  at hand to film me running terminal commands.

  Please contact me if you need additional information.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 13:35:28 2020
  InstallationDate: Installed on 2015-12-22 (1627 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719

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

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

[Desktop-packages] [Bug 1883155] Re: Vino advertises TLS even when require-encryption is false

Thanks, I'm sharing the url know as well since that can be useful to
check the status,

https://gitlab.gnome.org/GNOME/vino/-/issues/12

** Bug watch added: gitlab.gnome.org/GNOME/vino/-/issues #12
   https://gitlab.gnome.org/GNOME/vino/-/issues/12

** Changed in: vino (Ubuntu)
   Status: New => Triaged

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

Title:
  Vino advertises TLS even when require-encryption is false

Status in vino package in Ubuntu:
  Triaged

Bug description:
  I have an old Xubuntu system which I administer remotely from a
  Windows machine using UltraVNC. This doesn't support encryption, but
  since it's on a local net this is acceptable, and it has worked fine
  for years.

  I have just installed Xubuntu 20.04 on a new machine, and have
  installed Vino from the repository and configured it using gsettings
  to the same values as on my old system. The settings are as follows:

  org.gnome.Vino prompt-enabled false
  org.gnome.Vino require-encryption false
  org.gnome.Vino use-alternative-port false
  org.gnome.Vino disable-background false
  org.gnome.Vino disable-xdamage false
  org.gnome.Vino alternative-port uint16 5900
  org.gnome.Vino icon-visibility 'client'
  org.gnome.Vino authentication-methods ['vnc']
  org.gnome.Vino network-interface ''
  org.gnome.Vino notify-on-connect true
  org.gnome.Vino mailto ''
  org.gnome.Vino lock-screen-on-disconnect false
  org.gnome.Vino use-upnp false
  org.gnome.Vino vnc-password 'xx=='
  org.gnome.Vino view-only false

  When I start the server, this is what I see:

  10/06/2020 20:25:40 WARNING: Width (1366) is not a multiple of 4. VncViewer 
has problems with that.
  10/06/2020 20:25:40 Autoprobing TCP port in (all) network interface
  10/06/2020 20:25:40 Listening IPv6://[::]:5900
  10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900
  10/06/2020 20:25:40 Autoprobing selected port 5900
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP 
port 5900 in (all) interface
  10/06/2020 20:25:40 Listening IPv6://[::]:5900
  10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900
  10/06/2020 20:25:40 Clearing securityTypes
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Clearing securityTypes
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Advertising authentication type: 'No Authentication' (1)
  10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP 
port 5900 in (all) interface
  10/06/2020 20:25:40 Listening IPv6://[::]:5900
  10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900
  10/06/2020 20:25:40 Clearing securityTypes
  10/06/2020 20:25:40 Clearing authTypes
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Advertising authentication type: 'VNC Authentication' (2)
  10/06/2020 20:28:21 [IPv4] Got connection from client xxx
  10/06/2020 20:28:21   other clients:
  10/06/2020 20:28:21 WARNING: New width (1366) is not a multiple of 4.
  10/06/2020 20:28:21 Client Protocol Version 3.4
  10/06/2020 20:28:21 Ignoring minor version mismatch
  10/06/2020 20:28:21 rfbClientConnFailed("No security type suitable for RFB 
3.3 supported")
  10/06/2020 20:28:21 Client xxx gone

  Note that it says "Advertising security type: 'TLS' (18)" even though
  I have set "org.gnome.Vino require-encryption" to false. And as a
  result, I can't connect from my Windows box.

  Can anyone tell me what to do to fix this?

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

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

[Desktop-packages] [Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)

2020-06-12 Thread Dean Henrichsmeyer

I rebooted last night for a new kernel. This morning the monitors were
on with nothing but a cursor on the screen again. Attached is the
journal output.

** Attachment added: "lastboot.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+attachment/5383262/+files/lastboot.log.gz

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

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

Title:
  Displays wake up pre-maturely (likely driven by notification)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After a period of time, my displays go to sleep as they should.
  However, I often come back to find that the displays are awake, the
  mouse pointer is on a screen, but the screens are otherwise black.
  They're in this weird "awake but not fully on" mode. At that point,
  they will not go back to sleep as they should unless I fully awake
  them and let them go back to sleep.

  I don't know exactly what triggers the "half awake" but I suspect it's
  a notification. The displays shouldn't turn on without a user action.
  It wastes power and is clearly broken. I've attached a photo for an
  example.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  7 16:10:20 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-07-24 (684 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-07 (152 days ago)

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

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

[Desktop-packages] [Bug 1858636] Re: color emoji not rendered; many bw emoji rendered as boxes

** Changed in: snapd (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- color emoji not rendered; many bw emoji rendered as boxes
+ snapd generated incomplete fontconfig caches, result in emoji rendering issue 
in chromium

** Summary changed:

- snapd generated incomplete fontconfig caches, result in emoji rendering issue 
in chromium
+ snapd generates incomplete fontconfig caches, result in emoji rendering issue 
in chromium

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not

[Desktop-packages] [Bug 1883253] [NEW] no Multi-Arch support

2020-06-12 Thread Stephan Lachnit

Public bug reported:

@seb128 please rebase gamemode against the Debian version 1.5.1-4 and
include Multi-Arch support. There are a lot of upstream bug reports
because 32bit support is missing in Ubuntu.

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

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

Title:
  no Multi-Arch support

Status in gamemode package in Ubuntu:
  New

Bug description:
  @seb128 please rebase gamemode against the Debian version 1.5.1-4 and
  include Multi-Arch support. There are a lot of upstream bug reports
  because 32bit support is missing in Ubuntu.

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

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

[Desktop-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation

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

** Changed in: shared-mime-info (Ubuntu)
   Status: New => Confirmed

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

Title:
  Update-mime-database is getting very slow during apps installation

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The installation of some apps has become very slow due to the update-
  mime-database command that takes up a lot of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 22:37:53 2019
  InstallationDate: Installed on 2019-01-16 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shared-mime-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions

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

[Desktop-packages] [Bug 1882112] Re: [radeon] Screen freeze

2020-06-12 Thread Robin

UPDATE: 11h41GMT Fri 12 Jun 2020  Rob Jarvis:  Freeze occured again today, 
second time since original report.  This time I was able to Alt+F2 and switch 
into the desktop in focus in the 4-part desktop 'palette' view.  This killed 
the freeze. The freeze seems to be associated with 2 factors which may be 
related, or not:

1) a having desktop with windows which overlap out of the visible area.
When swithcing into dektop palette mode the previously out of sight bits
of the windows in the one desktop then show as overlapping into the
adjacent desktops in the palette view (clearly all 4 are mapped into the
same large pixel space).

If I try to tidy up the overlaps in the palette view I am likely to hit
a freeze. If I return to the single desktop and tidy up the windows by
reducing their size and ensure all fit into the active desktop, then
return to the palette view, I can then shuffle the smaller windows from
one desktop to another without hitting a freeze, unless...

2)... I drag a window diagonally, say from Top-left to bottom right, so that 
the subject window traverses more than 2 desktop areas.  Then I am more leikely 
to see the freeze... it seems.  If I drag a desktop completely from that top 
left to top right and then wholly from there to bottom right it seems to stay 
well behaved and doesn't freeze.. so far.
==> END OF UPDATE 11h41GMT Fri 12 Jun 2020

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

Title:
  [radeon] Screen freeze

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

Bug description:
  This may be correlated to the move to Bionic Beaver(?) LTS, now
  18.04.4.  It may also be correlated to getting low on disk space on my
  system drive (50GB SSD) and putting pressure on swap space. e.g when
  system HDD <= 1GB.   My secondary HDD is a 1TB USB spinning device
  that sometimes seems to go into sleep mode and then fails to rapidly
  respond to IO request or may be is in a 'hot IO' state. On my Bus I
  have a low capacity HDD that is essentially unused because it rarely
  comes ready when I boot.  If it is partially alive it is conceivable
  that it might be chattering and so competing for IO interrupt handling
  bandwidth?

  The problem only occurs when I have selected the desktop management
  tile from the 'side tray' and if I then shuffle or better align the
  windows inside one of the four desktops so as to stop them running
  into the neighbouring desktop area. Particularly, it seems to me, when
  at least one of the desktops is quite busy with windows open in it and
  the overlapped desktop has a few also.  The fewer windows in total
  across the desktops the less likely it seems that rearranging a few
  will have any bad effect.

  When the freeze occurs then 60%(?) of the time it ends in a 'big red
  switch' reboot.  The cursor stays active but ineffective.  Keyboard
  combinations, like Alt+W, will sometimes succeed in bringing up to
  full screen mode and active the desktop that was in focus and
  constitutes a recovery.  Other times, and keys, will delete focussed
  windows in the focussed desktop, and Tab will move focus around the 4
  desktops.  SHIFT+Print Screen also executes but just takes the whole
  screen and dumps it somewhere I haven't yet located... with sound
  effect.

  Hope this helps... I am not at fully at home with Ubuntu/Linux yet... having 
spent a lifetime on glasshouse legacy IBM mainframe field systems engineering.  
I am making myself more system disk space meanwhile, and while extract my old 
Maxtor.  It would be nice if I didn't have to up my system disk to hundreds of 
GB!   
  best regards,
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Jun  4 11:31:56 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7480D] [1043:8526]
  InstallationDate: Installed on 2016-11-27 (1284 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic

[Desktop-packages] [Bug 1883236] Re: Clock keep running even though the board is solved

2020-06-12 Thread Chris Guiver

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

apport-collect 1883236

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

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

Title:
  Clock keep running even though the board is solved

Status in gnome-mines package in Ubuntu:
  New

Bug description:
  Sometimes when I solve a game, the clock will keep running when the
  game is over, even though all mines are found.

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

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

[Desktop-packages] [Bug 1883236] [NEW] Clock keep running even though the board is solved

2020-06-12 Thread Terje Kristensen

Public bug reported:

Sometimes when I solve a game, the clock will keep running when the game
is over, even though all mines are found.

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

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

Title:
  Clock keep running even though the board is solved

Status in gnome-mines package in Ubuntu:
  New

Bug description:
  Sometimes when I solve a game, the clock will keep running when the
  game is over, even though all mines are found.

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

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

[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264

2020-06-12 Thread knossos456

Ok.

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

Title:
  Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i
  H.264

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  uname -a
  Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  inxi -G
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 
240/340 OEM]
 Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 
1920x1080@60.00hz
 OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 
9.0.0) version: 4.5 Mesa 19.2.8

  For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen
  (top) compressed image.

  To solve the default, i have to revert via synaptic the package mesa-
  va-driver to 19.0.8.

  Other solution is to take nighty builds as complete mesa package via : 
  https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers   that works 
too and is at mesa 20.1 git

  Please correct the problem to the official Ubuntu repos.

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

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

[Desktop-packages] [Bug 1862308] Re: Desktop wallpaper is slightly blurry

But first...

Patch to groovy proposed: https://salsa.debian.org/gnome-
team/mutter/-/merge_requests/65

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

Title:
  Desktop wallpaper is slightly blurry

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Desktop wallpaper is slightly blurry in Gnome 3.34 and 3.36

  Upstream fix pending:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Feb  7 16:08:58 2020
  DisplayManager:

  InstallationDate: Installed on 2020-02-03 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  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/mutter/+bug/1862308/+subscriptions

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

[Desktop-packages] [Bug 1880086] Re: [nvidia+xorg] High latency while running gtk4 demos like Fishbowl

or https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1284

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

Title:
  [nvidia+xorg] High latency while running gtk4 demos like Fishbowl

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  High latency while running gtk4 demos like Fishbowl, using the Nvidia
  driver (on Xorg)

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

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

[Desktop-packages] [Bug 1883155] Re: Vino advertises TLS even when require-encryption is false

2020-06-12 Thread Phssthpok

Done.

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

Title:
  Vino advertises TLS even when require-encryption is false

Status in vino package in Ubuntu:
  New

Bug description:
  I have an old Xubuntu system which I administer remotely from a
  Windows machine using UltraVNC. This doesn't support encryption, but
  since it's on a local net this is acceptable, and it has worked fine
  for years.

  I have just installed Xubuntu 20.04 on a new machine, and have
  installed Vino from the repository and configured it using gsettings
  to the same values as on my old system. The settings are as follows:

  org.gnome.Vino prompt-enabled false
  org.gnome.Vino require-encryption false
  org.gnome.Vino use-alternative-port false
  org.gnome.Vino disable-background false
  org.gnome.Vino disable-xdamage false
  org.gnome.Vino alternative-port uint16 5900
  org.gnome.Vino icon-visibility 'client'
  org.gnome.Vino authentication-methods ['vnc']
  org.gnome.Vino network-interface ''
  org.gnome.Vino notify-on-connect true
  org.gnome.Vino mailto ''
  org.gnome.Vino lock-screen-on-disconnect false
  org.gnome.Vino use-upnp false
  org.gnome.Vino vnc-password 'xx=='
  org.gnome.Vino view-only false

  When I start the server, this is what I see:

  10/06/2020 20:25:40 WARNING: Width (1366) is not a multiple of 4. VncViewer 
has problems with that.
  10/06/2020 20:25:40 Autoprobing TCP port in (all) network interface
  10/06/2020 20:25:40 Listening IPv6://[::]:5900
  10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900
  10/06/2020 20:25:40 Autoprobing selected port 5900
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP 
port 5900 in (all) interface
  10/06/2020 20:25:40 Listening IPv6://[::]:5900
  10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900
  10/06/2020 20:25:40 Clearing securityTypes
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Clearing securityTypes
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Advertising authentication type: 'No Authentication' (1)
  10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP 
port 5900 in (all) interface
  10/06/2020 20:25:40 Listening IPv6://[::]:5900
  10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900
  10/06/2020 20:25:40 Clearing securityTypes
  10/06/2020 20:25:40 Clearing authTypes
  10/06/2020 20:25:40 Advertising security type: 'TLS' (18)
  10/06/2020 20:25:40 Advertising authentication type: 'VNC Authentication' (2)
  10/06/2020 20:28:21 [IPv4] Got connection from client xxx
  10/06/2020 20:28:21   other clients:
  10/06/2020 20:28:21 WARNING: New width (1366) is not a multiple of 4.
  10/06/2020 20:28:21 Client Protocol Version 3.4
  10/06/2020 20:28:21 Ignoring minor version mismatch
  10/06/2020 20:28:21 rfbClientConnFailed("No security type suitable for RFB 
3.3 supported")
  10/06/2020 20:28:21 Client xxx gone

  Note that it says "Advertising security type: 'TLS' (18)" even though
  I have set "org.gnome.Vino require-encryption" to false. And as a
  result, I can't connect from my Windows box.

  Can anyone tell me what to do to fix this?

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

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

[Desktop-packages] [Bug 1858636] Re: color emoji not rendered; many bw emoji rendered as boxes

Marius, that last comment is a very interesting data point. I'm adding a
snapd task to the bug.

** 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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1858636

Title:
  color emoji not rendered; many bw emoji rendered as boxes

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  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:

[Desktop-packages] [Bug 1858636] Re: color emoji not rendered; many bw emoji rendered as boxes

Yes I was thinking this sounds like a font cache problem. Perhaps unique
to Ubuntu? I couldn't find anything like it reported against Chromium
upstream.

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

Title:
  color emoji not rendered; many bw emoji rendered as boxes

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  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:

[Desktop-packages] [Bug 1880086] Re: [nvidia+xorg] High latency while running gtk4 demos like Fishbowl

New upstream fix:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1309

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

Title:
  [nvidia+xorg] High latency while running gtk4 demos like Fishbowl

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  High latency while running gtk4 demos like Fishbowl, using the Nvidia
  driver (on Xorg)

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

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

[Desktop-packages] [Bug 1883144] Re: Can't connect to ProtonVPN (probably VPN in general)

2020-06-12 Thread Łukasz Konieczny

I must add, that I'm able to connect to this VPN using openvpn command.
So this has to be a bug in NetworkManager.

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

Title:
  Can't connect to ProtonVPN (probably VPN in general)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.4.0-37-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz
  Memory: 15,6 GiB

  network-manager version: 1.22.10-1ubuntu2.1

  What happens?

  I want to connect to VPN, no matter how I am doing so, be it using Plasma 
applet or via terminal (nmcli connection up se.protonvpn.com.udp), I can't. On 
the 4th June 2020 there was a network-manager update, and probably since this 
day I can't connect to VPN. Previously I could do so. Of course I have 
network-manager-openvpn installed, and ProtonVPN uses this method.
  When I try to connect using terminal command, I have message to run 
"journalctl -xe NM_CONNECTION=59f16a8e-7dcb-4638-a810-8d07efe00fde + 
NM_DEVICE=wlp7s0".
  When I run this, I've got warnings, which I have included in attachment 
"bug.txt".

  What I expect?

  I want to connect to VPN, like I used to earlier.

  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.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jun 11 18:07:41 2020
  InstallationDate: Installed on 2020-02-05 (126 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp7s0 scope link metric 1000
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.17 metric 600
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-05-04 (38 days ago)
  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/network-manager/+bug/1883144/+subscriptions

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

[Desktop-packages] [Bug 1858636] Re: color emoji not rendered; many bw emoji rendered as boxes

2020-06-12 Thread Marius Gedminas

I ended up adding

if [ -n "$PS1" ]; then
# only for interactive sessions please
if [ -f /var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-le64.cache-7 
]; then
   echo "color emoji will be broken in Chromium again (LP: #1858636) unless 
you"
   echo "sudo rm 
/var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-le64.cache-7"
fi
fi

to my ~/.bashrc to warn me when this problem is coming back.  So far the
appearance of this broken font cache file correlates 100% with some snap
(any snap!  refreshing _lxd_ which has nothing to do with GUI apps or
fonts causes this!) getting refreshed, according to the timestamp
reported by snap changes.

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

Title:
  color emoji not rendered; many bw emoji rendered as boxes

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev

[Desktop-packages] [Bug 1870270] Re: gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from intel_flush_front() from intel_glFlush()

Please remember to test the above PPA (comment #19). Otherwise this bug
will close without any fix to 18.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/1870270

Title:
  gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from
  intel_flush_front() from intel_glFlush()

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Eoan:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter package in CentOS:
  Unknown

Bug description:
  [Impact]

  gnome-shell crashes a lot on bionic:
  https://errors.ubuntu.com/problem/3841a5bc586bc3f532d2313a35f51e511772751f

  [Test Case]

  ** Someone who can reproduce the crash please fill this in **

  [Regression Potential]

  Low. The same fix has been released to newer versions already for most
  of a year.

  [Other Info]

  gnome shell crashed / froze while switching keyboard layouts.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.13
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 31 22:47:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1571973788
  InstallationDate: Installed on 2020-03-13 (19 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  SegvAnalysis:
   Segfault happened at: 0x7fedbfa22393:jmpq   *%rax
   PC (0x7fedbfa22393) ok
   source "*%rax" (0xfffaffed90151620) not located in a known VMA region 
(needed readable region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgbm.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1883144] Re: Can't connect to ProtonVPN (probably VPN in general)

2020-06-12 Thread Łukasz Konieczny

@Sebastien Bacher

Hi.
I have run "nmcli connection up se.protonvpn.com.udp" and "journalctl -f" in 
another terminal window. The output is in file "journalctl_log.txt".

** Attachment added: "Output of journalctl -f"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1883144/+attachment/5383186/+files/journalctl_log.txt

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

Title:
  Can't connect to ProtonVPN (probably VPN in general)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.4.0-37-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz
  Memory: 15,6 GiB

  network-manager version: 1.22.10-1ubuntu2.1

  What happens?

  I want to connect to VPN, no matter how I am doing so, be it using Plasma 
applet or via terminal (nmcli connection up se.protonvpn.com.udp), I can't. On 
the 4th June 2020 there was a network-manager update, and probably since this 
day I can't connect to VPN. Previously I could do so. Of course I have 
network-manager-openvpn installed, and ProtonVPN uses this method.
  When I try to connect using terminal command, I have message to run 
"journalctl -xe NM_CONNECTION=59f16a8e-7dcb-4638-a810-8d07efe00fde + 
NM_DEVICE=wlp7s0".
  When I run this, I've got warnings, which I have included in attachment 
"bug.txt".

  What I expect?

  I want to connect to VPN, like I used to earlier.

  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.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jun 11 18:07:41 2020
  InstallationDate: Installed on 2020-02-05 (126 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp7s0 scope link metric 1000
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.17 metric 600
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-05-04 (38 days ago)
  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/network-manager/+bug/1883144/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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%

2020-06-12 Thread Fusion

Noveau fractional scaling is fine, but pc works on slow motion..

marco-carrarini's solution seems perfect in the beginning, but many apps
do not work as they should.. so I used to change to default while using
such an app and return to the solution elsewhere. But after a while I
dismiss the solution.

Now I am just waiting the fix while running the temporary solution of
1.25 font scale.

Maybe users with nvidia and hidpi shouldn't move forward from 19.10
(fractional scaling worked fine).

-- 
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 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

2020-06-12 Thread Norbert

The Qt4 is missed in 20.04 LTS, not the Qt5.
All other seems to be true.

Anyway HPLIP developers should fix all issues running it on 20.04 LTS. I
see many negative reports about running HPLIP on 20.04 LTS. Check
https://askubuntu.com/search?tab=newest=hplip%2020.04 .

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

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Install HPLIP with `sudo apt-get install hplip-gui`
  3. Install all stuff to satisfy `hp-doctor` requirements by:

  sudo apt-get build-dep hplip
  sudo apt-get install build-essential libtool libtool-bin libcups2-dev 
cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2

  
  4. Run `hp-doctor` and `hp-check`

  Expected results:

  * `hp-doctor` ran successfully without errors 
  * `hp-check` ran successfully without errors

  Actual results:

  ```
  $ hp-doctor 

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Self Diagnse Utility and Healing Utility ver. 1.0
  ...
  Checking for Dependencies
  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
  ...
  --
  | PERMISSION |
  --

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing or 'cups' service is not running.
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 
  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 
  ...


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

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1
  ...
  ---
  | SUMMARY |
  ---

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing/incompatible 
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 

  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

  Total Errors: 3
  Total Warnings: 0

  
  Done.

  ```

  Note: many mentioned packages are already installed, Qt4 related
  packages are not installable:

  ```
  $ sudo apt-get install libcups2 libcups2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libcups2 is already the newest version (2.3.1-9ubuntu1.1).
  libcups2-dev is already the newest version (2.3.1-9ubuntu1.1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install gtk2-engines-pixbuf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install python3-pyqt4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-pyqt4

  $ sudo apt-get install python3-dbus.mainloop.qt
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-dbus.mainloop.qt
  E: Couldn't find any package by glob 'python3-dbus.mainloop.qt'
  E: Couldn't find any package by regex 'python3-dbus.mainloop.qt'
  ```

  Please consider to fix HPLIP package and support 20.04 LTS package
  base before 20.04.1 release!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May 30 12:25:39 2020
  InstallationDate: Installed on 2020-04-23 (36 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  Papersize: a4

[Desktop-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

2020-06-12 Thread Kai-Chuan Hsieh

@Hui

Sure, will do.

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
 1. enable Pre-released updates in Developer Options
Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-wip
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

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

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

[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

2020-06-12 Thread Volodymyr Dudenko

Hello Shivani, 
I cannot install HPLIP 3.20.5 in Ubuntu 20.04, because it requires a pyqt5 
package which is nowhere to be found. I know this should be a separate bug, but 
I'm just replying to your statement that 3.20.5 installation should work.

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

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Install HPLIP with `sudo apt-get install hplip-gui`
  3. Install all stuff to satisfy `hp-doctor` requirements by:

  sudo apt-get build-dep hplip
  sudo apt-get install build-essential libtool libtool-bin libcups2-dev 
cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2

  
  4. Run `hp-doctor` and `hp-check`

  Expected results:

  * `hp-doctor` ran successfully without errors 
  * `hp-check` ran successfully without errors

  Actual results:

  ```
  $ hp-doctor 

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Self Diagnse Utility and Healing Utility ver. 1.0
  ...
  Checking for Dependencies
  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
  ...
  --
  | PERMISSION |
  --

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing or 'cups' service is not running.
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 
  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 
  ...


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

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1
  ...
  ---
  | SUMMARY |
  ---

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing/incompatible 
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 

  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

  Total Errors: 3
  Total Warnings: 0

  
  Done.

  ```

  Note: many mentioned packages are already installed, Qt4 related
  packages are not installable:

  ```
  $ sudo apt-get install libcups2 libcups2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libcups2 is already the newest version (2.3.1-9ubuntu1.1).
  libcups2-dev is already the newest version (2.3.1-9ubuntu1.1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install gtk2-engines-pixbuf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install python3-pyqt4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-pyqt4

  $ sudo apt-get install python3-dbus.mainloop.qt
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-dbus.mainloop.qt
  E: Couldn't find any package by glob 'python3-dbus.mainloop.qt'
  E: Couldn't find any package by regex 'python3-dbus.mainloop.qt'
  ```

  Please consider to fix HPLIP package and support 20.04 LTS package
  base before 20.04.1 release!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May 30 12:25:39 2020
  InstallationDate: Installed on 2020-04-23 (36 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

2020-06-12 Thread shivani mandora

Hi Till,

Here packages are failing on ubuntu 20.04 for user. 
For 3.20.5,package installation will be working properly. 
Yes but print and scan through usb will not work because of ippusbxd in ubuntu 
20.04.

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

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Install HPLIP with `sudo apt-get install hplip-gui`
  3. Install all stuff to satisfy `hp-doctor` requirements by:

  sudo apt-get build-dep hplip
  sudo apt-get install build-essential libtool libtool-bin libcups2-dev 
cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2

  
  4. Run `hp-doctor` and `hp-check`

  Expected results:

  * `hp-doctor` ran successfully without errors 
  * `hp-check` ran successfully without errors

  Actual results:

  ```
  $ hp-doctor 

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Self Diagnse Utility and Healing Utility ver. 1.0
  ...
  Checking for Dependencies
  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
  ...
  --
  | PERMISSION |
  --

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing or 'cups' service is not running.
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 
  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 
  ...


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

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1
  ...
  ---
  | SUMMARY |
  ---

  Missing Required Dependencies
  -
  error: 'libcups2' package is missing/incompatible 
  error: 'python3-pyqt4' package is missing/incompatible 
  error: 'gtk2-engines-pixbuf' package is missing/incompatible 

  Missing Optional Dependencies
  -
  error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

  Total Errors: 3
  Total Warnings: 0

  
  Done.

  ```

  Note: many mentioned packages are already installed, Qt4 related
  packages are not installable:

  ```
  $ sudo apt-get install libcups2 libcups2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  libcups2 is already the newest version (2.3.1-9ubuntu1.1).
  libcups2-dev is already the newest version (2.3.1-9ubuntu1.1).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install gtk2-engines-pixbuf
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  $ sudo apt-get install python3-pyqt4
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-pyqt4

  $ sudo apt-get install python3-dbus.mainloop.qt
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package python3-dbus.mainloop.qt
  E: Couldn't find any package by glob 'python3-dbus.mainloop.qt'
  E: Couldn't find any package by regex 'python3-dbus.mainloop.qt'
  ```

  Please consider to fix HPLIP package and support 20.04 LTS package
  base before 20.04.1 release!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: hplip 3.20.3+dfsg0-2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May 30 12:25:39 2020
  InstallationDate: Installed on 2020-04-23 (36 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic

[Desktop-packages] [Bug 1882415] Re: artifact in top-right corner

Please ensure you have rebooted after disabling all extensions. Run this
command to verify:

  gsettings list-recursively org.gnome.shell > settings.txt

and then please attach the resulting text file here.

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

Title:
  artifact in top-right corner

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1883013] Re: gnome-shell-extensions-prefs does not show any updates

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

  apport-collect 1883013

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

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

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

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

Title:
  gnome-shell-extensions-prefs does not show any updates

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  One of the touted features of the GNOME 3.36 release was being able to
  update extensions directly from the Extensions app.  This doesn't seem
  to be working at all on Ubuntu 20.04, however.  I regularly receive
  update notifications from the Firefox extension, but the only way I
  have found to actually update them is using the old Gnome Extensions
  website.  I can still configure, disable, and remove extensions from
  the app, it just doesn't show any updates.  Is this functionality
  somehow disabled in Ubuntu?

  gnome-shell-extension-prefs 3.36.2-1ubuntu1~20.04.1

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

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

[Desktop-packages] [Bug 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 80866566

2020-06-12 Thread Timo Aaltonen

20.0.8 is now out, so I'll push an updated version to focal-proposed
today

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

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

Status in Mesa:
  Fix Released
Status in MPV:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Confirmed

Bug description:
  [Impact]

  Wayland apps fail to start in focal with:

  error 7: failed to import supplied dmabufs: Unsupported buffer format
  808669784

  [Test Case]

  Just run: es2gears_wayland

  [Regression Potential]

  Medium/unknown. The fix is quite new.

  [Other Info]

  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info:
  fragment shader info:
  info:
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] wl_registry@3.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104437.096]

[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

I don't think that's necessary in this case. This bug has been happening
for a year or so at least already.

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

Title:
  Gnome Shell clock is truncated/corrupt on the right side

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When clock changes value, it doesn't displaying time properly

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

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

[Desktop-packages] [Bug 1883000] Re: screengrab window remain open, without icon in launcher, hence impossible to find

>  when you click to close the gnome-screenshot window, it fails to
close and remains open

the issue there would be a gnome-screenshot one. Do you click on the
dialog button on the decoration X ?

the launcher not listing it would be an unity problem

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

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

Title:
  screengrab window remain open, without icon in launcher, hence
  impossible to find

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Sometimes, after taking a screenshot, when you click to close the
  gnome-screenshot window, it fails to close and remains open, but in
  the background, behind everything else.

  What is much worse, is that the icon in launcher does disappear. So,
  you have a "ghost" window left open, behind every other window, that
  you have NO WAY TO REACH except by minimizing or closing EVERY SINGLE
  other window one by one, until the only one that remains is
  screengrab.

  
  This makes bug 1526082 even more annoying, as sometimes, even after you 
(think you) have closed all screengrab's windows, there is still a rectanguar 
area of the screen that is slightly dimmed. The first time it happened to me, I 
thought bug 1526082 had got worse and that the screengrabbed area would now 
remain dimmed forever even after closing screengrab. But then I found out the 
window was still there.

  This is fucking pathetic. Please drop Gnome for good and pick an
  alternative that is decently maintained, by non-idiots.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: screengrab (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219
  Uname: Linux 4.4.0-179-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 10 19:54:46 2020
  InstallationDate: Installed on 2013-10-11 (2434 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: screengrab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1883144] Re: Can't connect to ProtonVPN (probably VPN in general)

Thank you for your bug report. Could you start that command

$ journalctl -f

trigger the issue and add the log 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/1883144

Title:
  Can't connect to ProtonVPN (probably VPN in general)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.5
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.4.0-37-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz
  Memory: 15,6 GiB

  network-manager version: 1.22.10-1ubuntu2.1

  What happens?

  I want to connect to VPN, no matter how I am doing so, be it using Plasma 
applet or via terminal (nmcli connection up se.protonvpn.com.udp), I can't. On 
the 4th June 2020 there was a network-manager update, and probably since this 
day I can't connect to VPN. Previously I could do so. Of course I have 
network-manager-openvpn installed, and ProtonVPN uses this method.
  When I try to connect using terminal command, I have message to run 
"journalctl -xe NM_CONNECTION=59f16a8e-7dcb-4638-a810-8d07efe00fde + 
NM_DEVICE=wlp7s0".
  When I run this, I've got warnings, which I have included in attachment 
"bug.txt".

  What I expect?

  I want to connect to VPN, like I used to earlier.

  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.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jun 11 18:07:41 2020
  InstallationDate: Installed on 2020-02-05 (126 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600
   169.254.0.0/16 dev wlp7s0 scope link metric 1000
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.17 metric 600
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-05-04 (38 days ago)
  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/network-manager/+bug/1883144/+subscriptions

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

[Desktop-packages] [Bug 1883154] Re: Nautilus should focus newly created file's name