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

[Achal Nath Tiwari]

Public bug reported:

Sometimes on my lock screen, my mouse stops for a moment, and also many
times certain application freezes and then I have to force quit them.
Also, it is not going too fast, it takes much time to boot up.

Please send me the solution I had recently sifted form windows to
ubuntu.

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: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul  4 10:22:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] 
[1002:9838] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] 
[1025:104b]
InstallationDate: Installed on 2020-07-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Aspire ES1-520
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=01e0d428-3558-4f95-a0f0-994b27c807c3 ro quiet splash i8042.nopnp 
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Bellemere_BE
dmi.board.vendor: Acer
dmi.board.version: V1.06
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
dmi.product.family: KB
dmi.product.name: Aspire ES1-520
dmi.product.sku: Aspire ES1-520_104B_V1.06
dmi.product.version: V1.06
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
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

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


** Tags: amd64 apport-bug false-gpu-hang 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/1886246

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes on my lock screen, my mouse stops for a moment, and also
  many times certain application freezes and then I have to force quit
  them. Also, it is not going too fast, it takes much time to boot up.

  Please send me the solution I had recently sifted form windows to
  ubuntu.

  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: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 10:22:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] 
[1002:9838] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] 
[1025:104b]
  InstallationDate: Installed on 2020-07-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire ES1-520
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=01e0d428-3558-4f95-a0f0-994b27c807c3 ro quiet splash i8042.nopnp 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  

[Desktop-packages] [Bug 1876523] Re: Window becomes partly offscreen when rearranging monitors

[Launchpad Bug Tracker]

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

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

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

Title:
  Window becomes partly offscreen when rearranging monitors

Status in mutter package in Ubuntu:
  Expired

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  Lenovo ThinkPad P52 + Thunderbold dock + 3 monitors

  I repositioned a monitor in display settings to reflect the actual
  position.   An open application on the monitor was not repositioned
  with the display.  The windows title bar and buttons were not on the
  display so the window could not be re-positioned.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Uname: Linux 5.3.0-51-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.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 20:10:34 2020
  DistUpgraded: 2020-05-02 16:29:42,699 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.59, 5.3.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:225f]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo GP107GLM [Quadro P1000 Mobile] [17aa:225f]
  InstallationDate: Installed on 2018-10-02 (578 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20M9CTO1WW
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2020-05-02 (0 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2CET50W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20M9CTO1WW
  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:bvrN2CET50W(1.33):bd01/15/2020:svnLENOVO:pn20M9CTO1WW:pvrThinkPadP52:rvnLENOVO:rn20M9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P52
  dmi.product.name: 20M9CTO1WW
  dmi.product.sku: LENOVO_MT_20M9_BU_Think_FM_ThinkPad P52
  dmi.product.version: ThinkPad P52
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  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/mutter/+bug/1876523/+subscriptions

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

[Desktop-packages] [Bug 1876508] Re: Fractional scaling crashes X11 session in KVM based virtual machines

[Launchpad Bug Tracker]

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

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

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

Title:
  Fractional scaling crashes X11 session in KVM based virtual machines

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  In focal release of Ubuntu proper (GNOME Desktop) i was going trought the 
release on livestream using KVM based VM(libvirtd and virt-manager using 
default video settings provided by virt-manager, Host is ubuntu mate 20.04) and 
one of the things i was trying to show was fractional scaling which made my X11 
session unusable. Screen turned black. Tryed different settings in Virt-manager 
for Video non worked.
  Resolved the issue by switching to wayland session within which fractional 
scaling worked and i could disable it/switch to 100%.
  When i after that switched to X11 session scaling was back to normal.

  SideNote: when switching scaling in a VM i was running resolution was
  reseting back to normal.

  https://youtu.be/0EFEGafZXDE?t=3400 link to the recording of a
  livestream on youtube with timecode enabled. (Video name: checking out
  Ubuntu 20.04 LTS, Channel: bigpod, timecode: 56:40)

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

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

[Desktop-packages] [Bug 1876431] Re: windows invisible when there should have been a lock screen

[Launchpad Bug Tracker]

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

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

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

Title:
  windows invisible when there should have been a lock screen

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Shortly after upgrading to focal (a few days) I left my computer alone
  and went and away for a good long while, long enough for the screen to
  lock

  Came back and
  1) the screen was not locked, 
  2) the dock at the right hand side was still available and i could manipulate 
it (ie click on the applications that were running, see the screenshots of them 
when i mouse'd over them)
  2) no windows could be seen.

  I managed to for example click on the running bitcoin icon in the top right 
hand corner, those were clickable too, but nothing did seemed to get the 
windows back. 
  Alt-tab...
  alt-crl up...
  super-tab...
  nothing i could think of

  Wound up exiting out to terminal (ctrl-alt-f3, logging in) killing
  gnome-shell and they all came back shortly there after.

  ubuntu: focal 20.04 lts
  gnome-shell:
Installed: 3.36.1-5ubuntu1
Candidate: 3.36.1-5ubuntu1
Version table:
   *** 3.36.1-5ubuntu1 500
  500 http://mirrors.layeronline.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
  Uname: Linux 5.4.0-26-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 03:16:38 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-04-18 (1109 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (6 days ago)

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

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

[Desktop-packages] [Bug 1875841] Re: package chromium-browser 80.0.3987.163-0ubuntu1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit stat

[Launchpad Bug Tracker]

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

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

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

Title:
  package chromium-browser 80.0.3987.163-0ubuntu1 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 10

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I was installing ice_6.0.7_all.deb (from ppa:peppermintos/ice-dev),
  that has chromium as dependency and in the process of installing that
  it crashed

  1) Ubuntu 20.04 LTS
  2) well, not using any package, the install of chromium-browser failed
  3) for the software to install correctly, as a dependency of ice
  4) installation chrashed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.163-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   chromium-browser:amd64: Install
   htop:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 29 17:12:11 2020
  Dependencies:
   
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2020-04-29 (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.2
  SourcePackage: chromium-browser
  Title: package chromium-browser 80.0.3987.163-0ubuntu1 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1876512] Re: Desktop wallpaper and taskbar freezes once system comes back from sleep

[Launchpad Bug Tracker]

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

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

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

Title:
  Desktop wallpaper and taskbar freezes once system comes back from
  sleep

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Once the system comes back from sleep, the desktop wallpaper appears
  as frozen screen. Same with taskbar. Also, things become normal once I
  reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 00:51:44 2020
  InstallationDate: Installed on 2019-07-29 (278 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-25 (6 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

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

[Desktop-packages] [Bug 1875782] Re: tracker-store and tracker-extract using 100% CPU

[Launchpad Bug Tracker]

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

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

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

Title:
  tracker-store and tracker-extract using 100% CPU

Status in tracker package in Ubuntu:
  Expired

Bug description:
  After upgrading from Ubuntu 18.04 to Ubuntu 20.04, tracker-store and
  tracker-extract processes are using 100% CPU. CPU temperature goes
  above 80 degrees celsius.

  This is causing fan spinning and computer is very loud because of it.

  I've tried removing tracker package, but it wants to remove the whole
  desktop with it.

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

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

[Desktop-packages] [Bug 1876642] Re: Firefox Dark

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox Dark

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When I lock the screen, Firefox goes dark like a modal window appears
  and everything else goes dark. This does not block the functionality
  of the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yerzinperez   2626 F pulseaudio
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 19:39:05 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-03-31 (33 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.9 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profile2Extensions: extensions.sqlite corrupt or missing
  Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile2Locales: extensions.sqlite corrupt or missing
  Profile2PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile2PrefSources: prefs.js
  Profile2Themes: extensions.sqlite corrupt or missing
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile3 - LastVersion=76.0/20200407205853 (Out of date)
   Profile1 (Default) - LastVersion=75.0/20200403170909
   Profile0 - LastVersion=75.0/20200403170909 (In use)
   Profile2 - LastVersion=75.0/20200403064004 (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-04-24 (9 days ago)
  dmi.bios.date: 05/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X507UF.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X507UF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX507UF.304:bd05/22/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX507UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX507UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 15_ASUS Laptop X507UF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1876524] Re: [nvidia] Issue after repositioning display/monitor location using display settings

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] Issue after repositioning display/monitor location using
  display settings

Status in mutter package in Ubuntu:
  Expired

Bug description:
  After repositioning the display applications would only maximise to use the 
area  of the screen that overlapped between the original and new positions, see 
attachment which is a screenshot of an application maximised on the affected 
display.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-10-02 (579 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.34.3-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_IE:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-51-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-05-02 (1 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1876657] Re: Sometimes Nautilus mounts USB media as read-only.

[Launchpad Bug Tracker]

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

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

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

Title:
  Sometimes Nautilus mounts USB media as read-only.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Ubuntu 18.04.4
  This happens in my all 3 laptops with several USB memories. so it's not 
hardware specific.  
  Sometimes(50% of times) Noutilus mounts USB memory as read-only. so I can't 
drag and drop files or delete files.  
  But from terminal. I can fully access my USB memories. 
  Rebooting all Nautilus process can solve this. so I guess problem is Noutilus.

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

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

[Desktop-packages] [Bug 1876433] Re: [amdgpu] Black screen after standby - clean Kubuntu on AMD T495

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [amdgpu] Black screen after standby - clean Kubuntu on AMD T495

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Expired

Bug description:
  I installed a fresh Kubuntu 20.04. on my Thinkpad T495 (AMD). No
  further software, simply clean installation. After every standby the
  Laptop wakes up, but shows only black screen. No way to get back to
  Kubuntu desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat May  2 11:48:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-05-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20NKS01Y00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=537c947f-55fc-4bba-bb91-e7c4b91e39e6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET49W(1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET49W(1.19):bd01/06/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  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
  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/xserver-xorg-video-amdgpu/+bug/1876433/+subscriptions

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

[Desktop-packages] [Bug 1876354] Re: Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one account to enable lifepatch

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one
  account to enable lifepatch

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  Two days ago I have reported a bug describing the complete path
  starting from the software updater button settings/lifepatch >
  lifepatch > sign in/lifepatch  Then a window was opened

  Line at top: X [] Ubuntu Single Sign-on Account
  Next line:  same title as above without X []
  Next line: Email address: field
  Next line: (*) I have an Ubuntu Single Sign-on Account
  Next line: Password: field
  Next line: (  ) I want to register for an account now
  Next line: (  ) I've forgotten my password
  Bottom line: link Privacy Policy

  There is no button to confirm any action above

  I looked for help at https://help.ubuntu.com/community/CommunityHelpWiki and 
clicked on support
  on the next page https://ubuntu.com/support/community-support I clicked on 
Lifepatch. Then on
  https://ubuntu.com/livepatch I found: free for personal use Get Lifepatch. 
Next page:
  
https://auth.livepatch.canonical.com/?_ga=2.18896568.1031641790.1588091589-177936974.1572286294

  Get your Lifepatch token. On the next page I got a key and two command lines 
to enable Lifepatch
  https://auth.livepatch.canonical.com/?user_type=ubuntu-user

  sudo snap install canonical-livepatch
  sudo canonical-livepatch enable ***key*** (a 32 digits code with letters and 
numbers)

  My problem was easily solved using the commands above in a terminal

  I feel silly that I have reported this two days ago as a bug. I took
  me two days to find a solution.

  Now an icon on top toolbar shows that lifepatch is activated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1876354/+subscriptions

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

[Desktop-packages] [Bug 1876787] Re: Keyboard Shortcuts didn't working.

[Launchpad Bug Tracker]

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

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

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

Title:
  Keyboard Shortcuts didn't working.

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Addded the "Super + 2", "Super + 3" and "Super + 4" commands to switch
  to the 2,3,and 4 Workspaces and it's not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  4 15:17:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [104d:908a]
  InstallationDate: Installed on 2020-04-24 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Sony Corporation VPCEG15FB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f4a823e2-8306-4dcc-a6bc-c34ec67ae110 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0240Z8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0240Z8:bd01/06/2012:svnSonyCorporation:pnVPCEG15FB:pvrC902GW09:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEG15FB
  dmi.product.sku: N/A
  dmi.product.version: C902GW09
  dmi.sys.vendor: Sony Corporation
  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
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1886245] [NEW] bluetooth freezing after boot

[Sam Srzen]

Public bug reported:

Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will 
work as normal.
I am using a plugable USB Bluetooth adapter for Bluetooth connections.
I am using  blueman to connect.
Mouse used is a Kensington Exper Mouse Wireless Trackball
Issue does not occur with bluetooth speakers, or headphones.

Computer- Dell Precision 5520.


Logs show these errors as below

bt_uhid_send: Invalid argument (22)

Bluetooth: hci0: advertising data len corrected


Description:Ubuntu 20.04 LTS
Release:20.04

blueman:
  Installed: 2.1.2-1
  Candidate: 2.1.2-1
  Version table:
 *** 2.1.2-1 500
500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul  4 13:24:01 2020
InstallationDate: Installed on 2020-06-03 (30 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.19.2
dmi.board.name: 06X96V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 5C:F3:70:7E:32:2F  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:193521 acl:13666 sco:0 events:137 errors:0
TX bytes:5858 acl:61 sco:0 commands:82 errors:0

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


** Tags: amd64 apport-bug focal

** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1886245/+attachment/5389533/+files/dmesg.txt

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

Title:
  bluetooth freezing after boot

Status in bluez package in Ubuntu:
  New

Bug description:
  Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it 
will work as normal.
  I am using a plugable USB Bluetooth adapter for Bluetooth connections.
  I am using  blueman to connect.
  Mouse used is a Kensington Exper Mouse Wireless Trackball
  Issue does not occur with bluetooth speakers, or headphones.

  Computer- Dell Precision 5520.

  
  Logs show these errors as below

  bt_uhid_send: Invalid argument (22)

  Bluetooth: hci0: advertising data len corrected

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  blueman:
Installed: 2.1.2-1
Candidate: 2.1.2-1
Version table:
   *** 2.1.2-1 500
  500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 13:24:01 2020
  InstallationDate: Installed on 2020-06-03 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic 
root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2020
  

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[erio]

It still fails in mutter 3.36.3 too.

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1841745] Re: Update to 1.2.0

[Bug Watch Updater]

** Changed in: libxt (Debian)
   Status: Unknown => New

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

Title:
  Update to 1.2.0

Status in libxt package in Ubuntu:
  New
Status in libxt package in Debian:
  New

Bug description:
  The new version has non trivial change and is not in Debian/Fedora yet

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1879968

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1886235] Re: EMU 1212m card (emu10k1 driver) stops working after PCI reset

[Kamyar Kaviani]

Here's t he information I got from alsa-info:

http://alsa-project.org/db/?f=0adb1150463e905a6584004021bacf1f11c850cc

** Summary changed:

- EMU 1212m card (emu10k1 driver) stops working after PCI reset
+ EMU 1212m card (emu10k1 driver) stops working after PCI reset snd_emu10k1 
invalid position buffer size

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

Title:
  EMU 1212m card (emu10k1 driver) stops working after PCI reset
  snd_emu10k1 invalid position buffer size

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After using my computer for a day or so and coming back to it, my
  sound card, EMU 1212m, randomly stops to work. And the only solution I
  have found is completely turn off the power to the motherboard and
  wait a few minutes until powering back on.

  When the card works, I am able to reproduce the problem after typing:

  sudo echo 1 > /sys/bus/pci/devices/:05:04.0/reset

  Executing that command stops the card from outputting any sound, and I
  see the following printed in dmesg:

  [   73.029029] snd_pcm_update_hw_ptr0: 3153 callbacks suppressed
  [   73.029033] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [   73.029114] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [   73.029122] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [   73.040768] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [   73.046208] snd_emu10k1 :05:04.0: interrupt: PCI error
  [   73.046235] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 
domain=0x0015 address=0x0 flags=0x]
  [   73.046244] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 
domain=0x0015 address=0x0 flags=0x]
  [   73.046250] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 
domain=0x0015 address=0x0 flags=0x]
  [   73.046255] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 
domain=0x0015 address=0x0 flags=0x]
  [   73.046261] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 
domain=0x0015 address=0x0 flags=0x]
  [   73.046266] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 
domain=0x0015 address=0x0 flags=0x]

  Further resets result in

  [  497.663897] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [  497.663971] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [  497.663997] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [  497.674025] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [  497.684046] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
  [  497.694065] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384

  
  It seems this is a problem with the driver snd_emu10k1 (maybe invalid buffer 
size?). In the past, I have used this card in earlier Ubuntu's before without 
any issues. All I had to do was to build and install the latest alsa-firmware, 
alsa-lib, and alsa-utils from https://www.alsa-project.org/wiki/Download.

  It's surprising that this card is not natively supported out of the
  box in 20.04, but even worse, the driver emu10k1 appears to be broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 14:56:03 2020
  InstallationDate: Installed on 2020-06-16 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1409
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X570-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1409:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: 

[Desktop-packages] [Bug 1234325] Re: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: tentative de remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet libjp

[Kai Kasurinen]

libjpeg8:i386 8d-1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu7 failed to install/upgrade: tentative de
  remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui
  appartient aussi au paquet libjpeg-turbo8:i386 1.2.1-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  unable to launch gnome session

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: libjpeg8 8c-2ubuntu7
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Sat Sep 28 02:00:27 2013
  DuplicateSignature: package:libjpeg8:8c-2ubuntu7:tentative de remplacement de 
« /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet 
libjpeg-turbo8:i386 1.2.1-0ubuntu2
  ErrorMessage: tentative de remplacement de « 
/usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet 
libjpeg-turbo8:i386 1.2.1-0ubuntu2
  InstallationDate: Installed on 2013-09-12 (19 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: tentative de 
remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi 
au paquet libjpeg-turbo8:i386 1.2.1-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1234325/+subscriptions

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

[Desktop-packages] [Bug 1886235] [NEW] EMU 1212m card (emu10k1 driver) stops working after PCI reset

[Kamyar Kaviani]

Public bug reported:

After using my computer for a day or so and coming back to it, my sound
card, EMU 1212m, randomly stops to work. And the only solution I have
found is completely turn off the power to the motherboard and wait a few
minutes until powering back on.

When the card works, I am able to reproduce the problem after typing:

sudo echo 1 > /sys/bus/pci/devices/:05:04.0/reset

Executing that command stops the card from outputting any sound, and I
see the following printed in dmesg:

[   73.029029] snd_pcm_update_hw_ptr0: 3153 callbacks suppressed
[   73.029033] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[   73.029114] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[   73.029122] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[   73.040768] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[   73.046208] snd_emu10k1 :05:04.0: interrupt: PCI error
[   73.046235] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 
address=0x0 flags=0x]
[   73.046244] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 
address=0x0 flags=0x]
[   73.046250] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 
address=0x0 flags=0x]
[   73.046255] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 
address=0x0 flags=0x]
[   73.046261] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 
address=0x0 flags=0x]
[   73.046266] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 
address=0x0 flags=0x]

Further resets result in

[  497.663897] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[  497.663971] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[  497.663997] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[  497.674025] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[  497.684046] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384
[  497.694065] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, 
buffer size = 16384, period size = 16384


It seems this is a problem with the driver snd_emu10k1 (maybe invalid buffer 
size?). In the past, I have used this card in earlier Ubuntu's before without 
any issues. All I had to do was to build and install the latest alsa-firmware, 
alsa-lib, and alsa-utils from https://www.alsa-project.org/wiki/Download.

It's surprising that this card is not natively supported out of the box
in 20.04, but even worse, the driver emu10k1 appears to be broken.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul  3 14:56:03 2020
InstallationDate: Installed on 2020-06-16 (17 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/12/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1409
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X570-E GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1409:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  EMU 1212m card (emu10k1 driver) stops working after PCI reset

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After using my computer for a day or so and coming back to it, my
  sound card, EMU 1212m, randomly stops to work. And the only solution I
  have found is completely turn off the power to 

[Desktop-packages] [Bug 1184148] Re: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: intentando sobreescribir `/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también en el paquete libjpeg-tur

[Kai Kasurinen]

libjpeg8:i386 8d-1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu7 failed to install/upgrade: intentando
  sobreescribir `/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también
  en el paquete libjpeg-turbo8:i386 1.2.1-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: libjpeg8 8c-2ubuntu7
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Thu May 23 08:24:58 2013
  ErrorMessage: intentando sobreescribir 
`/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también en el paquete 
libjpeg-turbo8:i386 1.2.1-0ubuntu2
  InstallationDate: Installed on 2013-04-15 (39 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: intentando 
sobreescribir `/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también en el 
paquete libjpeg-turbo8:i386 1.2.1-0ubuntu2
  UpgradeStatus: Upgraded to raring on 2013-04-26 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1184148/+subscriptions

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

[Desktop-packages] [Bug 1357242] Re: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64

[Kai Kasurinen]

libjpeg8:amd64 8d-1+deb7u1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in
  package libjpeg-turbo8:amd64 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  When I boot up, the application tells me it crashes.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libjpeg8 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Wed Aug 13 22:07:06 2014
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.1
   libgcc1 1:4.9.1-0ubuntu1
   libjpeg-turbo8 1.3.0-0ubuntu2
   multiarch-support 2.19-0ubuntu6.1
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg8_8d-1+deb7u1_amd64.deb ...
   Unpacking libjpeg8:amd64 (8d-1+deb7u1) over (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg8_8d-1+deb7u1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also 
in package libjpeg-turbo8:amd64 1.3.0-0ubuntu2
  DuplicateSignature: package:libjpeg8:8c-2ubuntu8:trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package 
libjpeg-turbo8:amd64 1.3.0-0ubuntu2
  ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', 
which is also in package libjpeg-turbo8:amd64 1.3.0-0ubuntu2
  InstallationDate: Installed on 2014-06-18 (57 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package 
libjpeg-turbo8:amd64 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1357242/+subscriptions

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

[Desktop-packages] [Bug 1371271] Re: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: tentative de rempla

[Kai Kasurinen]

libjpeg8  8d-1+deb7u1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 [modified:
  usr/share/doc/libjpeg8/changelog.Debian.gz
  usr/share/doc/libjpeg8/copyright] failed to install/upgrade: tentative
  de remplacement de « /usr/share/doc/libjpeg8/copyright », qui est
  différent d'autres instances du paquet libjpeg8:i386

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  i don't know im a new user on ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  Date: Thu Sep 18 20:06:35 2014
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.3
   libgcc1 1:4.9.1-0ubuntu1
   libjpeg-turbo8 1.3.0-0ubuntu2
   multiarch-support 2.19-0ubuntu6.3
  DuplicateSignature: package:libjpeg8:8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz 
usr/share/doc/libjpeg8/copyright]:tentative de remplacement de « 
/usr/share/doc/libjpeg8/copyright », qui est différent d'autres instances du 
paquet libjpeg8:i386
  ErrorMessage: tentative de remplacement de « 
/usr/share/doc/libjpeg8/copyright », qui est différent d'autres instances du 
paquet libjpeg8:i386
  InstallationDate: Installed on 2014-09-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] 
failed to install/upgrade: tentative de remplacement de « 
/usr/share/doc/libjpeg8/copyright », qui est différent d'autres instances du 
paquet libjpeg8:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1371271/+subscriptions

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

[Desktop-packages] [Bug 1756502] Re: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite

[Kai Kasurinen]

libjpeg8:i386 (8d-1+deb7u1)
libjpeg8:amd64 (8d-1+deb7u1)

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: libjpeg8-empty (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg8 8c-2ubuntu8 [modified:
  usr/share/doc/libjpeg8/changelog.Debian.gz
  usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libjpeg8/copyright', which is
  different from other instances of package libjpeg8:i386

Status in libjpeg8-empty package in Ubuntu:
  Invalid

Bug description:
  dont know my system charshes for what

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 16 15:48:52 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libjpeg-turbo8 1.4.2-0ubuntu3
   multiarch-support 2.23-0ubuntu10
  DuplicateSignature:
   package:libjpeg8:8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]
   Unpacking libjpeg8:i386 (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg8_8c-2ubuntu8_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', which is 
different from other instances of package libjpeg8:i386
  ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', 
which is different from other instances of package libjpeg8:i386
  InstallationDate: Installed on 2018-02-17 (27 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.25
  SourcePackage: libjpeg8-empty
  Title: package libjpeg8 8c-2ubuntu8 [modified: 
usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libjpeg8/copyright', which is different from other instances of 
package libjpeg8:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1756502/+subscriptions

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

[Desktop-packages] [Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

[chris pollock]

Ref bug #1886110, I submitted this because after almost 2yrs this issue
is still valid, at least on my Ubuntu 18.04LTS. I'm commenting here
because I was asked to on my other report. According to comments made
here - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/501, the last
one by  Marco Trevisan a commit was made a year ago to fix this issue -
https://gitlab.gnome.org/GNOME/gnome-
shell/-/commit/a9234f7631f2228184d027419cab1350666ffdc1 therefore I'm
wondering why it's not been fixed, at least in my case.

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

Title:
  gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been
  already deallocated - impossible to access to it

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/501

  ---

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.28.2-0ubuntu0.18.04.1
    Candidate: 3.28.2-0ubuntu0.18.04.1
    Version table:
   *** 3.28.2-0ubuntu0.18.04.1 500

  Since upgrading from 16.04.5LTS to 18.04.1LTS last Thursday my syslog
  has been filling with the below:

  Aug 19 11:34:11 localhost gnome-shell[2503]: Object Meta.Background 
(0x7febd401a470), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: == Stack trace for 
context 0x561c9a54e330 ==
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #0 0x561c9a9edbd8 i  
 resource:///org/gnome/shell/ui/background.js:718 (0x7febd000f450 @ 22)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #1 0x561c9a9edb50 i  
 resource:///org/gnome/shell/ui/tweener.js:113 (0x7febd02c7e68 @ 37)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #2 0x7fff0e3e36e0 b  
 resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7febd02d3b38 @ 54)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #3 0x7fff0e3e3830 b  
 resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7febd02d3bc0 @ 
1626)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #4 0x7fff0e3e38e0 b  
 resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7febd02d3c48 @ 100)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #5 0x7fff0e3e3970 b  
 resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7febd02d3cd0 @ 10)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #6 0x7fff0e3e3a60 b  
 resource:///org/gnome/gjs/modules/signals.js:128 (0x7febd02d3230 @ 386)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #7 0x7fff0e3e3b10 b  
 resource:///org/gnome/shell/ui/tweener.js:245 (0x7febd02cf808 @ 159)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #8 0x7fff0e3e3be0 b  
 resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7febd02b5de0 @ 71)
  Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #9 0x7fff0e3e3c80 b  
 resource:///org/gnome/shell/ui/tweener.js:220 (0x7febd02cf780 @ 15)

  Following suggestions in previous bug reports about this I went
  through and removed all of my shell extensions:

  chris@localhost:~/.local/share/gnome-shell/extensions$ ls -l
  total 0
  chris@localhost:~/.local/share/gnome-shell/extensions$
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-10-24 (1395 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-32-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (3 days ago)
  UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1877038]

[Jaromir Talir]

Any update on this? We are using FIDO MDS to verify attestations and
only get useless fido-u2f type attestation statement (no aaguids
included) with Firefox  on Linux. This works fine in Chrome. I believe
it's related to this issue. The situation forces us to put disclaimer on
our service: "Do not use Firefox for FIDO2 token registrations". It
makes me sad since Firefox has always been my favourite browser. Hope
this will move forward.

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

Title:
  [upstream] Firefox lacks FIDO2 support with Yubikeys

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

Bug description:
  Ubuntu LTS versions affected.

  "Passwordless" authentications with Yubikeys using Firefox don't work
  with FIDO2.

  Tested both with the yubikey software packages from the
  bionic/universe repo and those from the vendor https://www.yubico.com/

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

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

[Desktop-packages] [Bug 1886229] [NEW] Clicking "Install" with .deb gives no response when APT in use

[Noor Muhammad Malik]

Public bug reported:

The problem description

If I open up a .deb file to install the package, it opens up the gnome-software 
GUI window, with the install button.
If the package manager APT is in use somewhere, either you left an "apt 
upgrade" running in the background, or there's some APT process running in the 
background, meaning that the lock is acquired by another process, clicking on 
the "install" button will do nothing. It will get stuck on a random % of 
progress and then just do nothing, no installations, no errors.
If you let all the APTs finish, or kill existing processes to release the lock, 
the install button works fine.

What I expected to happen:
==
I expected it to check for a running instance of the package manager, check if 
the lock is free and then generate a pop-up/dialogue-box telling me that the 
package manager is in use, instead of randomly misbehaving with no output, 
which is bad user experience.

I'd recently encountered this bug and it was very frustrating for quite
a while until I figured out why it was happening and wanted to report
it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.1-0ubuntu4.18.04.15
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul  4 01:45:58 2020
InstallationDate: Installed on 2018-04-15 (810 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.15
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Clicking "Install" with .deb gives no response when APT in use

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The problem description
  
  If I open up a .deb file to install the package, it opens up the 
gnome-software GUI window, with the install button.
  If the package manager APT is in use somewhere, either you left an "apt 
upgrade" running in the background, or there's some APT process running in the 
background, meaning that the lock is acquired by another process, clicking on 
the "install" button will do nothing. It will get stuck on a random % of 
progress and then just do nothing, no installations, no errors.
  If you let all the APTs finish, or kill existing processes to release the 
lock, the install button works fine.

  What I expected to happen:
  ==
  I expected it to check for a running instance of the package manager, check 
if the lock is free and then generate a pop-up/dialogue-box telling me that the 
package manager is in use, instead of randomly misbehaving with no output, 
which is bad user experience.

  I'd recently encountered this bug and it was very frustrating for
  quite a while until I figured out why it was happening and wanted to
  report it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.15
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  4 01:45:58 2020
  InstallationDate: Installed on 2018-04-15 (810 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.15
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1841745] Re: Update to 1.2.0

[Hans Joachim Desserud]

** Bug watch added: Debian Bug tracker #962735
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962735

** Also affects: libxt (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962735
   Importance: Unknown
   Status: Unknown

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

Title:
  Update to 1.2.0

Status in libxt package in Ubuntu:
  New
Status in libxt package in Debian:
  Unknown

Bug description:
  The new version has non trivial change and is not in Debian/Fedora yet

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

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

[Desktop-packages] [Bug 1886217] Re: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all

[Dmitry Syomin]

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front]
  No sound at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula
  with Supreme FX audio card. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 21:25:22 2020
  InstallationDate: Installed on 2020-07-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: Maximus Formula
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1

[Alberto Donato]

I can confirm the issue with 3.36.3-0ubuntu0.20.04.1 too

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

Title:
  Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1

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

Bug description:
  Till yesterday, it was working fine. But today after reboot, night
  light failed to start. I tried turning Night Light off/on but nothing
  seemed to work.

  Unfortunately, I don't know what the previous version of mutter was installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-04 (22 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1

[Launchpad Bug Tracker]

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

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

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

Title:
  Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1

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

Bug description:
  Till yesterday, it was working fine. But today after reboot, night
  light failed to start. I tried turning Night Light off/on but nothing
  seemed to work.

  Unfortunately, I don't know what the previous version of mutter was installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-04 (22 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1

[Launchpad Bug Tracker]

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

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

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

Title:
  Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1

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

Bug description:
  Till yesterday, it was working fine. But today after reboot, night
  light failed to start. I tried turning Night Light off/on but nothing
  seemed to work.

  Unfortunately, I don't know what the previous version of mutter was installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-04 (22 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1886217] [NEW] [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all

[Dmitry Syomin]

Public bug reported:

Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula
with Supreme FX audio card. No sound.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dmitrys2051 F pulseaudio
 /dev/snd/controlC1:  dmitrys2051 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul  3 21:25:22 2020
InstallationDate: Installed on 2020-07-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dmitrys2051 F pulseaudio
 /dev/snd/controlC1:  dmitrys2051 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1403
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Maximus Formula
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: Maximus Formula
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

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

Title:
  [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula
  with Supreme FX audio card. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 21:25:22 2020
  InstallationDate: Installed on 2020-07-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitrys2051 F pulseaudio
   /dev/snd/controlC1:  dmitrys2051 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: Maximus Formula
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1886214] [NEW] apt-get upgrade fails on zsys package

[Patrick Gray]

Public bug reported:

root@tmp:/home/pgray# zfs list -t snapshot -o name -S creation 
no datasets available

root@tmp:/home/pgray# sudo apt-get install zsys
Reading package lists... Done
Building dependency tree   
Reading state information... Done
zsys is already the newest version (0.4.6).
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Requesting to save current system state
Successfully saved as "autozsys_90843v"
Setting up zsys (0.4.6) ...
dpkg: error processing package zsys (--configure):
 installed zsys package post-installation script subprocess returned error exit 
status 1
Errors were encountered while processing:
 zsys
ZSys is adding automatic system snapshot to GRUB menu
ERROR Service took too long to respond. Disconnecting client. 
E: Sub-process /usr/bin/dpkg returned an error code (1)

root@tmp:/home/pgray# zpool list
NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
rpool   107G  9.27G  97.7G- -10% 8%  1.00xONLINE  -

This was after a previous upgrade failed.
Even after removing all snapshots for that pool, it fails.

root@tmp:/home/pgray# lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

root@tmp:/home/pgray# apt-cache policy zsys
zsys:
  Installed: 0.4.6
  Candidate: 0.4.6
  Version table:
 *** 0.4.6 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.4.5 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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


** Tags: zfs

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

Title:
  apt-get upgrade fails on zsys package

Status in zsys package in Ubuntu:
  New

Bug description:
  root@tmp:/home/pgray# zfs list -t snapshot -o name -S creation 
  no datasets available

  root@tmp:/home/pgray# sudo apt-get install zsys
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  zsys is already the newest version (0.4.6).
  0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Requesting to save current system state
  Successfully saved as "autozsys_90843v"
  Setting up zsys (0.4.6) ...
  dpkg: error processing package zsys (--configure):
   installed zsys package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   zsys
  ZSys is adding automatic system snapshot to GRUB menu
  ERROR Service took too long to respond. Disconnecting client. 
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  root@tmp:/home/pgray# zpool list
  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
  rpool   107G  9.27G  97.7G- -10% 8%  1.00xONLINE  
-

  This was after a previous upgrade failed.
  Even after removing all snapshots for that pool, it fails.

  root@tmp:/home/pgray# lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04

  root@tmp:/home/pgray# apt-cache policy zsys
  zsys:
Installed: 0.4.6
Candidate: 0.4.6
Version table:
   *** 0.4.6 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Desktop-packages] [Bug 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

[Marcus Urso-Bernick]

So I'm following up after a long time away from my laptop. I'm currently
experiencing an error which says: TLS/SSL support not available; install
glib-networking. I'm not sure why this is happening but I'm willing to
poke around if you are able to help me. I"m hoping together we can ID
the cause. I'm sorry to say that I haven't been willing to even open my
laptop because of this issue.

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

Title:
  https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

Status in glib-networking package in Ubuntu:
  Incomplete

Bug description:
  OS: Pop!_OS 20.04 LTS x86_64 
  Host: XPS 13 9370 
  Kernel: 5.4.0-7634-generic 
  Uptime: 2 hours, 50 mins 
  Packages: 1817 (dpkg), 20 (snap) 
  Shell: bash 5.0.16 
  Resolution: 1920x1080 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Pop 
  Theme: Pop-dark [GTK2/3] 
  Icons: Pop [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i5-8250U (8) @ 3.400GHz 
  GPU: Intel UHD Graphics 620 
  Memory: 3322MiB / 15729MiB 

  Summary(cont) - Attempt to input Google account info into online
  account util and get error--> TLS/SSL support not available; install
  glib-networking.

   
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
  Referenced this BUG REPORT

  ##Downloaded Deb build but I'm having an issue applying appropriate
  inputs in the provided documentation. Please help!##

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1882636/+subscriptions

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

[Desktop-packages] [Bug 1886204] Re: Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Flickering and sudden resolution changes on 20.04/18.04 and old Radeon
  HD 6570 card

Status in xorg package in Ubuntu:
  New

Bug description:
  Initially, Ubuntu started with far lower resolution than my monitor.
  I've tried xrandr --newmode command*, it temporarily helps to get back
  to my original 1600X900 resolution. But now screen sometimes go back
  to that lower resolution (and randpomly comes back to normal after
  some time), and xrandr doesn't help.

  Plus, my screen keeps flickering, sometimes quite frequently. Combined
  with low resolution, it has become almost unbearable at this point.
  Things work alright with windows 10 (dual boot).

  Further details:

  1. Sometimes, but not always, simply going to Display Setting by
  GUI or typing xrandr in command line fixes it.

  2. I sometimes see "drm:radeon_vga_detect [radeon]] ERROR VGA-1:
  probed a monitor but no|invalid EDID" while shutting down or in
  /var/log/syslog. Also quite frequently "ERROR:edid_parser.cc(102)] Too
  short EDID data: manufacturer id" in the log.

  3. Using read-edid package, I noticed that while on low res, it
  can't detect EDID on any bus. However if I keep running this command,
  at some point it successfully reads & parses EDID. Then, if I go to
  Display Setting, or after some time automatically- the resolution
  comes back to normal.

  4. Reinstalled ubuntu 20.04, removed that cron job. Didn't change
  the situation.

  5. I've tried Wayland, awesome window manager, lightdm display
  manager. I'd rather not change the GNOME environment.

  6. Tried Ubuntu 18.04.4 (current OS), now its always low
  resolution.

  Config: CPU: Ryzen 3700x, MB: Asus Tuf x570 Gaming plus, Monitor:
  Samsung SyncMaster E2020

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.7.1-050701-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 20:53:51 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] 
[1002:6759] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Turks PRO [Radeon HD 
6570/7570/8550] [174b:e193]
  InstallationDate: Installed on 2020-07-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic 
root=UUID=e26c767f-e791-4209-905a-0e9eaa3bc363 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  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/1886204/+subscriptions

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

[Desktop-packages] [Bug 1886204] [NEW] Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Initially, Ubuntu started with far lower resolution than my monitor.
I've tried xrandr --newmode command*, it temporarily helps to get back
to my original 1600X900 resolution. But now screen sometimes go back to
that lower resolution (and randpomly comes back to normal after some
time), and xrandr doesn't help.

Plus, my screen keeps flickering, sometimes quite frequently. Combined
with low resolution, it has become almost unbearable at this point.
Things work alright with windows 10 (dual boot).

Further details:

1. Sometimes, but not always, simply going to Display Setting by GUI
or typing xrandr in command line fixes it.

2. I sometimes see "drm:radeon_vga_detect [radeon]] ERROR VGA-1:
probed a monitor but no|invalid EDID" while shutting down or in
/var/log/syslog. Also quite frequently "ERROR:edid_parser.cc(102)] Too
short EDID data: manufacturer id" in the log.

3. Using read-edid package, I noticed that while on low res, it
can't detect EDID on any bus. However if I keep running this command, at
some point it successfully reads & parses EDID. Then, if I go to Display
Setting, or after some time automatically- the resolution comes back to
normal.

4. Reinstalled ubuntu 20.04, removed that cron job. Didn't change
the situation.

5. I've tried Wayland, awesome window manager, lightdm display
manager. I'd rather not change the GNOME environment.

6. Tried Ubuntu 18.04.4 (current OS), now its always low resolution.

Config: CPU: Ryzen 3700x, MB: Asus Tuf x570 Gaming plus, Monitor:
Samsung SyncMaster E2020

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.7.1-050701-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul  3 20:53:51 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] 
[1002:6759] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Turks PRO [Radeon HD 
6570/7570/8550] [174b:e193]
InstallationDate: Installed on 2020-07-02 (0 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic 
root=UUID=e26c767f-e791-4209-905a-0e9eaa3bc363 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1405
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
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

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


** Tags: amd64 apport-bug bionic focal resolution ubuntu
-- 
Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 
card
https://bugs.launchpad.net/bugs/1886204
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1883497] Autopkgtest regression report (xorg-server-hwe-18.04/2:1.20.8-2ubuntu2.2~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server-hwe-18.04 
(2:1.20.8-2ubuntu2.2~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.138-0ubuntu0.18.04.1 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#xorg-server-hwe-18.04

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

Thank you!

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

  this is required to support new laptop models which use such panels

  [Test case]
  Test that a proper list of modes is shown with a panel that uses the new EDID.

  [Regression potential]
  The patch retains the previous code path for setting modes on GTF-able 
monitors, and only adds support for non-GTF monitors. So in that sense there 
shouldn't be any regression potential, this has been reviewed by an upstream 
expert.

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

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

[Desktop-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract

[F S]

I get the same error as Alex, but for TGA files:

```
tracker-extract[13828]: Call to 
gst_discoverer_discover_uri(file://[...]/Ale_col.tga) failed: Internal data 
stream error.
```

The error only occurs with certain TGAs, I shall attaching one below.

My current workaround is to add '*.tga' to
"/org/freedesktop/tracker/miner/files/ignored-files" in `dconf-editor`.

SYSTEM:
```
#lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

#apt-cache policy tracker*
tracker-extract:
  Installed: 2.3.3-2
  Candidate: 2.3.3-2

tracker-miner-fs:
  Installed: 2.3.3-2
  Candidate: 2.3.3-2

tracker:
  Installed: 2.3.4-1
  Candidate: 2.3.4-1
```

** Attachment added: "Ale_col.tga"
   
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+attachment/5389438/+files/Ale_col.tga

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

Title:
  Abysmal memory leak on tracker-extract

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging
  madly. It became very difficult to use and I discovered the problem to
  be tracker-extract running and very rapidly leaking memory up to 100%
  and breaching into swap memory. I tried killing it several times but
  Tracker appears to relaunch it every time, so I deleted it from
  /usr/lib/tracker entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 13:02:25 2019
  InstallationDate: Installed on 2019-03-11 (42 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1884428] Re: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory)

[Abir]

Not working, please solve this problem

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

Title:
  calculator won't open (error while loading shared libraries:
  libgtk-3.so.0: cannot open shared object file: No such file or
  directory)

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  new bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:21:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  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-59-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.101-2~18.04.1
  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/gnome-calculator/+bug/1884428/+subscriptions

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

[Desktop-packages] [Bug 1884428] Re: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory)

[Abir]

** Attachment added: "15937877820911335792869835982818.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+attachment/5389419/+files/15937877820911335792869835982818.jpg

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

Title:
  calculator won't open (error while loading shared libraries:
  libgtk-3.so.0: cannot open shared object file: No such file or
  directory)

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  new bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:21:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  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-59-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.101-2~18.04.1
  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/gnome-calculator/+bug/1884428/+subscriptions

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

[Desktop-packages] [Bug 1885610] Re: enlarged components on lock/login screen

[Relly Valentine]

Just tried both suggestions and unfortunately no changes.

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

Title:
  enlarged components on lock/login screen

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Source Package: usr/bin/gnome-shell
  Ubuntu Release: 20.04 LTS
  Package Version: 3.36.2-1ubuntu1~20.04.1
  Expected: Normal sized components on lock/login screen
  Happened: Enlarged components on lock/login screen

  This behavior is unaffected by resolution size from different monitors

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Flat-Remix-Miami-Dark-GNOME:GNOME
  Date: Mon Jun 29 13:01:06 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-02 (331 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   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-06-27 (2 days ago)

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

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

[Desktop-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output

[AceLan Kao]

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => 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/1882248

Title:
  plug headset won't proper reconfig ouput to it on machine with default
  output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Bionic:
  New

Bug description:
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.


  
  target machine does not have built-in speaker, and the monitor does not have 
an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

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

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

[Desktop-packages] [Bug 1196339] Re: Firefox "Open Containing Folder" opens Audacious instead of File Manager

[We need robots]

I had the same issue with Firefox on Arch Linux and LXDE. The "Open
containing folder" in Firefox was opening the Elementary Code editor.

The solution described in rmoorman's comment #16 also worked for me.

I had to update /usr/share/applications/mimeinfo.cache ,

and change the line:

inode/directory=io.elementary.code.desktop;pcmanfm.desktop;

to:

inode/directory=pcmanfm.desktop;

Now Firefox opens the folder correctly with pcmanfm. I guess it is the
same for all applications.

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

Title:
  Firefox "Open Containing Folder" opens Audacious instead of File
  Manager

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

Bug description:
  Steps to reproduce:

  1. Open Firefox web browser
  2. Click on Downloads arrow (to right of search box by default)
  3. Click on Show All Downloads
  4. Click on the "Open Containing Folder" icon next to a file you have already 
downloaded

  Actual behavior: The containing folder doesn't open. Instead Audacious
  opens.

  Expected behavior: The containing folder should open in the File
  Manager.

  This bug is present in a clean install of Ubuntu Studio 13.04

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

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

[Dmitry]

Worked for me too

Jul 03 15:39:40 pop-os gnome-shell[1517]: Crtc at 0.00x0.00 size 
3840.00x2160.00 (@ 1.00 - adapted 1.00) considering it of 
3840.00x2160.00
Jul 03 15:39:40 pop-os gnome-shell[1517]: Crtc at 3840.00x0.00 size 
1920.00x1200.00 (@ 1.00 - adapted 1.00) considering it of 
1920.00x1200.00
Jul 03 15:39:40 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:40 pop-os gnome-shell[1517]: Configuring CRTC 442 with mode 448 
(3840 x 2160 @ 59.996624) at position 0, 0 and transform 0
Jul 03 15:39:40 pop-os gnome-shell[1517]: Setting UBUNTU crtc config crtc 442, 
timestamp 0 (config timestamp 13025), x: 0, y: 0, mode: 448, rotation 1, 
n_outputs 1: RETURN reply 0x55f93a90d600, error: (nil)
Jul 03 15:39:40 pop-os gnome-shell[1517]: Configuring CRTC 441 with mode 477 
(1920 x 1200 @ 59.950172) at position 3840, 0 and transform 0
Jul 03 15:39:40 pop-os gnome-shell[1517]: Setting UBUNTU crtc config crtc 441, 
timestamp 0 (config timestamp 13025), x: 3840, y: 0, mode: 477, rotation 1, 
n_outputs 1: RETURN reply 0x55f93a90d6f0, error: (nil)
Jul 03 15:39:40 pop-os gnome-shell[1517]: Failed to load module 
"appmenu-gtk-module"
Jul 03 15:39:41 pop-os gnome-shell[1517]: Unset XDG_SESSION_ID, 
getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jul 03 15:39:41 pop-os gnome-shell[1517]: Will monitor session c1
Jul 03 15:39:41 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:41 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:41 pop-os gnome-shell[1517]: Setting screen size 5760x2160
Jul 03 15:39:41 pop-os gnome-shell[1517]: Unable to connect to ibus: Could not 
connect: Connection refused
Jul 03 15:39:41 pop-os gnome-shell[1517]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jul 03 15:39:41 pop-os gnome-shell[1517]: JS WARNING: 
[resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property 
"MetaWindowX11"
Jul 03 15:39:42 pop-os gnome-shell[1517]: Registering session with GDM
Jul 03 15:39:48 pop-os gnome-shell[2515]: Enabling experimental feature 
'x11-randr-fractional-scaling'
Jul 03 15:39:48 pop-os gnome-shell[2515]: Failed to read monitors config file 
'/home/route/.config/monitors.xml': Logical monitors not adjacent
Jul 03 15:39:48 pop-os gnome-shell[2515]: Crtc at 0.00x0.00 size 
3840.00x2160.00 (@ 1.00 - adapted 1.00) considering it of 
3840.00x2160.00
Jul 03 15:39:48 pop-os gnome-shell[2515]: Crtc at 3840.00x0.00 size 
1920.00x1200.00 (@ 1.00 - adapted 1.00) considering it of 
1920.00x1200.00
Jul 03 15:39:48 pop-os gnome-shell[2515]: Setting screen size 5760x2160
Jul 03 15:39:48 pop-os gnome-shell[2515]: Scaling at 1.00 (transformation 
matrix is 65536 = 1.00) using filter fast
Jul 03 15:39:48 pop-os gnome-shell[2515]: Configuring CRTC 442 with mode 448 
(3840 x 2160 @ 59.996624) at position 0, 0 and transform 0
Jul 03 15:39:48 pop-os gnome-shell[2515]: Setting UBUNTU crtc config crtc 442, 
timestamp 0 (config timestamp 21095), x: 0, y: 0, mode: 448, rotation 1, 
n_outputs 1: RETURN reply 0x55f990fde6b0, error: (nil)
Jul 03 15:39:48 pop-os gnome-shell[2515]: Scaling at 1.00 (transformation 
matrix is 65536 = 1.00) using filter fast
Jul 03 15:39:48 pop-os gnome-shell[2515]: Configuring CRTC 441 with mode 477 
(1920 x 1200 @ 59.950172) at position 3840, 0 and transform 0
Jul 03 15:39:48 pop-os gnome-shell[2515]: Setting UBUNTU crtc config crtc 441, 
timestamp 0 (config timestamp 21095), x: 3840, y: 0, mode: 477, rotation 1, 
n_outputs 1: RETURN reply 0x55f990fde7a0, error: (nil)
Jul 03 15:39:48 pop-os gnome-shell[2515]: Unset XDG_SESSION_ID, 
getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jul 03 15:39:48 pop-os gnome-shell[2515]: Will monitor session 2
Jul 03 15:39:49 pop-os gnome-shell[2515]: Telepathy is not available, chat 
integration will be disabled.
Jul 03 15:39:49 pop-os gnome-shell[2515]: gnome-shell-extension-system76-power: 
power profile was set: 'Balanced'
Jul 03 15:39:49 pop-os gnome-shell[2515]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pop-sh...@system76.com/math.js 42]: test for 
equality (==) mistyped as assignment (=)?
Jul 03 15:39:49 pop-os gnome-shell[2515]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pop-sh...@system76.com/math.js 42]: test for 
equality (==) mistyped as assignment (=)?
Jul 03 15:39:49 pop-os gnome-shell[2515]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pop-sh...@system76.com/math.js 42]: 
reference to undefined property 1
Jul 03 15:39:49 pop-os gnome-shell[2515]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pop-sh...@system76.com/math.js 42]: 
reference to undefined property 0
Jul 03 15:39:49 pop-os gnome-shell[2515]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pop-sh...@system76.com/math.js 42]: 
reference to 

[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen

[pqwoerituytrueiwoq]

Awesome!
Any idea when it will land in the ubuntu groovy repos?
Just pulled it into my 20.04 install and it seems to not be there yet
$ xfce4-panel --version
xfce4-panel 4.14.4 (Xfce 4.14)

Copyright (c) 2004-2011
The Xfce development team. All rights reserved.

Please report bugs to .

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  Confirmed
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Won't Fix

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions

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

[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

[Łukasz Zemczak]

Hello AaronMa, or anyone else affected,

Accepted xorg-server-hwe-18.04 into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-hwe-18.04/2:1.20.8-2ubuntu2.2~18.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-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. 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.

** Tags added: verification-needed-bionic

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

  this is required to support new laptop models which use such panels

  [Test case]
  Test that a proper list of modes is shown with a panel that uses the new EDID.

  [Regression potential]
  The patch retains the previous code path for setting modes on GTF-able 
monitors, and only adds support for non-GTF monitors. So in that sense there 
shouldn't be any regression potential, this has been reviewed by an upstream 
expert.

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

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

[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

[Timo Aaltonen]

autopkgtests cleared

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

  this is required to support new laptop models which use such panels

  [Test case]
  Test that a proper list of modes is shown with a panel that uses the new EDID.

  [Regression potential]
  The patch retains the previous code path for setting modes on GTF-able 
monitors, and only adds support for non-GTF monitors. So in that sense there 
shouldn't be any regression potential, this has been reviewed by an upstream 
expert.

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[joao vieira]

this affects me for some years now, bosses now complain for me to move
to windows as now we are all remote with tons of meetings and this is a
big impact on how they see all this linux desktop adoption.

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

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

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New

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

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

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

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

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

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

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

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

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

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

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

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

[Mark Lagace]

I don't believe this is related to Dropbox, as I had what appears to be
the same bug happen to me (crash with SIGSEGV, very shortly after login)
but do not have Dropbox installed. This is a clean install of 20.04.

-- 
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 1883425] Re: Various bugs in network part of GNOME settings

[Launchpad Bug Tracker]

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

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

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

Title:
  Various bugs in network part of GNOME settings

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

Bug description:
  1) "Turn On WiFi Hotspot" is greyed out in the 3 dot menu when opening GNOME 
settings directly on the WiFi tab. However, switching to a different tab and 
back fixes this. When hovering the mouse above the greyed out "Turn On WiFi 
Hotspot", a tooltip says "System policy prohibits use as a Hotspot".
  See also: https://askubuntu.com/q/1236823/801743

  2) Deleting a route in the settings window for a particular network makes the 
settings window for that network blank until re-opened. To reproduce:
   - Open GNOME settings on WiFi tab
   - Click gear icon next to any WiFi network
   - Add a new IPv4 route
   - Close the window
   - Re-open the window
   - Try to delete the route

  Expected result:
   The route is removed and when clicking "apply" it is gone permanently

  Actual result:
   All the widgets on the window disappear and the route is not removed 
permanently when clicking "apply" so it can be seen again when re-opening the 
window.

  Details:
   - Ubuntu 20.04 with all updates applied

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 14 12:36:56 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-04-25 (49 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1886021] Re: Nautilus slow after upgrade 20.04

[Cristina Franzolini]

** Package changed: xfce4-settings (Ubuntu) => nautilus (Ubuntu)

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

Title:
  Nautilus slow after upgrade 20.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  After I upgraded to 20.04, nautilus is very slow to open (open folder
  from applications, also, when I need open a file or save it)

  time nautilus:
  real  0m54,410s
  user  0m2,962s
  sys   0m0,483s

  Error:
  Error creating proxy: Errore nel chiamare StartServiceByName per 
org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 
24)
  RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not 
initialized

  Nautilus version 1:3.36.3-0ubuntu1

  I tried this solution:
  
https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04

  But it doesn't work.

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

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

[Desktop-packages] [Bug 1886021] [NEW] Nautilus slow after upgrade 20.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After I upgraded to 20.04, nautilus is very slow to open (open folder
from applications, also, when I need open a file or save it)

time nautilus:
real0m54,410s
user0m2,962s
sys 0m0,483s

Error:
Error creating proxy: Errore nel chiamare StartServiceByName per 
org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 
24)
RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not 
initialized

Nautilus version 1:3.36.3-0ubuntu1

I tried this solution:
https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04

But it doesn't work.

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

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

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

[Desktop-packages] [Bug 1886176] [NEW] gnome-shell crashes on screen-lock, disable and re-enable extensions fixes until session restart

[ak-a]

Public bug reported:

After logging in I can't screen-lock until I disable then re-enable
extensions.  I have tried disable extensions one by one and it doesn't
matter which extensions are enable, any will break on first attempt to
lock after fresh login.  systemd sees the SEGV, logs attached.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul  3 10:31:02 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-01-06 (178 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-25 (68 days ago)

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


** Tags: amd64 apport-bug focal gnome-shell

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

Title:
  gnome-shell crashes on screen-lock, disable and re-enable extensions
  fixes until session restart

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After logging in I can't screen-lock until I disable then re-enable
  extensions.  I have tried disable extensions one by one and it doesn't
  matter which extensions are enable, any will break on first attempt to
  lock after fresh login.  systemd sees the SEGV, logs attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 10:31:02 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-01-06 (178 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-25 (68 days ago)

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

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

[Desktop-packages] [Bug 1886162] Re: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time

[Timo Aaltonen]

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

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

Title:
  Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from
  time to time

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

Bug description:
  Side scrollbar setting feature works from time to time . If you set it
  on and close the window it saves the setting and side scrollbar works
  . If you set it on and move to another menu item i.e. "Sound" or
  "search" it doesn't save the setting and switch it back to off.

  S.T.R.
  1. Open "Settings";
  2. Move to  "Mouse and scroll pad" item;
  3. Set Side scrollbar to on;
  4. Move to "Sound" item;
  5. Move to  "Mouse and scroll pad" item.

  A.R. Side scrollbar is on.
  E.R. Side scrollbar is off.

  Severity: low

  Environment:
  Ubuntu 20.04 LTS 64 bit Russian language
  Gnome 3.36.2

  Check screenshot attached.

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

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

[Desktop-packages] [Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions

[Luis Alberto Pabón]

:O

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

Title:
  Very poor multi-monitor performance in Wayland sessions

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

Bug description:
  Upstream bug:
  https://gitlab.gnome.org/GNOME/mutter/issues/3

  ---

  When dragging a window between displays, I can see cpu usage increase
  while framerate drops dramatically to single numbers.

  Desktop scaling is 1.0, one is a WXGA screen and another FHD.

  Ubuntu session (wayland), 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:09:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

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

[Desktop-packages] [Bug 1886162] Re: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time

[Yurii Pankov]

screenshot attached.

** Attachment added: "screenshot 2020-07-03 09-57-17.png"
   
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1886162/+attachment/5389315/+files/screenshot%202020-07-03%2009-57-17.png

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

Title:
  Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from
  time to time

Status in x11-apps package in Ubuntu:
  New

Bug description:
  Side scrollbar setting feature works from time to time . If you set it
  on and close the window it saves the setting and side scrollbar works
  . If you set it on and move to another menu item i.e. "Sound" or
  "search" it doesn't save the setting and switch it back to off.

  S.T.R.
  1. Open "Settings";
  2. Move to  "Mouse and scroll pad" item;
  3. Set Side scrollbar to on;
  4. Move to "Sound" item;
  5. Move to  "Mouse and scroll pad" item.

  A.R. Side scrollbar is on.
  E.R. Side scrollbar is off.

  Severity: low

  Environment:
  Ubuntu 20.04 LTS 64 bit Russian language
  Gnome 3.36.2

  Check screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1886162/+subscriptions

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

[Desktop-packages] [Bug 1886162] [NEW] Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time

[Yurii Pankov]

Public bug reported:

Side scrollbar setting feature works from time to time . If you set it
on and close the window it saves the setting and side scrollbar works .
If you set it on and move to another menu item i.e. "Sound" or "search"
it doesn't save the setting and switch it back to off.

S.T.R.
1. Open "Settings";
2. Move to  "Mouse and scroll pad" item;
3. Set Side scrollbar to on;
4. Move to "Sound" item;
5. Move to  "Mouse and scroll pad" item.

A.R. Side scrollbar is on.
E.R. Side scrollbar is off.

Severity: low

Environment:
Ubuntu 20.04 LTS 64 bit Russian language
Gnome 3.36.2

Check screenshot attached.

** Affects: x11-apps (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from
  time to time

Status in x11-apps package in Ubuntu:
  New

Bug description:
  Side scrollbar setting feature works from time to time . If you set it
  on and close the window it saves the setting and side scrollbar works
  . If you set it on and move to another menu item i.e. "Sound" or
  "search" it doesn't save the setting and switch it back to off.

  S.T.R.
  1. Open "Settings";
  2. Move to  "Mouse and scroll pad" item;
  3. Set Side scrollbar to on;
  4. Move to "Sound" item;
  5. Move to  "Mouse and scroll pad" item.

  A.R. Side scrollbar is on.
  E.R. Side scrollbar is off.

  Severity: low

  Environment:
  Ubuntu 20.04 LTS 64 bit Russian language
  Gnome 3.36.2

  Check screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/1886162/+subscriptions

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

[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen

[Simon Steinbeiß]

It's "Won't fix" only for the component xorg, because it won't/can't be
fixed in that component.

The fix has already landed in the relevant package (xfce4-panel).

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  Confirmed
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Won't Fix

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions

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

[Desktop-packages] [Bug 1886154] [NEW] package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1

[Michał Sawicz]

Public bug reported:

Tried to `dist-upgrade` and can't get `zsys` to get past the postinst
script, there's also no helpful information that I can see anywhere in
the logs.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: zsys 0.4.6
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.3
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jul  3 10:03:57 2020
DpkgTerminalLog:
 Setting up zsys (0.4.6) ...
 cannot trim '/dev/sda4': currently trimming
 dpkg: error processing package zsys (--configure):
  installed zsys package post-installation script subprocess returned error 
exit status 1
ErrorMessage: installed zsys package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-02-10 (143 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vbwrmj@/vmlinuz-5.4.0-29-generic 
root=ZFS=rpool/ROOT/ubuntu_vbwrmj ro quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.2, unpackaged
RelatedPackageVersions:
 zfs-initramfs  0.8.3-1ubuntu12.1
 zfsutils-linux 0.8.3-1ubuntu12.1
SourcePackage: zsys
Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
ZFSImportedPools:
 NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH  
ALTROOT
 rpool   114G  73,0G  41,0G- -52%64%  1.00xONLINE  -
ZFSListcache-bpool:
 bpool  /boot   off on  on  off on  off on  off 
-   none
 bpool/BOOT noneoff on  on  off on  off on  
off -   none
 bpool/BOOT/ubuntu_vbwrmj   /boot   on  on  on  off on  
off on  off -   none

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


** Tags: amd64 apport-package focal

** Description changed:

  Tried to `dist-upgrade` and can't get `zsys` to get past the postinst
- script, there's also no helpful information anywhere in the logs.
+ script, there's also no helpful information that I can see anywhere in
+ the logs.
  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zsys 0.4.6
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jul  3 10:03:57 2020
  DpkgTerminalLog:
-  Setting up zsys (0.4.6) ...
-  cannot trim '/dev/sda4': currently trimming
-  dpkg: error processing package zsys (--configure):
-   installed zsys package post-installation script subprocess returned error 
exit status 1
+  Setting up zsys (0.4.6) ...
+  cannot trim '/dev/sda4': currently trimming
+  dpkg: error processing package zsys (--configure):
+   installed zsys package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed zsys package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-02-10 (143 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vbwrmj@/vmlinuz-5.4.0-29-generic 
root=ZFS=rpool/ROOT/ubuntu_vbwrmj ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.2, unpackaged
  RelatedPackageVersions:
-  zfs-initramfs  0.8.3-1ubuntu12.1
-  zfsutils-linux 0.8.3-1ubuntu12.1
+  zfs-initramfs  0.8.3-1ubuntu12.1
+  zfsutils-linux 0.8.3-1ubuntu12.1
  SourcePackage: zsys
  Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  ZFSImportedPools:
-  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH 
 ALTROOT
-  rpool   114G  73,0G  41,0G- -52%64%  1.00xONLINE 
 -
+  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH 
 ALTROOT
+  rpool   114G  73,0G  41,0G- -52%64%  1.00xONLINE 
 -
  ZFSListcache-bpool:
-  bpool/boot   off on  on  off on  off on  
off -   none
-  bpool/BOOT   noneoff on  on  off on  off on  
off -   none
-  bpool/BOOT/ubuntu_vbwrmj /boot   on  on  on  off on  
off on  off -  

[Desktop-packages] [Bug 1886151] Re: monitor problem

[Daniel van Vugt]

I can see some strange things happening every few seconds in XorgLog.txt

Please try:

1. Deleting your monitor settings by deleting the file:

   ~/.config/monitors.xml

2. Reboot

and tell us if the problem happens again.

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

Title:
  monitor problem

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

Bug description:
  my second monitor turn off, the appeared with resized set and then
  just disappear, not able to turn it on again, although the light of
  the led is on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 09:24:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:1357]
  InstallationDate: Installed on 2020-06-29 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Acer Extensa 215-51
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=4a77fddc-3b20-4cf4-9395-4f25052d3ae9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Taurus_WC
  dmi.board.vendor: CML
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd03/31/2020:svnAcer:pnExtensa215-51:pvrV1.09:rvnCML:rnTaurus_WC:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: Extensa 15
  dmi.product.name: Extensa 215-51
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  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/mutter/+bug/1886151/+subscriptions

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

[Desktop-packages] [Bug 1886151] Re: monitor problem

[Daniel van Vugt]

I can see some strange things happening every few seconds in XorgLog.txt

Please try:

1. Deleting your monitor settings by deleting the file:
~/.config/monitors.xml

2. Reboot

and tell us if the problem happens again.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

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

** Tags added: multimonitor

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

Title:
  monitor problem

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

Bug description:
  my second monitor turn off, the appeared with resized set and then
  just disappear, not able to turn it on again, although the light of
  the led is on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 09:24:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:1357]
  InstallationDate: Installed on 2020-06-29 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Acer Extensa 215-51
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=4a77fddc-3b20-4cf4-9395-4f25052d3ae9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Taurus_WC
  dmi.board.vendor: CML
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd03/31/2020:svnAcer:pnExtensa215-51:pvrV1.09:rvnCML:rnTaurus_WC:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: Extensa 15
  dmi.product.name: Extensa 215-51
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  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/mutter/+bug/1886151/+subscriptions

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

[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Aaron Whitehouse]

Hello all,

Apologies, I missed these recent messages.

For background, the error UnicodeDecodeError just means that a non-ASCII
character is hitting a piece of code that was not designed to handle it.
That is not surprising -- prior to the 0.8 series, very little of the
code was designed for non-ASCII characters. What that means is that you
may be seeing a UnicodeDecodeError even though this bug is fixed,
because somewhere else in the code needs fixing.

Victor Douglas (jhngalt): This is an interesting error and thank you very much 
for following our instructions on testing the snap and giving the relevant 
details. Can you please test with the latest stable duplicity snap and, if you 
still have a problem, report the bug in our new tracker 
(https://gitlab.com/duplicity/duplicity/-/issues )? Note that "snap run 
duplicity" does not actually do anything without arguments (even working 
correctly it gives:
Command line error: Expected 2 args, got 0
Enter 'duplicity --help' for help screen.), but it still should not be giving 
an error like that. It looks as though the error was related to non-ASCII in 
your temporary directory name not being handled correctly.

Martin Theiner (mathesubu1) and BlueT - Matthew Lien - 練喆明 (bluet) --
you are both using an old (pre 0.8 series) version of duplicity/deja
dup. Please uninstall the system version (e.g. "sudo apt-get purge
duplicity") and install the stable snap (e.g. "sudo snap install
duplicity —classic") and test again.

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1886151] [NEW] monitor problem

[Laura]

Public bug reported:

my second monitor turn off, the appeared with resized set and then just
disappear, not able to turn it on again, although the light of the led
is on.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-62-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul  3 09:24:00 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1357]
InstallationDate: Installed on 2020-06-29 (3 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: Acer Extensa 215-51
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=4a77fddc-3b20-4cf4-9395-4f25052d3ae9 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/31/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Taurus_WC
dmi.board.vendor: CML
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd03/31/2020:svnAcer:pnExtensa215-51:pvrV1.09:rvnCML:rnTaurus_WC:rvrV1.09:cvnAcer:ct10:cvrV1.09:
dmi.product.family: Extensa 15
dmi.product.name: Extensa 215-51
dmi.product.sku: 
dmi.product.version: V1.09
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
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

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


** Tags: amd64 apport-bug bionic 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/1886151

Title:
  monitor problem

Status in xorg package in Ubuntu:
  New

Bug description:
  my second monitor turn off, the appeared with resized set and then
  just disappear, not able to turn it on again, although the light of
  the led is on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  3 09:24:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:1357]
  InstallationDate: Installed on 2020-06-29 (3 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Acer Extensa 215-51
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic 
root=UUID=4a77fddc-3b20-4cf4-9395-4f25052d3ae9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Taurus_WC
  dmi.board.vendor: CML
  dmi.board.version: V1.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd03/31/2020:svnAcer:pnExtensa215-51:pvrV1.09:rvnCML:rnTaurus_WC:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: Extensa 15
  dmi.product.name: Extensa 215-51
  dmi.product.sku: 
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  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 

[Desktop-packages] [Bug 1872452] Re: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD)

[hboetes]

I noticed the same problems and a few more. For example closing the lid
hangs the system. Disconnecting the power supply hangs the system. All
clearly kernel related.

I tried the iommu=soft solution which didn't work for me. Also adding
amd_iommu=pt didn't help.

The best fix I found so far was upgrading to a more recent kernel. i.e. Get 
this script: https://github.com/pimlie/ubuntu-mainline-kernel.sh
And install the latest kernel.

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

Title:
  [amdgpu] Boot into black screen without power supply (Kubuntu on AMD)

Status in kwin package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Always when I turn on my Lenovo Thinkpad T495 (AMD CPU)- without the
  power supply connected - the laptop  boots correctly at the beginning,
  but then just before going to the login screen it gets black. It can
  only be restarted. When I attach the power supply before the laptop
  boot everything works correctly. I see this behavior only on Kubuntu
  (with KDE desktop). On Ubuntu 20.04 everything works fine.

  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
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 13 14:20:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-04-02 (10 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: LENOVO 20NKS01Y00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=d6957960-70a9-45a8-98b1-b0a14d07b829 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T495
  dmi.product.name: 20NKS01Y00
  dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
  dmi.product.version: ThinkPad T495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 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/kwin/+bug/1872452/+subscriptions

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

[Desktop-packages] [Bug 1884775] Re: SRU the current 3.36.3.1 stable update

[Paul White]

With -proposed enabled I updated to version 3.36.3.1-0ubuntu1 and logged
into a GNOME session.

As per test case I was able to:

Change the background image
Change the locale
Reconfigure my dual display setup
Confirm version in Settings | About was 3.36.3
Verify that Nautilus previewed images correctly
Reset any changed settings back to my defaults


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

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

Title:
  SRU the current 3.36.3.1 stable update

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some translation updates
  https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS

  * Test case

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

  Check that a GNOME session still works correctly, including changing
  the background image, locale and screen settings. The GNOME version in
  setting should also be 3.36.3

  * Regression potential

  The update has some test and translations fixes and a change to the
  thumbnailing, check that nautilus still previews images correctly

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

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

[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Anton Panduru]

@Bob Lawrence (pilotbob42) I don't have .xprofile but i created it my
home folder like you suggested and added the text, mine was HDMI3.
Unfortunately it doesn't seem to do anything.

I also observed that changing the DPI solves the issue on most distros I tried.
But i don't like any other DPI than 100%.

Also in regard to the workaround posted by me changing to DRI 2, mostly
solves the issue on gnome on POP OS, still a few mouse trails but it is
bearable.

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in Linux:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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/linux/+bug/1767654/+subscriptions

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

[Desktop-packages] [Bug 1874962] Re: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from othe

[Kai Kasurinen]

libpango-1.0-0:1.42.4-7~deb10u1

Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug. Please
report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

** Changed in: pango1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz',
  which is different from other instances of package
  libpango-1.0-0:amd64

Status in pango1.0 package in Ubuntu:
  Invalid

Bug description:
  Rendering issues with the monospace default font (DejaVu Mono Book)
  led me to try and downgrade the libpango packages, which in turn
  caused this problem with the system packages.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpango-1.0-0 1.42.4-7~deb10u1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 23:15:13 2020
  DuplicateSignature:
   package:libpango-1.0-0:1.42.4-7~deb10u1
   Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over 
(1.42.4-7~deb10u1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', 
which is different from other instances of package libpangocairo-1.0-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other 
instances of package libpango-1.0-0:amd64
  InstallationDate: Installed on 2014-09-11 (2052 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: pango1.0
  Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is 
different from other instances of package libpango-1.0-0:amd64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1874962/+subscriptions

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