date:20200518

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

Title:
  [nvidia] Gnome Shell freeze

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  My Nvidia GPU is set to on-demand mode, so it uses the integrated
  intel iGPU for most of the every day tasks.

  This hang seems to happen when watching media (1080p @ 11605 kbps in
  H.264 in MKV container with EAC3 5.1 sound) and then switching to a
  resource intensive tab, which loads up lot's of media (ex: Reddit)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-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 20200224 (Ubuntu 9.2.1-30ubuntu1)
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  1 22:48:00 2020
  DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.59, 5.3.0-40-generic, x86_64: installed
   nvidia, 440.59, 5.4.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
  InstallationDate: Installed on 2020-01-22 (39 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET41W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1867337] Re: Login screen visible after login, in place of desktop wallpaper

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

Title:
  Login screen visible after login, in place of desktop wallpaper

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I logged into Ubuntu and the system crashed and the login screen was a frozen 
screen with login page on it.
  All the apps were not as responsive as the expected login screen won't go.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 13 17:20:00 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fa]
  InstallationDate: Installed on 2020-03-11 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Apple Inc. MacBookPro9,2
  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-18-generic 
root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 229.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-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
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  NonfreeKernelModules: wl
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: focal third-party-packages
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1867758] Re: Gnome shell froze completely

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

Title:
  Gnome shell froze completely

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Gnome shell froze completely and would not respond to any mouse clicks
  or keyboard action. The mouse did move, but that's about it. It stayed
  this way for ~15mins before I reset it and lost all my work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 11:51:50 2020
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-02-15 (1126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2020-02-15 (30 days ago)

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

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

[Desktop-packages] [Bug 1862359] Re: Gnome Control Center doesn't open

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

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

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

Title:
  Gnome Control Center doesn't open

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

Bug description:
  When I try to open the Gnome Control Center application, it dies
  silently. When I try to open it on the terminal, this error is
  displayed on the terminal:

  $ gnome-control-center --verbose
  can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: 
/usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared 
object file: No such file or directory
  Segmentation fault (core dumped)

  I believe it is a problem with outdated dependencies (libspa-support).
  Could you fix this bug, please?

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

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

[Desktop-packages] [Bug 1868057] Re: screen flickering some small parts in user interface not right

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

Title:
  screen flickering some small parts in user interface not right

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  just flickering but rare and little bits of colour problems in text.
  Don't really know what I'm doing now but it's an error report.
  Hopefully for graphics issues. lol

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 19 09:52:59 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics Controller [103c:1944]
  InstallationDate: Installed on 2020-03-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Hewlett-Packard HP ProBook 440 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=f6a4f0fe-5dac-4579-a54d-22600c546092 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2019
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L74 Ver. 01.49
  dmi.board.name: 1944
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 12.F4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL74Ver.01.49:bd08/29/2019:svnHewlett-Packard:pnHPProBook440G1:pvrA3008DD10B03:rvnHewlett-Packard:rn1944:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 440 G1
  dmi.product.sku: C7N87AV#AB5
  dmi.product.version: A3008DD10B03
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1867955] Re: My entire DE flashes when trying to install an app and the application doesn't install

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

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

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

Title:
  My entire DE flashes when trying to install an app and the application
  doesn't install

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  When I try to install an app both with gnome-software and snap-store
  my DE flashes and it doesn't install anything. tried both with snap
  and deb. At at least we deb a got an error message "Permission denied"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 18:48:22 2020
  InstallationDate: Installed on 2019-12-24 (85 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.35.91-0ubuntu1
   gnome-software-plugin-snap3.35.91-0ubuntu1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-03-15 (2 days ago)

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

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

[Desktop-packages] [Bug 1868059] Re: Boot Flickering Issue

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

Title:
  Boot Flickering Issue

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  On boot after I selected Ubuntu to load, it flickers while loading and
  I have to boot in "safe mode" then after that it loads normally. Quite
  frustrating not knowing how long it's going to take to load if at all.

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

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

[Desktop-packages] [Bug 1879182] Re: Sound cuts off and back on randomly during online streaming of videos

It looks like the main problem here is that your kernel audio devices
keep reappearing (and disappearing??):

May 18 21:04:31 sidpc kernel: snd_hda_intel :00:1f.3: Applying patch 
firmware 'hda-jack-retask.fw'
May 18 21:04:31 sidpc kernel: snd_hda_intel :00:1f.3: bound :00:02.0 
(ops i915_audio_component_bind_ops [i915])
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: ALC1150: SKU 
not ready 0x
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC1150: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:
speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:mono: 
mono_out=0x0
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:
dig-out=0x11/0x1e
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:inputs:
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:  Front 
Mic=0x19
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:  Rear 
Mic=0x18
May 18 21:04:31 sidpc kernel: snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a

And the fact that i915 is mentioned makes me think it's the HDMI or
DisplayPort monitor confusing the system into reconfiguring audio.

** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)

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

Title:
  Sound cuts off and back on randomly during online streaming of videos

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sound shuts off and turns back on again with two pop clicks. When the
  sound is off, if i turn up the volume to the max, i can hear crackling
  sound in speakers in tune with sound playing on the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siddahuja  31829 F pulseaudio
   /dev/snd/controlC0:  siddahuja  31829 F pulseaudio
   /dev/snd/pcmC0D0p:   siddahuja  31829 F...m pulseaudio
   /dev/snd/timer:  siddahuja  31829 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 23:56:27 2020
  InstallationDate: Installed on 2020-04-27 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z170X-Gaming 3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821

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

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

[Desktop-packages] [Bug 1879282] Re: Workspace shows windows that is not on the current workspace

First please try removing all nonstandard gnome-shell extensions. We
need to try this first because so many bugs are caused by extensions. If
you can reproduce the problem without gnome-shell extensions then please
attach a new video showing that.

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

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

Title:
  Workspace shows windows that is not on the current workspace

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  If I have two workspaces and have for example firefox on both
  workspaces, then the second workspace will show the firefox windows
  that is on the first workspace. I can not controll this window, its
  just a piece of the background. I get this problem 100% of the time.
  The way I get it is by being on my second workspace, howering my
  pointer over the firefox on my topbar, go through the windows of the
  windows open for firefox, which makes my screen jump to the first
  window when i hower over the firefox window that is open on the first
  workspace, to indicate where it is located. Then when i click on the
  firefox window that is on the second workspace, the window from the
  first workspace is "stuck" as a wallpaper.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:59:15 2020
  DistUpgraded: 2020-04-26 19:27:56,468 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1740]
  InstallationDate: Installed on 2020-04-17 (30 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58e4 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=dc6ec013-e29e-4a5e-8dd0-17ae3cf639fc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-26 (21 days ago)
  dmi.bios.date: 11/14/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UA
  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.:bvrUX430UA.304:bd11/14/2017:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/1879282/+subscriptions

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

[Desktop-packages] [Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)

Thanks. That core is of the login screen itself. We haven't got a
retrace yet but maybe wait a few hours and the bots will get to it...

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

Title:
  wayland session hard freezes on login from GDM (X11 session works
  fine)

Status in mutter package in Ubuntu:
  New

Bug description:
  When I login to my laptop running Ubuntu 20.04, after entering my
  username, when I choose the "gear" button and select Ubuntu on Wayland
  as the session type, my laptop freezes hard. Mouse and keyboard do not
  respond, and the first three times I hit this issue I had to forcibly
  power off. The normal (X11) Ubuntu session works fine.

  However, I realized that I could still ping and ssh in, and doing that
  gave me some clues to the issue.

  I have keychain installed for password-less SSH, and my bash_profile has:
  ---
  #!/bin/bash
  # Get the aliases and functions
  if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
  fi

  # Setup password-less SSH
  [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
  keychain $HOME/.ssh/id_rsa
  source $HOME/.keychain/${HOSTNAME}-sh
  ---

  When I login via SSH from another machine after hitting the issue, I get:
  [johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Your Hardware Enablement Stack (HWE) is supported until April 2025.
  Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3

   * keychain 2.8.5 ~ http://www.funtoo.org
   * Waiting 5 seconds for lock...
   * Found existing ssh-agent: 2086
   * Adding 1 ssh key(s): /home/john/.ssh/id_rsa
  Enter passphrase for /home/john/.ssh/id_rsa: 
   * ssh-add: Identities added: /home/john/.ssh/id_rsa
  [john@andromeda: ~] pstree
  systemd─┬─NetworkManager───2*[{NetworkManager}]
  ├─accounts-daemon───2*[{accounts-daemon}]
  ├─acpid
  ├─avahi-daemon───avahi-daemon
  ├─bluetoothd
  ├─boltd───2*[{boltd}]
  ├─colord───2*[{colord}]
  ├─containerd───13*[{containerd}]
  ├─cron
  ├─cups-browsed───2*[{cups-browsed}]
  ├─cupsd
  ├─dbus-daemon
  ├─dnsmasq───dnsmasq
  
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  └─2*[{gdm3}]
  ├─gnome-keyring-d───2*[{gnome-keyring-d}]
  ├─iio-sensor-prox───2*[{iio-sensor-prox}]
  ├─irqbalance───{irqbalance}
  ├─2*[kerneloops]
  ├─libvirtd───16*[{libvirtd}]
  ├─networkd-dispat
  ├─packagekitd───2*[{packagekitd}]
  ├─polkitd───2*[{polkitd}]
  ├─rsyslogd───3*[{rsyslogd}]
  ├─rtkit-daemon───2*[{rtkit-daemon}]
  ├─ssh-agent
  ├─sshd───sshd───sshd───bash───pstree
  ├─switcheroo-cont───2*[{switcheroo-cont}]
  ├─systemd─┬─(sd-pam)
  │ ├─at-spi-bus-laun─┬─dbus-daemon
  │ │ └─3*[{at-spi-bus-laun}]
  │ ├─at-spi2-registr───2*[{at-spi2-registr}]
  │ ├─dbus-daemon
  │ ├─dconf-service───2*[{dconf-service}]
  │ ├─gjs───10*[{gjs}]
  │ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
  │ ├─gnome-session-b───3*[{gnome-session-b}]
  │ ├─gnome-session-c───{gnome-session-c}
  │ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
  │ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
  │ │ │ 
├─ibus-engine-sim───2*[{ibus-engi+
  │ │ │ └─2*[{ibus-daemon}]
  │ │ └─16*[{gnome-shell}]
  │ ├─goa-daemon───3*[{goa-daemon}]
  │ ├─goa-identity-se───2*[{goa-identity-se}]
  │ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
  │ ├─gsd-color───3*[{gsd-color}]
  │ ├─gsd-keyboard───3*[{gsd-keyboard}]
  │ ├─gsd-media-keys───3*[{gsd-media-keys}]
  │ ├─gsd-power───3*[{gsd-power}]
  │ ├─gsd-print-notif───2*[{gsd-print-notif}]
  │ ├─gsd-printer───2*[{gsd-printer}]
  │ ├─gsd-rfkill───2*[{gsd-rfkill}]
  │

[Desktop-packages] [Bug 1879044] Re: gnome-shell restarts due to bluetooth disconnection

Thanks but none of those are gnome-shell or Xorg. They're just apps that
have crashed.

Please wait till the problem happens again and repeat the steps in
comment #4.

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

Title:
  gnome-shell restarts due to bluetooth disconnection

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am logged in an X session with gnome.  Just after logging, I start a
  Sony Bluetooth headphones (WH-1000XM3).  After they connect (and they
  work), I switch them off (using the switch in the headphones).  < 3
  seconds after disconnections, the gnome-session crashes (and
  restarts).

  If I do this in Wayland, since the server does not seem to support
  restarts, I am logged out of the session and the laptop returns to the
  login screen.

  Best,

  Manuel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 11:23:01 2020
  DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-03-26 (416 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-05-08 (7 days ago)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET71W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  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:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  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 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/1879044/+subscriptions

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

[Desktop-packages] [Bug 1878998] Re: Value in Yaru-dark/gnome-shell/gnome-shell.css not used

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

** Changed in: yaru-theme (Ubuntu)
   Status: Incomplete => New

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

Title:
  Value in Yaru-dark/gnome-shell/gnome-shell.css not used

Status in gnome-shell package in Ubuntu:
  New
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  The value for selected-color at line 153 in the gnome-shell.css files for 
Yaru and Yaru-dark is ignored by the shell. (Selected text should change color 
from dark grey to white.)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-17 (214 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: yaru-theme
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxsf
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1866134] Re: Yaru icons are not shown in Gnome-Software

2020-05-18 Thread Ken VanDine

** Changed in: snap-store
   Status: Triaged => Fix Committed

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

Title:
  Yaru icons are not shown in Gnome-Software

Status in GNOME Software:
  New
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  When an icon theme different from Adwaita is selected, the icons from
  that theme are not shown in Gnome-Software.

  This is confusing for user because they now see two different icons
  for the same application (see the screenshot upstream).

  It would be great if Gnome-Software would look for the icon in the
  selected icon theme.

  
  

  Reported upstream here: https://gitlab.gnome.org/GNOME/gnome-
  software/issues/929

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

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

[Desktop-packages] [Bug 1878998] ShellJournal.txt

apport information

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

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

Title:
  Value in Yaru-dark/gnome-shell/gnome-shell.css not used

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in yaru-theme package in Ubuntu:
  Incomplete

Bug description:
  The value for selected-color at line 153 in the gnome-shell.css files for 
Yaru and Yaru-dark is ignored by the shell. (Selected text should change color 
from dark grey to white.)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-17 (214 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: yaru-theme
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxsf
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1878998] GsettingsChanges.txt

apport information

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

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

Title:
  Value in Yaru-dark/gnome-shell/gnome-shell.css not used

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in yaru-theme package in Ubuntu:
  Incomplete

Bug description:
  The value for selected-color at line 153 in the gnome-shell.css files for 
Yaru and Yaru-dark is ignored by the shell. (Selected text should change color 
from dark grey to white.)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-17 (214 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: yaru-theme
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxsf
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1878998] Re: Value in Yaru-dark/gnome-shell/gnome-shell.css not used

apport information

** Tags added: apport-collected focal

** Description changed:

- The value for selected-color at line 153 in the gnome-shell.css files
- for Yaru and Yaru-dark is ignored by the shell. (Selected text should
- change color from dark grey to white.)
+ The value for selected-color at line 153 in the gnome-shell.css files for 
Yaru and Yaru-dark is ignored by the shell. (Selected text should change color 
from dark grey to white.)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-10-17 (214 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Package: yaru-theme
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
+ RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
+ Tags:  focal
+ Uname: Linux 5.4.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: sudo vboxsf
+ _MarkForUpload: True

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

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

Title:
  Value in Yaru-dark/gnome-shell/gnome-shell.css not used

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in yaru-theme package in Ubuntu:
  Incomplete

Bug description:
  The value for selected-color at line 153 in the gnome-shell.css files for 
Yaru and Yaru-dark is ignored by the shell. (Selected text should change color 
from dark grey to white.)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-17 (214 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: yaru-theme
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxsf
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Value in Yaru-dark/gnome-shell/gnome-shell.css not used

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in yaru-theme package in Ubuntu:
  Incomplete

Bug description:
  The value for selected-color at line 153 in the gnome-shell.css files for 
Yaru and Yaru-dark is ignored by the shell. (Selected text should change color 
from dark grey to white.)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-17 (214 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: yaru-theme
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxsf
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed

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

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


** This bug has been marked a duplicate of bug 1874217
   [nvidia] Dual monitor setup with secondary monitor in portrait-right mode 
cause tiled windows to occupy 1.5 monitors

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-30 (383 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1878193] Re: Shell crashes and returns to the login screen

gnome-shell looks like the relevant crash here. I can see it is crashing
for you almost daily. Unfortunately none of those crashes are traceable,
which is a common problem with the Nvidia driver :(

Please check that you don't have any nonstandard gnome-shell extensions
installed, by running:

  gsettings list-recursively org.gnome.shell > settings.txt

and then attach the resulting text file here.

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

Title:
  Shell crashes and returns to the login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  from https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 14:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] 
[103c:8603]
  InstallationDate: Installed on 2020-04-24 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP OMEN by HP Laptop 17-cb0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8603
  dmi.board.vendor: HP
  dmi.board.version: 45.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-cb0xxx
  dmi.product.sku: 5VX37AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.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/1878193/+subscriptions

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

[Desktop-packages] [Bug 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.

Amr,

Please check that this command fixes the problem:

  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

after logging out and in again. If the leak still happens then please
don't comment here, but open a new bug by running:

  ubuntu-bug gnome-shell

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

Title:
  gnome-shell leaks hundreds of megabytes when the dock option 'show-
  trash' is enabled.

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  Gnome shell is the single largest resident memory user on my system.

  It was hovering at ~700mb, then with a few minutes of use of the
  system (nothing in particular, mostly shell windows, one google-chrome
  window) - spiked to ~980mb or so, before retreating to 903m.

  Even with 16gb of ram, that's a huge chunk of the system.

  I've not been able to identify anything in particular that I'm doing
  that triggers the growth.

  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1856838/comments/5, it was suggested to open a new bug,
  instead of adding to one of the several existing bugs for this.  I'm
  happy to help try and debug this, but it's not clear where to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 17:32:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-18 (532 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago)

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

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

[Desktop-packages] [Bug 1877589] Re: Wayland windows does not redraw itself

That version is not in updates yet. Are you sure you are using it?

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

Title:
  Wayland windows does not redraw itself

Status in mutter package in Ubuntu:
  New

Bug description:
  I'm not sure, if it is not a bug of certain Wayland applications.

  Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications,
  namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves
  unless I change their size, or switch to another window or overview.
  For example, audacity does not redraw current position marker, and I
  need to click with a mouse, or resize the window to see it. Firefox
  sometimes just freeze, until I click or until I resize its window, or
  I switch to overview.

  What kind of trace shoud I perform to obtain more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 17:27:24 2020
  InstallationDate: Installed on 2019-11-16 (173 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago)

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

Setting Invalid for Ubuntu 19.10, since the problem right now is in
mutter 3.36 and that's not in Ubuntu 19.10. But also 19.10 is just over
a month away from reaching end-of-life so I wouldn't bother with that
release even if it was affected.

** Changed in: mutter (Ubuntu Eoan)
   Status: Triaged => Invalid

** No longer affects: mutter (Ubuntu Eoan)

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions

** No longer affects: gnome-control-center

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

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2804
   Importance: Unknown
   Status: Unknown

** Tags added: fixed-in-3.36.3 fixed-upstream

** No longer affects: gnome-control-center (Ubuntu)

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

Title:
  Do Not Disturb setting does not persist across login sessions

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  gnome-control-center:
Installed: 1:3.36.1-1ubuntu5
Candidate: 1:3.36.1-1ubuntu5
Version table:
   *** 1:3.36.1-1ubuntu5 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Selecting do not disturb from settings does not persist across login
  sessions.

  What I did
  - Set Do Not Disturb in settings or from top bar to prevent pop-up 
notification banners from appearing, which it does.
  - logout and log back in
  - expect pop-up notifications to continue to be blocked and only displayed in 
the top bar

  What happens:
  - Do Not Disturb is reset to disabled on each new login

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 14:42:49 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-24 (270 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago)

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

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

[Desktop-packages] [Bug 1874219] Re: PC suspends after 20 minutes at the login screen

Yes I was thinking that... My development desktop (which is always a
fresh install) does not experience this bug.

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

Title:
   PC suspends after 20 minutes at the login screen

Status in gnome-control-center package in Ubuntu:
  Opinion
Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Same as LP: #1759325 in Bionic, but this time affecting Focal.

  After some update in the last month, my desktop PC now suspends after
  20 minutes at the login screen.

  I was able to override the setting for my user account by adjusting
  the power settings in gnome-control-center. I see no obvious way of
  overriding the default for the system.

  Asking on IRC, I was pointed at LP: #1868260, but got no response
  there.

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

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders

Before I move this bug, can anyone else confirm?

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders

Yeah it seems many of the dash/overview issues we have in Ubuntu are
actually due to the ubuntu-dock extension.

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-18 Thread Dusty

I am sorry. I tend to agree with others. A lot of us are endearing
folks. And when I say us I mean people already exposed and using a
distro. Only a portion of us though, so the rest will get fed up.

99% of new users will encounter this and just can the distro guys. The
majority would not even fool with it long enough to realize there's the
non-productive work around of pressing ctrl+c twice every time. Most
will just see it fails at something really basic and wonder what else it
fails at that they don't see yet, or just get frustrated and move on.

A basic function like this being broke should be a huge priority. But
from what I am reading here it has carried on into the next LTS version
without a fix as well...


Daniel, I don't see an option to select Ubuntu on Wayland on the login screen? 
I will have to figure that out. I haven't moved to 20.04 yet. Since the bug was 
still present I didn't get motivated to.

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1875285] Re: Fractional scaling zooms to 200% and crops half the screen

Nvidia users see also bug 1870736

** Summary changed:

- Ubuntu 20.04 Fractional scaling crops half the screen
+ Fractional scaling zooms to 200% and crops half the screen

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

Title:
  Fractional scaling zooms to 200% and crops half the screen

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 20.04 with a NVIDIA MX250. Firstly, nvidia-prime was not 
working. Even when selecting nvidia only, it was using Intel HD Graphics.
  [IMAGE1]

  I've forced the use of NVIDIA as the primary GPU by creating 
/etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf with: Option "PrimaryGPU" 
"yes" (seen here https://wiki.archlinux.org/index.php/NVIDIA_Optimus).
  [IMAGE2]
  This works, now nvidia-settings show all options (before was showing only 
prime options, and nothing more - even when selecting NVIDIA Only).

  But now, fractional scalling crops half of the screen. The funny thing
  is that when I try to printscreen, on the picture it looks fine, but
  in reality is not. I had to make a photo with my cellphone. As you can
  see, elements don't fit the screen (Note firefox title bar, for
  example).[IMAGE3]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 27 02:49:29 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

It sounds like bug 1875285 was also experienced by the original reporter
here...

Strictly speaking I intended for this bug to be more about "Selecting
scale 125% highlights 200% but actually renders at 100% still". Bug
1875285 will definitely confuse the matter though, as the screen may
literally scale up 200%. That's a separate bug which you might
experience at the same time :S

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

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

Diego, that is bug 1857383, not this one.

Alex, that sounds like bug 1875285 and bug 1874217, not this one. But
yes I can see there will be some confusion between bug 1875285 and here.

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen

cmpilato,

To avoid confusing symptoms between various peoples' machines please
open your own bug by running:

  ubuntu-bug gnome-shell


** Information type changed from Public to Private

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

Title:
  Memory usage grows when locking/unlocking the screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Many times after logging in gnome-shell uses 600-800MB of memory, and
  also slows down quite a bit (e.g., 20-30 seconds waiting for login).
  Only after multiple resets (Alt+F2 r) drops the memory usage below
  200MB. I use my computer mainly for work, and the above phenomenon is
  quite disturbing. After a couple of hours of work memory usage is
  growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't
  help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest
  Ubuntu also behaves similarly. This is an old issue, it was present in
  18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all
  of them suffer with this problem. Anyone can check this with the
  "gnome-shell memory monitor"  gnome-shell extension.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Oct 28 20:28:38 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-04 (297 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

Remember you can select 'Ubuntu on Wayland' on the login screen and that
will avoid this bug. At least those people not using Nvidia can...

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1347080] Re: gnome-shell memory leak

1. We don't support gnome-shell on Ubuntu 14.04

2. Ubuntu 14.04 is past end of standard support

3. If you want to continue discussing related issues then please open a
new bug by running:

   ubuntu-bug gnome-shell


** Changed in: gnome-shell (Ubuntu)
   Status: New => Won't Fix

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

Title:
  gnome-shell memory leak

Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  gnome-shell  consumes 1,6 giga memory

  
  (gnome-shell:27091): GLib-GObject-WARNING **: g_object_set_valist: object 
class 'ClutterSettings' has no property named 'window-scaling-factor'
  Gjs-Message: JS LOG: Failed to add search provider 
/usr/share/gnome-shell/search-providers/org.gnome.Weather.Application.search-provider.ini:
 TypeError: appInfo is null
  Gjs-Message: JS LOG: No permission to trigger offline updates: Polkit.Error: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action 
org.freedesktop.packagekit.trigger-offline-update is not registered
  Gjs-Message: JS LOG: GNOME Shell started at Tue Jul 22 2014 18:46:27 GMT+0100 
(BST)
  Gjs-Message: JS LOG: loading user theme: 
/usr/share//themes/Zukitwo-Shell/gnome-shell/gnome-shell.css
  [Fatal 18:46:29.401] [GLib] Source ID 6569 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6648 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6611 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6644 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6651 was not found when attempting to 
remove it
  Cairo.Surface is leaking, programmer is missing a call to Dispose
  Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
  [Fatal 18:46:29.402] [GLib] Source ID 6647 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6645 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6527 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6632 was not found when attempting to 
remove it
  [Fatal 18:46:29.404] [GLib] Source ID 6526 was not found when attempting to 
remove it
  [Fatal 18:46:29.404] [GLib] Source ID 6631 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6560 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6646 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6665 was not found when attempting to 
remove it
  Cairo.Surface is leaking, programmer is missing a call to Dispose
  Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
  [Fatal 18:46:29.405] [GLib] Source ID 6499 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6498 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6641 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6610 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6638 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6570 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6640 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6643 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6650 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6483 was not found when attempting to 
remove it
  Window manager warning: Log level 8: meta_window_raise: assertion 
'!window->override_redirect' failed
  Window manager warning: Log level 8: meta_window_raise: assertion 
'!window->override_redirect' failed
  Window manager warning: Log level 8: meta_window_lower: assertion 
'!window->override_redirect' failed

  ii  gnome-accessibility-themes  
3.12.0-1ubuntu1~trusty1 all  Accessibility 
themes for the GNOME desktop
  ii  gnome-applets   
3.5.92-0ubuntu3 amd64Various 
applets for the GNOME panel - binary files
  ii  gnome-applets-data  
3.5.92-0ubuntu3 all  Various 
applets for the GNOME panel - data files
  ii  gnome-backgrounds   
3.12.2-1~trusty1all  Set of 
backgrounds packaged with the GNOME desktop
  ii  gnome-bluetooth 
3.9.3really3.8.1-2ubuntu2   amd64GNOME 
Bluetooth tools
  ii  gnome-boxes 
3.12.3-1~trusty1

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

Karl,

1. Please check the version you have installed:

   dpkg -s libmutter-6-0 | grep Version

   What does it report?

2. Please make sure you have rebooted after installing the new version.

3. Even if the fix still doesn't work for you then I think we should
release it anyway as it helps other people. Then you can open a new bug
after that.

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

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

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

Bug description:
  [ Impact ]

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

  [ Test case ]

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

  [ Regression potential ]

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

  - Configuration is not restored at all.

  [ Known issue ]

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

  
  -

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

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

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2020-05-18 Thread Wilson Wang

I also experienced regular system freeze when playing youtube videos.
The freeze would not occur after removing xserver-xorg-video-intel. I am
on 20.04.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1878998] Re: Value in gnome-shell.css not used

OK we can separate this bug again, but:

1. Please run 'apport-collect 1878998' to complete the bug report
process. It will attach more info about the machine; and

2. I still think bug 1842886 is masking this and may need fixing first.

** This bug is no longer a duplicate of bug 1842886
   Yaru-dark shell menus and dialogs are not dark

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

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Value in gnome-shell.css not used
+ Value in Yaru-dark/gnome-shell/gnome-shell.css not used

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

Title:
  Value in Yaru-dark/gnome-shell/gnome-shell.css not used

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in yaru-theme package in Ubuntu:
  Incomplete

Bug description:
  The value for selected-color at line 153 in the gnome-shell.css files
  for Yaru and Yaru-dark is ignored by the shell. (Selected text should
  change color from dark grey to white.)

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

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

[Desktop-packages] [Bug 1879043] Re: gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

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

Try using 'apport-cli' instead of 'ubuntu-bug'. That should give you a
link you can then copy and paste into any web browser to complete the
process.

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

Title:
  gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It might be bug 184.
  This is a new installation. During the installation After each change I made 
Suspend and restarted the computer and checked if gnome-shell had crashed.
  Installed: Printer, Flatpaks, Sensory Perceptions, AlternateTab, Applications 
Menu, OpenWeather and Dash to Panel without crash.
  The last thing I did before the crash was to "install" Gmail and Google 
Calender and put all my favorite applications in the panel. Left the computer 
to suspend, after 15 minutes, and restarted the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 11:11:09 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879352] Re: /usr/bin/im-launch i3 fails

2020-05-18 Thread Wl-dustin

I was able to fix this by changing

```
exec $STARTUP
```

to

```
$STARTUP
```

Interestingly, this doesn't leave a shell process running -- it leaves
`gdm-x-session` running.  So perhaps that is emulating a shell somehow,
but gets the unquoting wrong for `exec`?

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

Title:
  /usr/bin/im-launch i3 fails

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying to run i3 in Focal Fossa, login fails.  The screen goes black
  briefly, then returns to the login screen.  I expect this is
  reproducible by just installing `i3`, selecting it on the settings in
  the login screen, and logging in.

  I see the following in the log:
  ```
  May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: 
/etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such 
file or directory
  ```

  Editing that file to just run `/usr/bin/im-launch i3` works fine.  Is
  this some kind of shell quoting issue, where it's trying to execve
  that full string?

  I believe this is in the `x11-common` package:
  ```
  hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start 
  x11-common: /etc/X11/Xsession.d/99x11-common_start
  ```
  but Launchpad complains that such a thing does not exist.  Perhaps I 
misunderstand "package".

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

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-05-18 Thread Matt Lee

Thanks Olivier. I'll keep my eye out for that, so I can test

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Beta Chromium 80 Snap with vaapi enabled :

  https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-
  source-enable-
  vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap

  Install it with --devmode

  
  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

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

[Desktop-packages] [Bug 1879417] [NEW] with default font, empty lines have different height to non-empty lines

2020-05-18 Thread Andy Owen

Public bug reported:

I suspect this bug is not a gedit bug, but a font bug, however I'm not
sure.

Steps to reproduce:

1) Ensure font is the default "Use the system fixed width font (Ubuntu
Mono 13)" is checked.

2) Create two tabs, in one tab write:

1
2
3
4

In the other tab, write:




4

Switch between the tabs and observer that line 4 is in a different
location in each tab.

Using a different font "Monospace Regular 12" makes the problem go away,
hence I suspect the problem is the font.

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

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

Title:
  with default font, empty lines have different height to non-empty
  lines

Status in gedit package in Ubuntu:
  New

Bug description:
  I suspect this bug is not a gedit bug, but a font bug, however I'm not
  sure.

  Steps to reproduce:

  1) Ensure font is the default "Use the system fixed width font (Ubuntu
  Mono 13)" is checked.

  2) Create two tabs, in one tab write:

  1
  2
  3
  4

  In the other tab, write:

  
  
  
  4

  Switch between the tabs and observer that line 4 is in a different
  location in each tab.

  Using a different font "Monospace Regular 12" makes the problem go
  away, hence I suspect the problem is the font.

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

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

[Desktop-packages] [Bug 1879402] Re: Proper monitor resolution/refresh rate not available

2020-05-18 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Proper monitor resolution/refresh rate not available

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 
59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This 
problem appeared after plugging in my old monitor after 2 years again, it's a 
philips 272g.  Things that I unsuccesfully tried to get a proper resolution:
  -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use 
different drivers: propritary and open source
  -Change resolution via xrandr addmode/newmode (leads to "no signal" from 
monitor)
  -Using "GRUB_GFXMODE" config in grub (no change)
  -Searching through logs, only useleful thing I found was in the Xorg log:
  [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0
  [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
  [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9   25.18  640 656 752 800 
 480 490 492 525 -hsync -vsync (31.5 kHz e)
  -In Windows the resolution works fine
  -Both GPUs work fine with a different monitor
  I'm not sure how to proceed here nor do I know where the problem lies. I 
assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers 
lead to this problem making it unlikely to be a driver problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.4.0-050400-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 18 22:16:58 2020
  DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1002:0b36]
  InstallationDate: Installed on 2019-11-26 (173 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic 
root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.LQ
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 PC MATE (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f
  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
  xserver.bootTime: Tue Nov 26 22:01:15 2019
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.5+git20191008-0ubuntu1

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

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

[Desktop-packages] [Bug 1879402] [NEW] Proper monitor resolution/refresh rate not available

You have been subscribed to a public bug:

I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, 
what I want to have is the monitor specs: 1080p and 144 Hz. This problem 
appeared after plugging in my old monitor after 2 years again, it's a philips 
272g.  Things that I unsuccesfully tried to get a proper resolution:
-Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different 
drivers: propritary and open source
-Change resolution via xrandr addmode/newmode (leads to "no signal" from 
monitor)
-Using "GRUB_GFXMODE" config in grub (no change)
-Searching through logs, only useleful thing I found was in the Xorg log:
[12.117] (II) AMDGPU(0): EDID for output DisplayPort-0
[12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
[12.117] (II) AMDGPU(0): Modeline "640x480"x59.9   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)
-In Windows the resolution works fine
-Both GPUs work fine with a different monitor
I'm not sure how to proceed here nor do I know where the problem lies. I assume 
this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to 
this problem making it unlikely to be a driver problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.4.0-050400-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 18 22:16:58 2020
DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1002:0b36]
InstallationDate: Installed on 2019-11-26 (173 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic 
root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.LQ
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 PC MATE (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f
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
xserver.bootTime: Tue Nov 26 22:01:15 2019
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.5+git20191008-0ubuntu1

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


** Tags: amd64 apport-bug focal resolution third-party-packages ubuntu
-- 
Proper monitor resolution/refresh rate not available
https://bugs.launchpad.net/bugs/1879402
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 1879409] Re: nautilus crashed with SIGSEGV

2020-05-18 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1879409/+attachment/5373762/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1879409/+attachment/5373764/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1879409/+attachment/5373768/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1879409/+attachment/5373769/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1879409/+attachment/5373770/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1879409/+attachment/5373771/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1879409/+attachment/5373772/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1857539
   nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  New

Bug description:
  Just restarted Ubuntu 20.10

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.37.1.1-1ubuntu1
  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 nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu34
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 19:01:33 2020
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1448, 807)'
  InstallationDate: Installed on 2020-05-18 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200518)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7f4cce623ac2:mov0x380(%rax),%rax
   PC (0x7f4cce623ac2) 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 docker 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/1879409/+subscriptions

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

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

2020-05-18 Thread Karl Nicoll

Hi Daniel,

Unsure if your response was aimed at me, but I can confirm that the
behaviour is still present for me and that neither of those criteria
apply to me. I'm using AMDGPU (AMD Radeon 5700XT) with three monitors
attached and fractional scaling enabled.

Additional Observations
===

* With Fractional Scaling enabled, but all three screens at 100%, display 
layout is restored at startup.
* With Fractional Scaling enabled, but screen 3 (the 4k monitor) set at 125% or 
150% scaling, the monitor layout and scaling are reset at startup.

If there's any more information you need, I'm happy to help, just let me
know what you need!

Thanks,

Karl

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

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

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

Bug description:
  [ Impact ]

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

  [ Test case ]

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

  [ Regression potential ]

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

  - Configuration is not restored at all.

  [ Known issue ]

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

  
  -

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

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

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

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

[Desktop-packages] [Bug 1879406] Re: Dark mode on gedit - unable to see text

2020-05-18 Thread Paul White

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

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

Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1857191
   Dark themes don't work well with highlighted current line in gedit

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

Title:
  Dark mode on gedit - unable to see text

Status in gedit package in Ubuntu:
  New

Bug description:
  Unable to see current line of text on gedit when in dark mode and with
  default gedit setting to highlight current line. Highilght is the same
  colour as the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 22:20:55 2020
  InstallationDate: Installed on 2020-05-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879385] Re: Unable to star files and folders in Dropbox folder in Ubuntu 20.04

2020-05-18 Thread Paul White

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

** Tags removed: nautilus
** Tags added: focal

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

Title:
  Unable to star files and folders in Dropbox folder in Ubuntu 20.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  It is impossible to star files or folder inside Dropbox folder. There
  is no menu in Nautilus after right click on file. Outside the Dropbox
  folder it works fine. I am not sure if it is bug of Dropbox extension
  or Nautilus.

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

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

[Desktop-packages] [Bug 1879385] [NEW] Unable to star files and folders in Dropbox folder in Ubuntu 20.04

You have been subscribed to a public bug:

It is impossible to star files or folder inside Dropbox folder. There is
no menu in Nautilus after right click on file. Outside the Dropbox
folder it works fine. I am not sure if it is bug of Dropbox extension or
Nautilus.

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


** Tags: dropbox nautilus
-- 
Unable to star files and folders in Dropbox folder in Ubuntu 20.04
https://bugs.launchpad.net/bugs/1879385
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 1879058] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-30 (383 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed

apport information

** Tags added: apport-collected focal

** Description changed:

  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.
  
- This issue can be more or less circumvented using Nvidia Tools to
- configure displays. With it, the viewport seems to work correctly.
- However, as soon as a screen is disconnected, the system reconfigure the
- various displays and the issue comes back. So often, after a sleep or
- something like that, the issue comes back.
+ This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-04-30 (383 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 3.36.1-5ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
+ RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
+ Tags:  focal
+ Uname: Linux 5.4.0-29-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-30 (383 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879058] GsettingsChanges.txt

apport information

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

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-30 (383 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879058] monitors.xml.txt

apport information

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

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-30 (383 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-30 (383 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879058] ShellJournal.txt

apport information

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

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to configure 
displays. With it, the viewport seems to work correctly. However, as soon as a 
screen is disconnected, the system reconfigure the various displays and the 
issue comes back. So often, after a sleep or something like that, the issue 
comes back.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-30 (383 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879406] [NEW] Dark mode on gedit - unable to see text

2020-05-18 Thread Pedro Galvao

Public bug reported:

Unable to see current line of text on gedit when in dark mode and with
default gedit setting to highlight current line. Highilght is the same
colour as the text.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gedit 3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 18 22:20:55 2020
InstallationDate: Installed on 2020-05-17 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Dark mode on gedit - unable to see text

Status in gedit package in Ubuntu:
  New

Bug description:
  Unable to see current line of text on gedit when in dark mode and with
  default gedit setting to highlight current line. Highilght is the same
  colour as the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gedit 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 22:20:55 2020
  InstallationDate: Installed on 2020-05-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852183]

2020-05-18 Thread Carlos Sevcik

Occurs in LO 7.0.0-Alpha too Linux+GNOME

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1852183]

2020-05-18 Thread Carlos Sevcik

All reports suggest that the bug occurs under Linux+GNOME, yet all other
Linux+GNOME applications do mouse copy/pastes OK.

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1852183]

2020-05-18 Thread timur

*** Bug 130012 has been marked as a duplicate of this bug. ***

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed

Indeed, it looks very much like  bug #1874217

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to
  configure displays. With it, the viewport seems to work correctly.
  However, as soon as a screen is disconnected, the system reconfigure
  the various displays and the issue comes back. So often, after a sleep
  or something like that, the issue comes back.

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

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

[Desktop-packages] [Bug 1879401] [NEW] [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound rarely works

2020-05-18 Thread Nathan Bryant

Public bug reported:

I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting to
a TV over HDMI via a Novoo USB-C multiport adapter. This is not a
Thunderbolt device, it is just USB-C.

It seemed like things used to work fine before I upgraded this system
from Ubuntu 19.10 to 20.04, although I couldn't say for certain at this
point. But I'm having a ton of difficulty getting audio output over
HDMI. Getting it to work requires a lot of retries to reinitialize the
device (either by suspending/resuming the laptop, or plugging/unplugging
the HDMI cable and/or the multiport adapter). It does work sometimes,
but my success rate is very low at this point.

Even when it does work, it's brittle: any change to the output port (to
speaker and back to HDMI, or from stereo to surround and back) will
often break the audio. This fact seems to suggest that the problem
doesn't have anything to do with the low-level initialization of the
HDMI port; I'd be looking at some mid-layer code.

To be clear, there doesn't seem to be any particular symptom, or
anything of interest in the logs, other than an absence of sound output.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
Uname: Linux 5.6.0-1010-oem x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nbryant1510 F pulseaudio
 /dev/snd/pcmC0D9p:   nbryant1510 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 18 17:32:11 2020
InstallationDate: Installed on 2020-01-31 (108 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_PulseAudioLog:
 May 18 16:36:42 atlantis dbus-daemon[633]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.41' (uid=124 pid=1116 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 May 18 16:36:53 atlantis systemd[1109]: pulseaudio.service: Succeeded.
 May 18 16:37:03 atlantis systemd[1109]: pulseaudio.socket: Succeeded.
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] fails after 
a while
UpgradeStatus: Upgraded to focal on 2020-04-21 (27 days ago)
dmi.bios.date: 03/02/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.1
dmi.board.name: 06CDVY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390 2-in-1
dmi.product.sku: 08B0
dmi.sys.vendor: Dell Inc.

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

Title:
  [XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound
  rarely works

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have an Ice Lake laptop (Dell 7390 2-in-one) which I am connecting
  to a TV over HDMI via a Novoo USB-C multiport adapter. This is not a
  Thunderbolt device, it is just USB-C.

  It seemed like things used to work fine before I upgraded this system
  from Ubuntu 19.10 to 20.04, although I couldn't say for certain at
  this point. But I'm having a ton of difficulty getting audio output
  over HDMI. Getting it to work requires a lot of retries to
  reinitialize the device (either by suspending/resuming the laptop, or
  plugging/unplugging the HDMI cable and/or the multiport adapter). It
  does work sometimes, but my success rate is very low at this point.

  Even when it does work, it's brittle: any change to the output port
  (to speaker and back to HDMI, or from stereo to surround and back)
  will often break the audio. This fact seems to suggest that the
  problem doesn't have anything to do with the low-level initialization
  of the HDMI port; I'd be looking at some mid-layer code.

  To be clear, there doesn't seem to be any particular symptom, or
  anything of interest in the logs, other than an absence of sound
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Uname: Linux 5.6.0-1010-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:

Re: [Desktop-packages] [Bug 1878666] Re: Firefox snap is very slow (30 sec) to start

2020-05-18 Thread Tommaso

No, always the same mistake:

tommi@tommi-pc:~$ snap run firefox
error: cannot find current revision for snap firefox: readlink
/snap/firefox/current: no such file or directory

I'm sorry,
Tom

Il giorno lun 18 mag 2020 alle ore 23:20 Olivier Tilloy <
olivier.til...@canonical.com> ha scritto:

> That's puzzling. And if you run "snap run firefox", the browser starts?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1878666
>
> Title:
>   Firefox snap is very slow (30 sec) to start
>
> Status in firefox package in Ubuntu:
>   New
>
> Bug description:
>   Firefox snap is very slow, when i start it
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.36.1-5ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
>   Uname: Linux 5.4.0-29-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu May 14 19:53:08 2020
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-04-25 (18 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878666/+subscriptions
>


-- 
Tommaso Trombetta

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

Title:
  Firefox snap is very slow (30 sec) to start

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox snap is very slow, when i start it

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 19:53:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-25 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879282] Re: Workspace shows windows that is not on the current workspace

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

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

Title:
  Workspace shows windows that is not on the current workspace

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  If I have two workspaces and have for example firefox on both
  workspaces, then the second workspace will show the firefox windows
  that is on the first workspace. I can not controll this window, its
  just a piece of the background. I get this problem 100% of the time.
  The way I get it is by being on my second workspace, howering my
  pointer over the firefox on my topbar, go through the windows of the
  windows open for firefox, which makes my screen jump to the first
  window when i hower over the firefox window that is open on the first
  workspace, to indicate where it is located. Then when i click on the
  firefox window that is on the second workspace, the window from the
  first workspace is "stuck" as a wallpaper.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:59:15 2020
  DistUpgraded: 2020-04-26 19:27:56,468 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1740]
  InstallationDate: Installed on 2020-04-17 (30 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58e4 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=dc6ec013-e29e-4a5e-8dd0-17ae3cf639fc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-26 (21 days ago)
  dmi.bios.date: 11/14/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UA
  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.:bvrUX430UA.304:bd11/14/2017:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/1879282/+subscriptions

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

[Desktop-packages] [Bug 1879326] Re: DNS resolution ceased to work after update

Thank you for your bug report. Could you check in /var/log/dpkg.log what
was updated before you started getting the issue?

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  DNS resolution ceased to work after update

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Hi

  I did a Focal install on 14th of May 2020, could work until in the
  night of 16th of May 2020 and in the morning of the 18th of May 2020 I
  could not resolve domain names anymore. I can ping DNS servers but the
  resolution to IP addresses fails. I have switched on automatic
  installation of security relevant updates.

  I can reproduce the behaviour with a fresh install accepting all the
  updates there are. I did not try to find out which update is the
  cause.

  See the behaviour below where I even have tried to work around by removing 
the DNS server of my router:
  thiemo @ Fujitsu-HO ~ :-( % systemd-resolve --status  
20-05-18 12:54
  Global
 LLMNR setting: no
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (enp0s25)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 139.18.25.33
139.18.25.34
77.59.232.36
62.167.241.5
62.2.107.35
62.2.121.84
62.2.121.88
fd00::7eff:4dff:feaa:2528
2001:638:902:1::10
DNS Domain: ~.
  thiemo @ Fujitsu-HO ~ % host -v myworkspaceinet.post.ch   
20-05-18 12:54
  Trying "myworkspaceinet.post.ch"
  ;; connection timed out; no servers could be reached

  thiemo @ Fujitsu-HO ~ :-( % alias pong
20-05-18 12:55
  pong='ping -c3'
  thiemo @ Fujitsu-HO ~ % pong 139.18.25.33 
20-05-18 12:58
  PING 139.18.25.33 (139.18.25.33) 56(84) bytes of data.
  64 bytes from 139.18.25.33: icmp_seq=1 ttl=246 time=39.9 ms
  64 bytes from 139.18.25.33: icmp_seq=2 ttl=246 time=39.0 ms
  64 bytes from 139.18.25.33: icmp_seq=3 ttl=246 time=39.4 ms

  --- 139.18.25.33 ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2003ms
  rtt min/avg/max/mdev = 39.000/39.431/39.868/0.354 ms

  Kind regards

  Thiemo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon May 18 13:03:40 2020
  InstallationDate: Installed on 2020-05-15 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.178.1 dev enp0s25 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.178.0/24 dev enp0s25 proto kernel scope link src 192.168.178.33 
metric 100
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID

[Desktop-packages] [Bug 1879330] Re: Copy of .xcf thumbnails does not work

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

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

Title:
  Copy of .xcf thumbnails does not work

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have a folder with an .xcf (GIMP) image, the image has a correct thumbnail 
in the nautilus window. When I copy (cut+paste) the image in the same folder 
the thumbnail is empty.
  If I copy the image from a different folder the thumbnail shows the logo of 
GIMP.
  In both cases the thumbnail is WRONG.
  Doing the same with a .jpg or .png image the thumbnails are correct. 
  The same problem happens in Ubuntu 20.04 and 20.10 
  See the attached image

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.37.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu34
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 15:21:24 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(653, 418)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2020-05-11 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200511)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1879362] Re: image viewer long display png file and then fall xorg

Thank you for your bug report. Is the issue specific to a file? If so
could you attach it to the report?

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

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

Title:
  image viewer long display png file and then fall xorg

Status in eog package in Ubuntu:
  Incomplete

Bug description:
  it takes a very long time to display the png file. then xorg crashes
  and a session login window appears. if this error is not resolved soon
  I will be forced to switch to Microsoft Windows. Sorry but i must
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: eog 3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 18:17:47 2020
  InstallationDate: Installed on 2020-04-26 (22 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879375] Re: Images thumbnails doesn't update on image changes

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Images thumbnails doesn't update on image changes

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Committed

Bug description:
  [ Impact ]

  Image thumbnails are not refreshed on file changes

  [ Test case ]

  1. Create a new image and save it in the desktop using your image editor
  2. Change the image content and save
  3. The image thumbnail in the desktop should reflect the changes

  [ Regression potential ]

  Icons updates (and so redraws) may increase even when there are no
  actual changes to perform.

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

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

[Desktop-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed

sounds similar to bug #1874217

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to
  configure displays. With it, the viewport seems to work correctly.
  However, as soon as a screen is disconnected, the system reconfigure
  the various displays and the issue comes back. So often, after a sleep
  or something like that, the issue comes back.

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

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

[Desktop-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed

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

  apport-collect 1879058

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

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

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

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

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

Title:
  Display viewport incorrect with 90° rotated displayed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system which automatically configure the position and size of the display 
seems to not handle the display viewport correctly.
  When configuring the position of displays with Ubuntu display settings 
interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, 
then it seems the viewport or virtual display (I don't really know how you name 
is) seems to be 1920x1920. So the desktop is bigger than the screen and it can 
be moved with the mouse. Considering I use multi screens (3 rotated and one 
normal) it makes some crazy things.
  So my feeling is that while the screen is rotated, the viewport definition 
remains 1920x1080 instead of 1080x1920, and the system resolve it by providing 
a viewport of 1920x1920.

  This issue can be more or less circumvented using Nvidia Tools to
  configure displays. With it, the viewport seems to work correctly.
  However, as soon as a screen is disconnected, the system reconfigure
  the various displays and the issue comes back. So often, after a sleep
  or something like that, the issue comes back.

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

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

[Desktop-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

The log has iptables errors

May 18 14:50:08 julep NetworkManager[1050]:   [1589806208.0498] 
Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlp3s0 
--protocol tcp --destination-port 53 --jump ACCEPT
May 18 14:50:08 julep NetworkManager[1050]:   [1589806208.0512] Error 
executing command: Failed to execute child process â€œ/sbin/iptablesâ€ (No 
such file or directory)

Do you have iptables installed? could you do
$ which iptables?

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+subscriptions

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

[Desktop-packages] [Bug 1878666] Re: Firefox snap is very slow (30 sec) to start

2020-05-18 Thread Olivier Tilloy

That's puzzling. And if you run "snap run firefox", the browser starts?

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

Title:
  Firefox snap is very slow (30 sec) to start

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox snap is very slow, when i start it

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 19:53:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-25 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1878301] Re: Focal regression: poor discoverability for search in Ubuntu Software Center

2020-05-18 Thread Dan Dascalescu

@seb128: Maybe I didn't notice the search being this undiscoverable, or
maybe I was using another theme that made it more obvious

@amr: "just start typing" is not a discoverability UX hint. Users don't
randomly start typing in dialogs without inputs. MAYBE the keyboard
fanatics will try '?', but those use apt directly. IMO gnome-software
should be as friendly as possible to people new to Ubuntu.

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

Title:
  Focal regression: poor discoverability for search in Ubuntu Software
  Center

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  I wanted to install a new package. Launched Ubuntu Software and... how
  do I search for anything?

  Search is a key function. It should be front and center. I couldn't
  see it.

  That was annoying enough that I wanted to file a bug against it. In
  the process I did notice the lens icon in the top left, but seriously
  - does that look easily discoverable to anyone? There's usually
  nothing in that cornerl so users don't look there, and the contrast is
  poor, which makes it very easy to not notice.

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

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

[Desktop-packages] [Bug 1873301] Re: charmap command missing after upgrade to 20.04 (Focal Fossa)

** Changed in: gucharmap (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  charmap command missing after upgrade to 20.04 (Focal Fossa)

Status in gucharmap package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading to the Ubuntu 20.04 LTS beta (gucharmap version
  1:13.0.1-1), I found that the charmap command was missing. After some
  searching I discovered it still exists with the name gucharmap. Maybe
  it was always called gucharmap and there used to be a symlink from
  charmap which the upgrade removed?

  The charmap(1) manpage still exists, as a symlink to gucharmap. It's
  weird having a manpage for a command that doesn't exist.

  Please could we have a charmap symlink (back)? At least some users are
  used to using that name.

  The changelog mentions previously fixing the charmap symlink in version 
0.6.0-1:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187522

  and installing the charmap.1 link in version 1:2.24.2-1.

  I couldn't see anything in there suggesting that the removal of the
  charmap symlink was intentional. Thanks.

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

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

[Desktop-packages] [Bug 1876510] Re: Print window too big for a 1366x768 screen

2020-05-18 Thread Heather Ellsworth

** Tags added: rls-ff-incoming

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

Title:
  Print window too big for a 1366x768 screen

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  On libreoffice write the window displayed for print is too big for a standard 
laptop screen 1366x768 so some important buttons are not visible and print 
can't be done
  see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.2-0ubuntu3
  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
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 20:54:16 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-24 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-18 Thread Hooman

I noticed the iptables needed for the hotspot to work are not set when
the hotspot is enabled.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a machine with a wired network connection and a wifi card. I've
  been using the machine as a wireless router and server in my house.
  I've attached a screenshot of the Wi-Fi network settings. It looks as
  expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+subscriptions

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

[Desktop-packages] [Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)

2020-05-18 Thread John Jacob

You can see the core at
https://errors.ubuntu.com/user/e35124d979e3b918d0a8f821141d16026a6862cda0707840355369e69b328df9d3a372a704b7af732e746e1600eb565efebfb0f79a83711873cfbe43fe12a08c

Killing the gnome-shell process resolves the freeze and the login
continues normally after that.

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

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

Title:
  wayland session hard freezes on login from GDM (X11 session works
  fine)

Status in mutter package in Ubuntu:
  New

Bug description:
  When I login to my laptop running Ubuntu 20.04, after entering my
  username, when I choose the "gear" button and select Ubuntu on Wayland
  as the session type, my laptop freezes hard. Mouse and keyboard do not
  respond, and the first three times I hit this issue I had to forcibly
  power off. The normal (X11) Ubuntu session works fine.

  However, I realized that I could still ping and ssh in, and doing that
  gave me some clues to the issue.

  I have keychain installed for password-less SSH, and my bash_profile has:
  ---
  #!/bin/bash
  # Get the aliases and functions
  if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
  fi

  # Setup password-less SSH
  [ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
  keychain $HOME/.ssh/id_rsa
  source $HOME/.keychain/${HOSTNAME}-sh
  ---

  When I login via SSH from another machine after hitting the issue, I get:
  [johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
  Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  
  0 updates can be installed immediately.
  0 of these updates are security updates.

  Your Hardware Enablement Stack (HWE) is supported until April 2025.
  Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3

   * keychain 2.8.5 ~ http://www.funtoo.org
   * Waiting 5 seconds for lock...
   * Found existing ssh-agent: 2086
   * Adding 1 ssh key(s): /home/john/.ssh/id_rsa
  Enter passphrase for /home/john/.ssh/id_rsa: 
   * ssh-add: Identities added: /home/john/.ssh/id_rsa
  [john@andromeda: ~] pstree
  systemd─┬─NetworkManager───2*[{NetworkManager}]
  ├─accounts-daemon───2*[{accounts-daemon}]
  ├─acpid
  ├─avahi-daemon───avahi-daemon
  ├─bluetoothd
  ├─boltd───2*[{boltd}]
  ├─colord───2*[{colord}]
  ├─containerd───13*[{containerd}]
  ├─cron
  ├─cups-browsed───2*[{cups-browsed}]
  ├─cupsd
  ├─dbus-daemon
  ├─dnsmasq───dnsmasq
  
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
  │  │ │ └─2*[{gdm-wayland-ses}]
  │  │ └─2*[{gdm-session-wor}]
  │  └─2*[{gdm3}]
  ├─gnome-keyring-d───2*[{gnome-keyring-d}]
  ├─iio-sensor-prox───2*[{iio-sensor-prox}]
  ├─irqbalance───{irqbalance}
  ├─2*[kerneloops]
  ├─libvirtd───16*[{libvirtd}]
  ├─networkd-dispat
  ├─packagekitd───2*[{packagekitd}]
  ├─polkitd───2*[{polkitd}]
  ├─rsyslogd───3*[{rsyslogd}]
  ├─rtkit-daemon───2*[{rtkit-daemon}]
  ├─ssh-agent
  ├─sshd───sshd───sshd───bash───pstree
  ├─switcheroo-cont───2*[{switcheroo-cont}]
  ├─systemd─┬─(sd-pam)
  │ ├─at-spi-bus-laun─┬─dbus-daemon
  │ │ └─3*[{at-spi-bus-laun}]
  │ ├─at-spi2-registr───2*[{at-spi2-registr}]
  │ ├─dbus-daemon
  │ ├─dconf-service───2*[{dconf-service}]
  │ ├─gjs───10*[{gjs}]
  │ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
  │ ├─gnome-session-b───3*[{gnome-session-b}]
  │ ├─gnome-session-c───{gnome-session-c}
  │ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
  │ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
  │ │ │ 
├─ibus-engine-sim───2*[{ibus-engi+
  │ │ │ └─2*[{ibus-daemon}]
  │ │ └─16*[{gnome-shell}]
  │ ├─goa-daemon───3*[{goa-daemon}]
  │ ├─goa-identity-se───2*[{goa-identity-se}]
  │ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
  │ ├─gsd-color───3*[{gsd-color}]
  │ ├─gsd-keyboard───3*[{gsd-keyboard}]
  │ ├─gsd-media-keys───3*[{gsd-media-keys}]
  │ ├─gsd-power───3*[{gsd-power}]

[Desktop-packages] [Bug 1864178] Re: Rhythmbox crashes when trying to connect to iPhone

2020-05-18 Thread Bug Watch Updater

** Changed in: rhythmbox
   Status: Unknown => New

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

Title:
  Rhythmbox crashes when trying to connect to iPhone

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  I connected my iPhone to my laptop running Ubuntu 19.10. Nautilus and 
Shotwell loaded the device fine. But when I open Rhythmbox, it crashes. 
  I opened Rhythmbox from the terminal to see the error and I got this

  ```
  (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-repeat can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)

  (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-shuffle can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)
  **
  Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion 
failed: (strlen (uri) >= 46)
  Bail out! Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: 
assertion failed: (strlen (uri) >= 46)
  [1]15045 abort (core dumped)  rhythmbox
  ```

  Details of the current system:

  ```
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  ```

  ```
  apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.3-2ubuntu1
Candidate: 3.4.3-2ubuntu1
Version table:
   *** 3.4.3-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  ```

  What I expected to happen:
  I was expected Rhythmbox to show my iPhone under "devices"

  What actually happned:
  Rhythmbox just crashed

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

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

[Desktop-packages] [Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

2020-05-18 Thread Daniel Letzeisen

** Description changed:

  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d
  
  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52
  
  Should Xubuntu default to a different camera program, such as guvcview?
+ 
+ (Partial?) WORKAROUND is to use dconf-editor:
+ dconf-editor /org/gnome/cheese

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

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Triaged

Bug description:
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-18 Thread Pablo San Martín

On Ubuntu 20.04, I had the issue of copy-paste working every other time,
specifically on LibreOffice apps (Writer, Calc and Draw), not in any
other apps (Gedit, Firefox, Thunderbird, etc.) or in the GNOME Shell.

However, disabling the Clipboard Indicator extension fixed this for me.

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions

The issue was in gnome-shell and a fix has been commited to git now

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Invalid

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

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

Title:
  Do Not Disturb setting does not persist across login sessions

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  gnome-control-center:
Installed: 1:3.36.1-1ubuntu5
Candidate: 1:3.36.1-1ubuntu5
Version table:
   *** 1:3.36.1-1ubuntu5 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Selecting do not disturb from settings does not persist across login
  sessions.

  What I did
  - Set Do Not Disturb in settings or from top bar to prevent pop-up 
notification banners from appearing, which it does.
  - logout and log back in
  - expect pop-up notifications to continue to be blocked and only displayed in 
the top bar

  What happens:
  - Do Not Disturb is reset to disabled on each new login

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 19 14:42:49 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-24 (270 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago)

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

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

[Desktop-packages] [Bug 1877589] Re: Wayland windows does not redraw itself

2020-05-18 Thread Ben Aceler

After updating to 3.36.2 problem still occurs.

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

Title:
  Wayland windows does not redraw itself

Status in mutter package in Ubuntu:
  New

Bug description:
  I'm not sure, if it is not a bug of certain Wayland applications.

  Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications,
  namely Audacity(2.3.3) and Firefox (76.0), does not redraw themselves
  unless I change their size, or switch to another window or overview.
  For example, audacity does not redraw current position marker, and I
  need to click with a mouse, or resize the window to see it. Firefox
  sometimes just freeze, until I click or until I resize its window, or
  I switch to overview.

  What kind of trace shoud I perform to obtain more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-session-wayland (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  8 17:27:24 2020
  InstallationDate: Installed on 2019-11-16 (173 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago)

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

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

[Desktop-packages] [Bug 1879389] [NEW] random freezes and xorg dies sending me back to login screen

2020-05-18 Thread Gilbertf

Public bug reported:

branch new dell xps 2020
machine randomly freezes and xorg dies on me
nothing in /var/crash
but everything opened, not saved, is lost. i am sent back to login screen.

machine has latest bios (1.0.7)
is up to date regarding its ubuntu 18.04

i am seeing this in my kern.log which makes me suspect something is
wrong with the Intel Iris driver :

May 18 22:12:28 asgard kernel: [ 4906.887448] 
WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 <<
 ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1))
May 18 22:12:28 asgard kernel: [ 4906.887524] WARNING: CPU: 2 PID: 5160 at 
/build/linux-oem-osp1-JJcJwF/linux
-oem-osp1-5.0.0/drivers/gpu/drm/i915/intel_runtime_pm.c:308 
hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [
i915]
May 18 22:12:28 asgard kernel: [ 4906.887525] Modules linked in: rfcomm ccm 
cmac bnep uvcvideo btusb btrtl vi
deobuf2_vmalloc btbcm videobuf2_memops btintel videobuf2_v4l2 bluetooth 
videobuf2_common videodev ecdh_generi
c media hid_multitouch 8250_dw dell_laptop nls_iso8859_1 intel_rapl 
x86_pkg_temp_thermal intel_powerclamp cor
etemp kvm_intel arc4 snd_hda_codec_hdmi crct10dif_pclmul sof_pci_dev 
snd_sof_intel_hda_common snd_soc_hdac_hd
a snd_sof_intel_hda snd_hda_codec_realtek snd_sof_xtensa_dsp snd_sof 
crc32_pclmul snd_hda_ext_core snd_hda_co
dec_generic snd_soc_acpi_intel_match ledtrig_audio snd_soc_acpi 
ghash_clmulni_intel snd_soc_core snd_compress
 ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_nhlt snd_hda_codec 
snd_hda_core snd_hwdep snd_pcm aesni_i
ntel snd_seq_midi snd_seq_midi_event snd_rawmidi aes_x86_64 crypto_simd cryptd 
glue_helper intel_cstate intel
_rapl_perf joydev input_leds snd_seq serio_raw dell_wmi iwlmvm dell_smbios 
snd_seq_device dcdbas idma64 snd_t
imer mac80211 virt_dma dell_wmi_descriptor snd
May 18 22:12:28 asgard kernel: [ 4906.887547]  intel_wmi_thunderbolt wmi_bmof 
iwlwifi hid_sensor_als soundcor
e hid_sensor_trigger industrialio_triggered_buffer kfifo_buf 
hid_sensor_iio_common mei_me cfg80211 rtsx_pci_m
s industrialio mei memstick intel_lpss_pci intel_lpss ucsi_acpi typec_ucsi 
typec int3403_thermal int340x_ther
mal_zone intel_hid mac_hid sparse_keymap int3400_thermal acpi_pad 
acpi_thermal_rel acpi_tad sch_fq_codel parp
ort_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async
_memcpy async_pq async_xor async_tx xor mmc_block raid6_pq libcrc32c raid1 
raid0 multipath linear hid_sensor_
hub hid_generic intel_ishtp_hid i915 kvmgt vfio_mdev mdev rtsx_pci_sdmmc 
vfio_iommu_type1 vfio kvm irqbypass 
psmouse i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt nvme 
fb_sys_fops drm rtsx_pci nvme_core
 intel_ish_ipc thunderbolt intel_ishtp i2c_hid wmi hid video pinctrl_icelake 
pinctrl_intel
May 18 22:12:28 asgard kernel: [ 4906.887575] CPU: 2 PID: 5160 Comm: Xorg 
Tainted: GW 5.0.0-1
050-oem-osp1 #55-Ubuntu
May 18 22:12:28 asgard kernel: [ 4906.887576] Hardware name: Dell Inc. XPS 13 
9300/077Y9N, BIOS 1.0.7 02/26/2
020
May 18 22:12:28 asgard kernel: [ 4906.887604] RIP: 
0010:hsw_wait_for_power_well_enable.isra.8+0x4c/0x50 [i915
]
May 18 22:12:28 asgard kernel: [ 4906.887607] Code: 01 c9 8b 70 04 6a 00 d3 e2 
89 d1 e8 3e 86 04 00 85 c0 5a 
75 02 c9 c3 48 c7 c6 98 42 5f c0 48 c7 c7 55 3d 5e c0 e8 a4 1c 9d df <0f> 0b c9 
c3 0f 1f 44 00 00 55 ba 01 00
 00 00 48 89 e5 41 57 41 56
May 18 22:12:28 asgard kernel: [ 4906.887609] RSP: 0018:add0048179c0 
EFLAGS: 00010282
May 18 22:12:28 asgard kernel: [ 4906.887611] RAX:  RBX: 
9ce96e438000 RCX: 00
00
May 18 22:12:28 asgard kernel: [ 4906.887612] RDX: 006d RSI: 
a196492d RDI: 02
46
May 18 22:12:28 asgard kernel: [ 4906.887613] RBP: add0048179c0 R08: 
 R09: a19648c0
May 18 22:12:28 asgard kernel: [ 4906.887614] R10:  R11: 
0001 R12: 
May 18 22:12:28 asgard kernel: [ 4906.887618] CS:  0010 DS:  ES:  CR0: 
80050033
May 18 22:12:28 asgard kernel: [ 4906.887619] CR2: 55ea60d5b730 CR3: 
00047a4a6006 CR4: 00760ee0
May 18 22:12:28 asgard kernel: [ 4906.887620] PKRU: 5554
May 18 22:12:28 asgard kernel: [ 4906.887621] Call Trace:
May 18 22:12:28 asgard kernel: [ 4906.887650]  hsw_power_well_enable+0xaf/0x1d0 
[i915]
May 18 22:12:28 asgard kernel: [ 4906.887678]  
icl_tc_phy_aux_power_well_enable+0x7f/0x90 [i915]
May 18 22:12:28 asgard kernel: [ 4906.887704]  
intel_power_well_enable+0x3f/0x50 [i915]
May 18 22:12:28 asgard kernel: [ 4906.887730]  
__intel_display_power_get_domain+0x75/0x90 [i915]
May 18 22:12:28 asgard kernel: [ 4906.887758]  
intel_display_power_get+0x33/0x50 [i915]
May 18 22:12:28 asgard kernel: [ 4906.887798]  intel_dp_detect+0x96/0x5b0 [i915]
May 18 22:12:28 asgard kernel: [ 4906.887802]  ? ww_mutex_lock+0x64/0x70
May 18 22:12:28 asgard kernel: [ 4906.887811]  
drm_helper_probe_detect+0x50/0x90 [drm_kms_helper]
May 18 22:12:28

[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders

2020-05-18 Thread Pedro Ryan

I couldn't reproduce the bug without Ubuntu Dock.

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

Title:
  Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside
  of app icon folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  Bug: Gnome shell while opening app drawer, clicking on an app folder
  and clicking on the blank area freezes gnome shell and it makes the
  session completely unusable and non recoverable.

  How to reproduce:  1- Click 9 dots on bottom corner of dash (the app
  launcher button), wait for the app grid to show up.

  2- Click on an app folder to open it.
  3- Click on the blank area outside of the opened folder dialog.
  4- Gnome shell gets freezes and never come back from this state, on both 
wayland session and x11 session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:00:13 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1857552] Re: [81NX, Realtek ALC285, Speaker, Internal] No sound at all

2020-05-18 Thread Dirk Hahn

Hi all, 
I've freshly installed Ubuntu Mate 20.04 on LENOVO_MT_81NX_BU_idea_FM_Yoga 
S740-15IRH with the same problem. No sound no speakers. It seems the Realtek 
codec driver is not able to configure the speaker for the system.

** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+attachment/5373615/+files/bootmessages.txt

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

Title:
  [81NX, Realtek ALC285, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  In dual boot machine (lenove S740 laptop) sound is fine on windows
  side.

  Headphones work on linux side, but there is no sound at all from
  speakers on the ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hu-mka 1574 F pulseaudio
hu-mka 5552 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 25 20:14:17 2019
  InstallationDate: Installed on 2019-12-22 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1126 F pulseaudio
hu-mka 1574 F pulseaudio
hu-mka 5552 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BKCN20WW(V1.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S740-15IRH
  dmi.modalias: 
dmi:bvnLENOVO:bvrBKCN20WW(V1.02):bd07/15/2019:svnLENOVO:pn81NX:pvrLenovoYogaS740-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaS740-15IRH:
  dmi.product.family: Yoga S740-15IRH
  dmi.product.name: 81NX
  dmi.product.sku: LENOVO_MT_81NX_BU_idea_FM_Yoga S740-15IRH
  dmi.product.version: Lenovo Yoga S740-15IRH
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1876629] Re: [HDA-Intel - HDA Intel PCH, playback] No sound output/recording at all

2020-05-18 Thread etzhaim

apport information

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** Tags added: apport-collected

** Description changed:

  Updating the kernel from 4.15.0-91-generic to 4.15.0-99-generic caused
  all audio playback and recording to stop. Reverting to the old kernel
  corrects the problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   etzhaim1677 F...m pulseaudio
   /dev/snd/controlC0:  etzhaim1677 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 23:59:43 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-08 (815 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   etzhaim1677 F...m pulseaudio
   /dev/snd/controlC0:  gdm1245 F pulseaudio
etzhaim1677 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (726 days ago)
  dmi.bios.date: 05/09/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 09NT72
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd05/09/2019:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn09NT72:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.14
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  etzhaim1693 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=ecb7bced-50ae-4b4e-8a43-c89f47b1c956
+ InstallationDate: Installed on 2018-02-08 (829 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
+ MachineType: Dell Inc. Inspiron 5379
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=UUID=92811e05-3a8b-47c4-b5e8-4283e1e2ec81 ro quiet splash 
i915.enable_psr=1 i915.disable_power_well=0 acpi_rev_override=5 pci=noaer 
pcie_aspm=force nmi_watchdog=0 vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-99-generic N/A
+  linux-backports-modules-4.15.0-99-generic  N/A
+  linux-firmware 1.173.18
+ Tags:  bionic
+ Uname: Linux 4.15.0-99-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-05-08 (741 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/09/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.12.0
+ dmi.board.name: 09NT72
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd05/09/2019:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn09NT72:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 5379
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1876629/+attachment/5373599/+files/AlsaInfo.txt

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound output/recording  at
  all

Status in linux package in Ubuntu:
  New

Bug description:
  Updating the kernel from 4.15.0-91-generic to 4.15.0-99-generic caused
  all audio playback and recording to stop. Reverting to the old kernel
  corrects the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   etzhaim1677 F...m pulseaudio
   /dev/snd/controlC0:  etzhaim1677 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 23:59:43 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-08 (815 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all

[Desktop-packages] [Bug 1871377] Re: URW Nimbus font issue

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

** Changed in: fonts-urw-base35 (Ubuntu)
   Status: New => Confirmed

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

Title:
  URW Nimbus font issue

Status in fonts-urw-base35 package in Ubuntu:
  Confirmed

Bug description:
  It seems that cyrillic small letter `te` (afii10084) has wrong glyph in 
italic and bold Italic style: width is too big.
  This issue presented in OpenType and Type1 URW Nimbus Sans fonts distribution.

  I suggest to replace with the glyph of greek small `tau` letter.

  Attaching here the screenshots of some example words contain small
  letter `te` with original (wide) and replaced glyph.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1871377/+subscriptions

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

[Desktop-packages] [Bug 1164016] Re: restore type-ahead find

2020-05-18 Thread amano

Why can't you just move on? What is your stupid agenda?

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

Re: [Desktop-packages] [Bug 1878666] Re: Firefox snap is very slow (30 sec) to start

2020-05-18 Thread Tommaso

Hi,

when i run the command, i  get the following error:

~$:  snap run --trace-exec firefox
error: cannot find current revision for snap firefox: readlink
/snap/firefox/current: no such file or directory

and fifefox doesn't start.

Sorry,
Tom

Il giorno lun 18 mag 2020 alle ore 19:05 Olivier Tilloy <
olivier.til...@canonical.com> ha scritto:

> Could you please run the firefox snap from a terminal using the
> following command, and after it shows the window, close it and attach
> the corresponding output:
>
> snap run --trace-exec firefox
>
> Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1878666
>
> Title:
>   Firefox snap is very slow (30 sec) to start
>
> Status in firefox package in Ubuntu:
>   New
>
> Bug description:
>   Firefox snap is very slow, when i start it
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.36.1-5ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
>   Uname: Linux 5.4.0-29-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu May 14 19:53:08 2020
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-04-25 (18 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878666/+subscriptions
>


-- 
Tommaso Trombetta

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

Title:
  Firefox snap is very slow (30 sec) to start

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox snap is very slow, when i start it

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 19:53:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-25 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues

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

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

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

Title:
  Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip
  issues

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Hi,
   
  I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04,
  Spent some time troubleshooting with the default (previously current) drivers 
hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially 
due to missing dependencies. Errors about missing pyqt4 dependencies among 
others.

  When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found
  but fails to print.

  Just noticed similar bug filed, 690720 , and saw note that new hplip
  ver. 3.20.5 was just released and supports Ubuntu 20.04

  When trying to install new package hplip ver. 3.20.5 with the .run
  script provided by HP I am unable to complete installatoin as it
  reports unmet dependency of pyqt5 , even though package python3-pyqt5
  is installed on system.

  https://developers.hp.com/hp-linux-imaging-and-printing/gethplip

  Maybe the repo just needs to be updated with a newer build (3.20.5) to
  install on my system, or is there something that can be done in the
  meantime.

  Below hp-check -t when using the repo hplip ver. 3.20.3 ,

  ==
  Saving output in log file: /root/hp-check.log

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

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies are installed to successfully compile
  HPLIP.

 
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
has the proper dependencies installed to
  successfully run. 

 
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time dependencies).   
  

  Check types:  

 
  a. EXTERNALDEP - External Dependencies

 
  b. GENERALDEP - General Dependencies (required both at compile and run time)  

 
  c. COMPILEDEP - Compile time Dependencies 

 
  d. [All are run-time checks]  

 
  PYEXT SCANCONF QUEUES PERMISSION  

 

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10
  versions dependencies to verify and install...

  ---
  | SYSTEM INFO |
  ---

   Kernel: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 
GNU/Linux
   Host: judith-mini
   Proc: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux
   Distribution: ubuntu 20.04
   Bitness: 64 bit

  
  ---
  | HPLIP CONFIGURATION |
  ---

  HPLIP-Version: HPLIP 3.20.3
  HPLIP-Home: /usr/share/hplip
  warning:

[Desktop-packages] [Bug 1879044] Re: gnome-shell restarts due to bluetooth disconnection

2020-05-18 Thread Manuel Carro

> I've never seen that before; Xorg says WH-1000XM3 is a keyboard
device.

Crashes happen also with other two BT headsets I have.


> 1. Look in /var/crash for crash files and if found run:
> ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.

No crash file was created.


> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID
> where ID is the content of file /var/lib/whoopsie/whoopsie-id on the
> machine. Do you find any links to recent problems on that page? If
> so then please send the links to us.

Here they are:

https://errors.ubuntu.com/oops/2aad4e58-8fc4-11ea-acce-fa163e983629
https://errors.ubuntu.com/oops/316d554c-8e2b-11ea-a94b-fa163ee63de6
https://errors.ubuntu.com/oops/190b8260-8df7-11ea-a943-fa163ee63de6
https://errors.ubuntu.com/oops/3480678a-871f-11ea-a30b-fa163e6cac46
https://errors.ubuntu.com/oops/1acb977a-852d-11ea-a2df-fa163e6cac46
 

Thanks,

Manuel

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

Title:
  gnome-shell restarts due to bluetooth disconnection

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am logged in an X session with gnome.  Just after logging, I start a
  Sony Bluetooth headphones (WH-1000XM3).  After they connect (and they
  work), I switch them off (using the switch in the headphones).  < 3
  seconds after disconnections, the gnome-session crashes (and
  restarts).

  If I do this in Wayland, since the server does not seem to support
  restarts, I am logged out of the session and the laptop returns to the
  login screen.

  Best,

  Manuel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 11:23:01 2020
  DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-03-26 (416 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-05-08 (7 days ago)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET71W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  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:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  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 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/1879044/+subscriptions

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

[Desktop-packages] [Bug 1879375] [NEW] Images thumbnails doesn't update on image changes

2020-05-18 Thread Treviño

Public bug reported:

[ Impact ]

Image thumbnails are not refreshed on file changes

[ Test case ]

1. Create a new image and save it in the desktop using your image editor
2. Change the image content and save
3. The image thumbnail in the desktop should reflect the changes

[ Regression potential ]

Icons updates (and so redraws) may increase even when there are no
actual changes to perform.

** Affects: gnome-shell-extension-desktop-icons (Ubuntu)
Importance: Low
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: In Progress

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

Title:
Images thumbnails doesn't update on image changes

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
In Progress

Bug description:
[ Impact ]

Image thumbnails are not refreshed on file changes

[ Test case ]

1. Create a new image and save it in the desktop using your image editor
2. Change the image content and save
3. The image thumbnail in the desktop should reflect the changes

[ Regression potential ]

Icons updates (and so redraws) may increase even when there are no
actual changes to perform.

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

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

[Desktop-packages] [Bug 1862087] Re: High RSS useage for gnome-software background process

2020-05-18 Thread Amr Ibrahim

Confirmed, here gnome-software 3.36.0-0ubuntu3 consumes 426 MiB of
memory.

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

Title:
  High RSS useage for gnome-software background process

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I've had an uptime of slightly in excess of 2 days, and the gnome-
  software --gapplication-service process is using 700M RSS (3GiB Virt,
  ~50MB SHR).

  This seems excessive. I'll try running under heaptrack to see if
  there's any obvious slow leaks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200129.3826d9e0-1.1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200129.3826d9e0-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 10:49:40 2020
  InstallationDate: Installed on 2019-08-29 (160 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.35.2-0ubuntu1
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-20 (16 days ago)

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

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

[Desktop-packages] [Bug 1863895] Re: gnome software taking large amount of memory

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

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

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

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

Title:
  gnome software taking large amount of memory

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I just notice that gnome-software is taking at the moment 377MB of
  memory, which I consider quite excessive.

  Let me know if I can help more.

  What happened?
  gnome-software using high memory, up to 377MB

  What did I expect?
  gnome-software using at most 280MB

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Feb 19 15:00:56 2020
  InstallationDate: Installed on 2019-02-03 (380 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.35.2-0ubuntu2
   gnome-software-plugin-snap3.35.2-0ubuntu2
  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/1863895/+subscriptions

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

[Desktop-packages] [Bug 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.

2020-05-18 Thread Amr Ibrahim

I also have the trash shown on the dock, and gnome-shell is consuming
559 MB of memory.

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

Title:
  gnome-shell leaks hundreds of megabytes when the dock option 'show-
  trash' is enabled.

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  Gnome shell is the single largest resident memory user on my system.

  It was hovering at ~700mb, then with a few minutes of use of the
  system (nothing in particular, mostly shell windows, one google-chrome
  window) - spiked to ~980mb or so, before retreating to 903m.

  Even with 16gb of ram, that's a huge chunk of the system.

  I've not been able to identify anything in particular that I'm doing
  that triggers the growth.

  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1856838/comments/5, it was suggested to open a new bug,
  instead of adding to one of the several existing bugs for this.  I'm
  happy to help try and debug this, but it's not clear where to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 17:32:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-18 (532 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago)

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

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

[Desktop-packages] [Bug 1347080] Re: gnome-shell memory leak

2020-05-18 Thread Amr Ibrahim

** Project changed: ubuntu-gnome => gnome-shell (Ubuntu)

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

Title:
  gnome-shell memory leak

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell  consumes 1,6 giga memory

  
  (gnome-shell:27091): GLib-GObject-WARNING **: g_object_set_valist: object 
class 'ClutterSettings' has no property named 'window-scaling-factor'
  Gjs-Message: JS LOG: Failed to add search provider 
/usr/share/gnome-shell/search-providers/org.gnome.Weather.Application.search-provider.ini:
 TypeError: appInfo is null
  Gjs-Message: JS LOG: No permission to trigger offline updates: Polkit.Error: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action 
org.freedesktop.packagekit.trigger-offline-update is not registered
  Gjs-Message: JS LOG: GNOME Shell started at Tue Jul 22 2014 18:46:27 GMT+0100 
(BST)
  Gjs-Message: JS LOG: loading user theme: 
/usr/share//themes/Zukitwo-Shell/gnome-shell/gnome-shell.css
  [Fatal 18:46:29.401] [GLib] Source ID 6569 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6648 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6611 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6644 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6651 was not found when attempting to 
remove it
  Cairo.Surface is leaking, programmer is missing a call to Dispose
  Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
  [Fatal 18:46:29.402] [GLib] Source ID 6647 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6645 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6527 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6632 was not found when attempting to 
remove it
  [Fatal 18:46:29.404] [GLib] Source ID 6526 was not found when attempting to 
remove it
  [Fatal 18:46:29.404] [GLib] Source ID 6631 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6560 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6646 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6665 was not found when attempting to 
remove it
  Cairo.Surface is leaking, programmer is missing a call to Dispose
  Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
  [Fatal 18:46:29.405] [GLib] Source ID 6499 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6498 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6641 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6610 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6638 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6570 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6640 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6643 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6650 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6483 was not found when attempting to 
remove it
  Window manager warning: Log level 8: meta_window_raise: assertion 
'!window->override_redirect' failed
  Window manager warning: Log level 8: meta_window_raise: assertion 
'!window->override_redirect' failed
  Window manager warning: Log level 8: meta_window_lower: assertion 
'!window->override_redirect' failed

  ii  gnome-accessibility-themes  
3.12.0-1ubuntu1~trusty1 all  Accessibility 
themes for the GNOME desktop
  ii  gnome-applets   
3.5.92-0ubuntu3 amd64Various 
applets for the GNOME panel - binary files
  ii  gnome-applets-data  
3.5.92-0ubuntu3 all  Various 
applets for the GNOME panel - data files
  ii  gnome-backgrounds   
3.12.2-1~trusty1all  Set of 
backgrounds packaged with the GNOME desktop
  ii  gnome-bluetooth 
3.9.3really3.8.1-2ubuntu2   amd64GNOME 
Bluetooth tools
  ii  gnome-boxes 
3.12.3-1~trusty1amd64Simple GNOME 
app to access remote or virtual systems
  ii  gnome-calculator
1:3.12.1-0ubuntu1~trusty1   amd64

[Desktop-packages] [Bug 1347080] Re: gnome-shell memory leak

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

Title:
  gnome-shell memory leak

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell  consumes 1,6 giga memory

  
  (gnome-shell:27091): GLib-GObject-WARNING **: g_object_set_valist: object 
class 'ClutterSettings' has no property named 'window-scaling-factor'
  Gjs-Message: JS LOG: Failed to add search provider 
/usr/share/gnome-shell/search-providers/org.gnome.Weather.Application.search-provider.ini:
 TypeError: appInfo is null
  Gjs-Message: JS LOG: No permission to trigger offline updates: Polkit.Error: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action 
org.freedesktop.packagekit.trigger-offline-update is not registered
  Gjs-Message: JS LOG: GNOME Shell started at Tue Jul 22 2014 18:46:27 GMT+0100 
(BST)
  Gjs-Message: JS LOG: loading user theme: 
/usr/share//themes/Zukitwo-Shell/gnome-shell/gnome-shell.css
  [Fatal 18:46:29.401] [GLib] Source ID 6569 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6648 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6611 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6644 was not found when attempting to 
remove it
  [Fatal 18:46:29.402] [GLib] Source ID 6651 was not found when attempting to 
remove it
  Cairo.Surface is leaking, programmer is missing a call to Dispose
  Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
  [Fatal 18:46:29.402] [GLib] Source ID 6647 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6645 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6527 was not found when attempting to 
remove it
  [Fatal 18:46:29.403] [GLib] Source ID 6632 was not found when attempting to 
remove it
  [Fatal 18:46:29.404] [GLib] Source ID 6526 was not found when attempting to 
remove it
  [Fatal 18:46:29.404] [GLib] Source ID 6631 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6560 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6646 was not found when attempting to 
remove it
  [Fatal 18:46:29.405] [GLib] Source ID 6665 was not found when attempting to 
remove it
  Cairo.Surface is leaking, programmer is missing a call to Dispose
  Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces
  [Fatal 18:46:29.405] [GLib] Source ID 6499 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6498 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6641 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6610 was not found when attempting to 
remove it
  [Fatal 18:46:29.406] [GLib] Source ID 6638 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6570 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6640 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6643 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6650 was not found when attempting to 
remove it
  [Fatal 18:46:29.407] [GLib] Source ID 6483 was not found when attempting to 
remove it
  Window manager warning: Log level 8: meta_window_raise: assertion 
'!window->override_redirect' failed
  Window manager warning: Log level 8: meta_window_raise: assertion 
'!window->override_redirect' failed
  Window manager warning: Log level 8: meta_window_lower: assertion 
'!window->override_redirect' failed

  ii  gnome-accessibility-themes  
3.12.0-1ubuntu1~trusty1 all  Accessibility 
themes for the GNOME desktop
  ii  gnome-applets   
3.5.92-0ubuntu3 amd64Various 
applets for the GNOME panel - binary files
  ii  gnome-applets-data  
3.5.92-0ubuntu3 all  Various 
applets for the GNOME panel - data files
  ii  gnome-backgrounds   
3.12.2-1~trusty1all  Set of 
backgrounds packaged with the GNOME desktop
  ii  gnome-bluetooth 
3.9.3really3.8.1-2ubuntu2   amd64GNOME 
Bluetooth tools
  ii  gnome-boxes 
3.12.3-1~trusty1amd64Simple GNOME 
app to access remote or virtual systems
  ii  gnome-calculator

[Desktop-packages] [Bug 1347080] [NEW] gnome-shell memory leak