date:20200920

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

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

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

Title:
  package chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  please check the report.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 85.0.4183.83-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
  Uname: Linux 4.15.0-117-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGr+xFAQEUAQOAIhN4Cgu1l1dUjCYjUFQBAQEBAQEBAQEBAQEBAQEBEhtWYFAAFjAICjEAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2WFcwNCBWNSAKAEc=
   modes: 1366x768
  Date: Sun Sep 13 15:17:35 2020
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2016-03-05 (1653 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Load-Avg-1min: 1.11
  Load-Processes-Running-Percent:   0.1%
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550LA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=8b0d4307-6a80-4644-be46-45ed8c27015b ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  SourcePackage: chromium-browser
  Title: package chromium-browser 85.0.4183.83-0ubuntu0.18.04.2 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-09-13 (0 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.505
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1896394] Re: Prevent add to favorite and vise versa when move apps to left or right

Please:

1. Run this command to send us more information about the machine:

   apport-collect 1896394

2. Describe the problem in different words, or add a video of the issue
so we can better understand it.

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

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

Title:
  Prevent add to favorite and vise versa when move apps to left or right

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

Bug description:
  Gnome dock has serious issue, we cannot move apps to left then it get
  added to favorite and if move to right then get removed from favorite
  then as result users cannot move apps in dock as preferred.

  No one add apps to 'dock favorite' more often then already it's
  possible to perform by right click on required app icon and click 'add
  to favorite'

  Is it possible to address this issue soon, this is most likely erase
  some codes rather than implement new feature.

  KDE and Windows 10 don't have such issue.

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

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

[Desktop-packages] [Bug 1896383] Re: Text is garbled in the Network > Wired dialog

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

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 1873184, 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.


** Summary changed:

- The Text is Garbled in Detail Window
+ Text is garbled in the Network > Wired dialog

** Summary changed:

- Text is garbled in the Network > Wired dialog
+ Text is overlapping in the Network > Wired dialog

** This bug has been marked a duplicate of bug 1873184
   Wired and wireless connection details have not enough height and items 
overlap

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

Title:
  Text is overlapping in the Network > Wired dialog

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

Bug description:
  *** COSMETIC ISSUE 

  This issue occurs using the Budgie desktop on Ubuntu 20.04LTS.

  The package using during the failure was:

  gnome-control-center:
Installed: 1:3.36.4-0ubuntu1
Candidate: 1:3.36.4-0ubuntu1
Version table:
   *** 1:3.36.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  As you can see on the supplied attachment, there are references to
  "Hardware Address" and "Last Used."

  The line containing "Last Used  Today" is being displayed over the
  "Connect automatically" selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Sun Sep 20 09:07:35 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-09-20 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

2020-09-20 Thread akilan

This bug happens to me in x11, Wayland fixes the glitch.
I have i5-8250u ,intel uhd 620 graphics.I had the issue in both ubuntu and pop 
os

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

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

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  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
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  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/1872802/+subscriptions

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

[Desktop-packages] [Bug 1889252] Re: [amdgpu] app blinking

2020-09-20 Thread Abir

Ok

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

Title:
  [amdgpu] app blinking

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  automatically blinking when opening app and sometimes the app does not
  open

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

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

[Desktop-packages] [Bug 1896377] Re: My Dell wireless mouse disconnects from USB

** Summary changed:

- My Dell wireless mouse stops after a while. 
+ My Dell wireless mouse disconnects from USB

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

** Summary changed:

- My Dell wireless mouse disconnects from USB
+ My Dell wireless mouse dongle disconnects from USB

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

Title:
  My Dell wireless mouse dongle disconnects from USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Dell wireless mouse stops working after a while. Sometimes it does
  not work at all. I have to unplug dongle and put again to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 16:17:16 2020
  DistUpgraded: 2018-09-02 08:57:59,590 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f9]
  InstallationDate: Installed on 2017-02-26 (1301 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=80dcea6d-1a75-47ed-ba9d-48393d1219fa ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (749 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0XJGC1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0XJGC1:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 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/linux/+bug/1896377/+subscriptions

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

[Desktop-packages] [Bug 1896257] Re: Xorg freeze

Next time a freeze happens, please reboot and then immediately run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also tell us if you have any files in /var/crash/

** Tags added: nvidia

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

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Xorg freeze
+ Screen freeze

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

Title:
  Screen freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Another freeze will playing videogames.

  I was playing MotoGP19 via Steam Proton, and the complete operating
  system froze.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 18 18:02:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-37-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-45-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-47-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] 
[1458:3752]
  InstallationDate: Installed on 2020-04-24 (146 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: X470 AORUS GAMING 7 WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X470 AORUS GAMING 7 WIFI
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/+bug/1896257/+subscriptions

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

[Desktop-packages] [Bug 1896349] Re: PCI/internal sound card not detected

2020-09-20 Thread Hui Wang

Please test this: https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1892714/comments/46

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I can select my default audio hardware

  When I test it, doesn't work.

  When watching a Youtube video, for example, audio doesn't work as
  well.

  Thru the command lspci, this shows up:

  00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 
(rev 07)
  00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
  00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB 
Controller (rev 03)
  00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host 
Controller (rev 30)
  00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
  00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz 
Wireless Network Adapter (201NGW) (rev 30)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #0 (rev 30)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #1 (rev 30)
  00:16.0 Communication controller: Intel Corporation Management Engine 
Interface (rev 30)
  00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 30)
  00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 
(rev 30)
  00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 
(rev 30)
  00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
  00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
  00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
  00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology 
Audio Controller (rev 30)
  00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI 
Controller (rev 30)
  01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
  03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03)
  04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 19 19:24:38 2020
  InstallationDate: Installed on 2020-09-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2020
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 875C
  dmi.board.vendor: HP
  dmi.board.version: 10.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 17m-cg0xxx
  dmi.product.sku: 9XM78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1896309] Re: apport-bug xorg

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  apport-bug xorg

Status in Ubuntu:
  Incomplete

Bug description:
  $ Gtk-Message: 08:56:49.280: Failed to load module "canberra-gtk-module"
  Gtk-Message: 08:56:49.280: Failed to load module "canberra-gtk-module"
  Opening in existing browser session

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 19 08:54:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0502]
  InstallationDate: Installed on 2020-09-15 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron N4050
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 02JCHC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/+bug/1896309/+subscriptions

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

[Desktop-packages] [Bug 1896385] Re: Xorg freeze

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

** This bug has been marked a duplicate of bug 1896257
   Xorg freeze

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When I was playing Desperado III in Steam, the game closed and I went
  back to desktop.

  I typed this command to try to help you. I think that the problem is
  Geoclue, that finish the process and next restart the process but I
  don't know.

  I haven't got any GPS localization system in my PC.

  pitx@Pitx-PC:~$ journalctl -e
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 
processe>
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of 
p>
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded.
  sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. 
Shutti>
  sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded.
  sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processe>
  sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by 
gnome-sh>
  sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] 
Activati>
  sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice.
  sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice 
apps-org.gnome.Terminal.sl>
  sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server...
  sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] 
Successf>
  sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server.
  sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 
launched>
  sep 20 16:13:49 Pitx-PC systemd[1704]: 
gnome-launched-org.gnome.Terminal.deskto>
  lines 986-1008/1008 (END)
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 
processes of 2 users.
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of 
process 13161 owned by '1000' RT at priority 10.
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded.
  sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. 
Shutting down..
  sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded.
  sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
  sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by 
gnome-shell.
  sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.1031' (uid=1000 pid=13505>
  sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice.
  sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice 
apps-org.gnome.Terminal.slice.
  sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server...
  sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] 
Successfully activated service 'org.gnome.Terminal'
  sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server.
  sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 
launched by gnome-terminal-server process 13508.
  sep 20 16:13:49 Pitx-PC systemd[1704]: 
gnome-launched-org.gnome.Terminal.desktop-13502.scope: Succeeded.
  ~

  ~
  ~
  ~
  ~
  lines 986-1008/1008 (END)
  sep 20 16:12:38 Pitx-PC

[Desktop-packages] [Bug 1896330] Re: gnome-shell crashed with SIGSEGV in _gdk_x11_screen_process_owner_change() from gdk_x11_display_translate_event() from _gdk_x11_event_translator_translate() from _

** Summary changed:

- 
/usr/bin/gnome-shell:11:_gdk_x11_screen_process_owner_change:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:_gdk_x11_display_queue_events:gdk_display_get_event
+ gnome-shell crashed with SIGSEGV in _gdk_x11_screen_process_owner_change() 
from gdk_x11_display_translate_event() from 
_gdk_x11_event_translator_translate() from _gdk_x11_display_queue_events() from 
gdk_display_get_event()

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

Title:
  gnome-shell crashed with SIGSEGV in
  _gdk_x11_screen_process_owner_change() from
  gdk_x11_display_translate_event() from
  _gdk_x11_event_translator_translate() from
  _gdk_x11_display_queue_events() from gdk_display_get_event()

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1896102] Re: gnome-shell crashes together with emacs-gtk regularly

Thanks. I can't see that bug, probably because it is private. Please
check that bug 1896273 does not contain any information you don't wish
to share with the wider world, and when ready, change it to Public (top
right corner of the page).

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

Title:
  gnome-shell crashes together with emacs-gtk regularly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Regularly emacs-gtk crashes (reported separately in LP: #1896100) and
  with it gnome-shell crashes as well. Since those two crashes happen at
  the same time I am assuming that those two events are related. I don't
  know what the causal relation is though.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.37.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
  Uname: Linux 5.8.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 12:54:15 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-17 (153 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

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

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

[Desktop-packages] [Bug 1896333] Re: [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack.

** Summary changed:

- "Select an audio" menu when user have not even inserted headphone jack.
+ [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted
headphone jack.

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

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

Title:
[Dell Inspiron 5548] "Select an audio" menu when user have not even
inserted headphone jack.

Status in pulseaudio package in Ubuntu:
Incomplete

Bug description:
GNOME 3.36.3 | Ubuntu 20.04.1

It has been a month and I have been experiencing this weird behavior.

Earphone option like this 3 while unlocking the laptop as if I
have inserted earphones.

Some details this issue:
I have to wait like 10 min or so after the lock of the screen. This will
trigger something and when I open the lid or touch mouse pad to unlock, I get
earphone options to chooose in the screen as if I have inserted headphone jack.

Something is wrong. I want to know why. This didn't used to happen a
month ago. I waited a month to report this issue thinking it will get
resolved in upcoming updates but sadly no changes so far. I think some
Ubuntu's GNOME update might have something to do this. This is my wild
guess. But very certain about it. Let me know.

Although the issue might seems really small issue but very annoying to
go throw this EVERYDAY.

I would love to know what is causing this? When its fixed? Is there
something wrong on my side?

Note: This happens ONLY when I try to unlock the screen after like >10
min or so.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.6
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: pranav 3554 F pulseaudio
/dev/snd/controlC0: pranav 3554 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 19 20:54:36 2020
InstallationDate: Installed on 2020-02-16 (216 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago)
dmi.bios.date: 05/28/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0FFJC4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias:
dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Inspiron 5548
dmi.product.sku: 0641
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1896333] Re: "Select an audio" menu when user have not even inserted headphone jack.

2020-09-20 Thread Hui Wang

Yes, it could record the jack status.

And you could also run sudo evtest-->choose headphone event in a
terminal, let evtest monitor the jack status.

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

Title:
[Dell Inspiron 5548] "Select an audio" menu when user have not even
inserted headphone jack.

Status in pulseaudio package in Ubuntu:
Incomplete

Bug description:
GNOME 3.36.3 | Ubuntu 20.04.1

It has been a month and I have been experiencing this weird behavior.

Earphone option like this 3 while unlocking the laptop as if I
have inserted earphones.

Although the issue might seems really small issue but very annoying to
go throw this EVERYDAY.

I would love to know what is causing this? When its fixed? Is there
something wrong on my side?

Note: This happens ONLY when I try to unlock the screen after like >10
min or so.

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

[Desktop-packages] [Bug 1893969] Re: Screen corruption and delayed update using onboard Intel video

Thanks for the screenshot. It's hard to tell if that's a bug in the
application, the toolkit, Xorg or the compositor.

Please continue collecting more screenshots of the problem. Please also
try a different desktop environment that's not GNOME. If your xrandr
command triggers the same problem without GNOME then we don't need to
involve the 'mutter' package in this bug.

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

Title:
  Screen corruption and delayed update using onboard Intel video

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

Bug description:
  I frequently get screen corruption or delayed screen updates using
  onboard Intel video (i7-10710U in a Dell XPS 13 7390).  I am attaching
  a screen shot of an example of this in Emacs, where you can see echoes
  of past cursor locations (center right side of screen, the highlighted
  word "boolean").

  A frequent failure is that an application updates its window, but the
  updates do not appear on screen until I take some action to disturb
  the window (move or resize it, change focus, change desktops, etc.),
  after which it cleans itself up.  Small changes (such as selecting
  text) will often clean up the image where the change is made without
  repainting the entire window.

  My display panel is 4K UHD+, and I have attached two external Full HD
  DisplayPort monitors using chaining with 2x2 scale using XrandR.  This
  corruption appears to happen on all three surfaces.  The configuration
  for my desktop is:

  HIX=3840
  HIY=2160
  HI=${HIX}x${HIY}
  xrandr --fb $(($HIX * 3))x$HIY \
 --output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
 --output DP-2-8 --auto --panning ${HI}+$HIX+0 \
 --scale-from $HI --left-of eDP-1 --scale 2x2 \
 --output DP-2-1 --auto --panning $HI+0+0 \
 --scale-from $HI --left-of DP-2-8 --scale 2x2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Sep  2 11:48:03 2020
  DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-21 (72 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)

2020-09-20 Thread Yuan-Chen Cheng

I heard that in the new design, we can't see nvidia pci device in lspci
as we are in power saving mode (say `prime-select intel`)

if that's the case, what's the proper too to list all pci device on the
machine?

** Tags added: oem-priority

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

Title:
  FFE: support for NVIDIA runtimepm (hybrid gfx)

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New
Status in nvidia-prime package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  The work that went into ubuntu-drivers-common and nvidia-prime is
  meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid
  systems, introduced by the NVIDIA 450 driver series.

  This allows the supported systems to make use of the integrated GPU
  (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until
  needed. While powered down, the NVIDIA GPU can still detect any
  events, should external displays be plugged in.

  This brings hybrid graphics on Linux on par with Windows.

  Only the supported GPUs will be able to benefit from this change. This
  is why NVIDIA provides a hardware database (included in the nvidia
  packages), which gpu-manager can now parse. The ubuntu-drivers tool
  relies on that detection to enable this new feature when installing
  the NVIDIA driver.

  Another improvement is the ability of ubuntu-drivers to detect LTSB
  (Long term support branch), NFB (New feature branch), Legacy, Beta
  flags, which the NVIDIA drivers can have, and make informed detection
  choices.

  
  This work also includes a number of bug fixes reported on errors.ubuntu.com.

  Requirements:

  The new ubuntu-drivers-common:

  
  The new nvidia-prime:

  
  Changes to the NVIDIA drivers:

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

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

[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected

^^^
That's bug 1871641

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

Title:
  booting with splash hangs when external monitors are connected

Status in Plymouth:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  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:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  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/plymouth/+bug/1872159/+subscriptions

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

[Desktop-packages] [Bug 1726224] Re: wacom invisible mouse pointer in wayland

That's a little bit obscure. If it takes chrome-remote-desktop to
trigger problems then perhaps open a new bug for that, by running:

  ubuntu-bug gnome-shell

Unless other people find this bug is still occurring for them with basic
gnome-shell in 20.04...

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

Title:
  wacom invisible mouse pointer in wayland

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.10, I connected my Wacom Intuos tablet,
  which has touch and pen functionality.

  Controlling the mouse pointer through the touch functionality seems to
  work fine, but using the stylus produced very strange behaviour,
  depending the program.

  - With Firefox there there are two pointers - one that is moving in
  accordance with the stylus movements, and one stays put at the
  position, when the stylus movement was detected.

  - With Darktable the mouse pointer becomes invisible, once it's moved
  inside of the application window (it registers clicks though). Once
  the pointer is moved outside of the application window, it appears
  again.

  I'm running Ubuntu inside of a wayland session.

  libwacom2: 0.24-1

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

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

[Desktop-packages] [Bug 1569068] Re: mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: assertion failed: (!e->dead)

The most recent crashes were in 19.04 so consider it fixed.

** Changed in: mate-settings-daemon (Ubuntu)
   Status: Incomplete => Fix Released

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

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

Title:
  mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407:
  glib_defer_free: assertion failed: (!e->dead)

Status in mate-settings-daemon package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-settings-daemon.  This problem was most recently seen
  with version 1.12.1-2build1, the problem page at
  https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7
  contains more details.

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

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

[Desktop-packages] [Bug 1896402] Re: comp starts with error

Please explain what kind of problem you are experiencing.

If it's just an error message then please run:

  sudo rm /var/crash/*

and reboot.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  comp starts with error

Status in Ubuntu:
  Incomplete

Bug description:
  Computer after start up has to sent an error message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
  Uname: Linux 4.15.0-117-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: i386
  CompositorRunning: None
  Date: Sun Sep 20 16:22:14 2020
  DistUpgraded: 2019-10-24 14:09:39,726 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Foxconn International, Inc. 82G33/G31 Express Integrated 
Graphics Controller [105b:0df7]
  InstallationDate: Installed on 2019-09-13 (373 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 
(20190304.5)
  MachineType: OEM OEM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=b408071f-56d9-440d-bdc4-aa1d2ae658b4 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-10-24 (332 days ago)
  dmi.bios.date: 07/07/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: G31MX Series
  dmi.board.vendor: Foxconn
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: OEM
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Jan  3 14:44:05 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

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

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

[Desktop-packages] [Bug 1890992] Re: package libnvidia-compute-440-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in p

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

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

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

Title:
  package libnvidia-compute-440-server (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so', which is also in package nvidia-340
  340.108-0ubuntu2

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Confirmed

Bug description:
  Not able to install cuda libraries for nvidia geforce 820m gpu

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-compute-440-server (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug  7 21:45:45 2020
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu2
  InstallationDate: Installed on 2020-08-06 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-440-server
  Title: package libnvidia-compute-440-server (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1890992/+subscriptions

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

[Desktop-packages] [Bug 1890992] Re: package libnvidia-compute-440-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in p

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

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

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

Title:
  package libnvidia-compute-440-server (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so', which is also in package nvidia-340
  340.108-0ubuntu2

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
  Confirmed

Bug description:
  Not able to install cuda libraries for nvidia geforce 820m gpu

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-compute-440-server (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug  7 21:45:45 2020
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu2
  InstallationDate: Installed on 2020-08-06 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-440-server
  Title: package libnvidia-compute-440-server (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1890992/+subscriptions

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

[Desktop-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards

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

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

Title:
  [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

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

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/gnome-shell/+bug/1895486/+subscriptions

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

[Desktop-packages] [Bug 1896375] Re: 25% cpu always for gnome-shell

While the problem is happening, please run:

  journalctl -f

and tell us what messages, if any, keep scrolling past.

Please also run these commands:

  xrandr --verbose > xrandr.txt
  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt
  ls ~/.local/share/gnome-shell/extensions/ > localext.txt

and attach the resulting text files here.

Finally, please try closing all your apps except Terminal running 'top'
and tell us if that solves the problem.


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

Title:
  25% cpu always for gnome-shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Tasks: 308 total,   1 running, 307 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  9.5 us,  3.6 sy,  0.0 ni, 86.3 id,  0.5 wa,  0.0 hi,  0.1 si,  0.0 
st
  MiB Mem :   3841.7 total,159.0 free,   1895.3 used,   1787.4 buff/cache
  MiB Swap:   7628.0 total,   7603.7 free, 24.2 used.   1624.8 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND
 2423 akhil 20   0 4310384 312188 115812 S  24.8   7.9  33:36.18 
gnome-shell
 2153 root  20   0  238576  82840  50104 S  12.6   2.1  10:59.90 Xorg   

 4193 akhil 20   0  938912 119056  82000 S   9.9   3.0  10:03.15 
gnome-control-c
 5308 akhil 20   0  977816  54544  40272 S   3.3   1.4   0:17.72 
gnome-terminal-
 1337 root -51   0   0  0  0 S   2.6   0.0   3:44.30 
irq/40-nvidia  
1 root  20   0  168984  12960   8392 S   0.3   0.3   0:12.09 
systemd
  210 root  20   0   0  0  0 S   0.3   0.0   0:01.63 
usb-storage
  952 root  20   0  418364  20028  16836 S   0.3   0.5   0:09.29 
NetworkManager

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 16:07:16 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-08-09 (41 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  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/1896375/+subscriptions

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

[Desktop-packages] [Bug 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper

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

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

Title:
  [memory leak] Gnome-Shell don't free ram when changing the wallpaper

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Sorry for my bad english, here is the link to see the error by
  yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be

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

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

[Desktop-packages] [Bug 1896110] Re: Ubuntu Dock has no icons when logged in with USB storage plugged in

2020-09-20 Thread Craig

This is issues is reproducible.

Update

If I open a terminal screen (CTRL + ALT + T) and then go full screen
(F11) for at least 5 seconds then go back to default size (F11) then the
Ubuntu Dock is redrawn and is shown as expected.

USB storage is 4 GB FAT formatted

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

Title:
  Ubuntu Dock has no icons when logged in with USB storage plugged in

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

Bug description:
  If I connect a USB key to the computer then login the Favorites side
  bar is empty and the Application launcher does not work.

  The mouse and keyboard still work

  Removing the USB key does not resolve the issue

  Removing the USB key and then logging out and back in again resolves
  the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 18 07:32:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.100, 5.4.0-45-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-47-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140]
   NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 
730] [1462:3380]
  InstallationDate: Installed on 2020-05-28 (111 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 10TXCTO1WW
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M22KT42A
  dmi.board.name: 3140
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN 3258133898759
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM22KT42A:bd12/23/2019:svnLENOVO:pn10TXCTO1WW:pvrV530S-07ICB:rvnLENOVO:rn3140:rvrSDK0J40700WIN3258133898759:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: V530S-07ICB
  dmi.product.name: 10TXCTO1WW
  dmi.product.sku: LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB
  dmi.product.version: V530S-07ICB
  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.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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-extension-ubuntu-dock/+bug/1896110/+subscriptions

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

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

2020-09-20 Thread Ivan Gašparović

Legion 5 laptop with AMD - best I could do is add "blacklist
hid_multitouch" to /etc/modprobe.d/blacklist.conf , it got the mouse to
move but stutters a lot.

[0.004610] ACPI: SSDT 0xCDFF4000 007216 (v02 LENOVO CB-01
0001 MSFT 0400)
[2.467514] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy 
regulator
[2.467526] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy 
regulator
[2.632628] input: MSFT0001:00 06CB:7F28 Mouse as 
/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input6
[2.632754] input: MSFT0001:00 06CB:7F28 Touchpad as 
/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input7
[2.632894] hid-generic 0018:06CB:7F28.0001: input,hidraw0: I2C HID v1.00 
Mouse [MSFT0001:00 06CB:7F28] on i2c-MSFT0001:00

I: Bus=0018 Vendor=06cb Product=7f28 Version=0100
N: Name="MSFT0001:00 06CB:7F28 Mouse"
P: Phys=i2c-MSFT0001:00
S: 
Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input6
U: Uniq=
H: Handlers=mouse0 event6 
B: PROP=0
B: EV=17
B: KEY=3 0 0 0 0
B: REL=3
B: MSC=10

I: Bus=0018 Vendor=06cb Product=7f28 Version=0100
N: Name="MSFT0001:00 06CB:7F28 Touchpad"
P: Phys=i2c-MSFT0001:00
S: 
Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0001/input/input7
U: Uniq=
H: Handlers=mouse1 event7 
B: PROP=0
B: EV=1b
B: KEY=400 1 0 0 0 0
B: ABS=103
B: MSC=10

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)

[Desktop-packages] [Bug 1896402] Re: comp starts with error

2020-09-20 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/1896402

Title:
  comp starts with error

Status in xorg package in Ubuntu:
  New

Bug description:
  Computer after start up has to sent an error message.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
  Uname: Linux 4.15.0-117-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: i386
  CompositorRunning: None
  Date: Sun Sep 20 16:22:14 2020
  DistUpgraded: 2019-10-24 14:09:39,726 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Foxconn International, Inc. 82G33/G31 Express Integrated 
Graphics Controller [105b:0df7]
  InstallationDate: Installed on 2019-09-13 (373 days ago)
  InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 
(20190304.5)
  MachineType: OEM OEM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=b408071f-56d9-440d-bdc4-aa1d2ae658b4 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-10-24 (332 days ago)
  dmi.bios.date: 07/07/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: G31MX Series
  dmi.board.vendor: Foxconn
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: OEM
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Jan  3 14:44:05 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

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

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

[Desktop-packages] [Bug 1896402] [NEW] comp starts with error

You have been subscribed to a public bug:

Computer after start up has to sent an error message.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: i386
CompositorRunning: None
Date: Sun Sep 20 16:22:14 2020
DistUpgraded: 2019-10-24 14:09:39,726 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: Foxconn International, Inc. 82G33/G31 Express Integrated Graphics 
Controller [105b:0df7]
InstallationDate: Installed on 2019-09-13 (373 days ago)
InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5)
MachineType: OEM OEM
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=b408071f-56d9-440d-bdc4-aa1d2ae658b4 ro quiet splash
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-10-24 (332 days ago)
dmi.bios.date: 07/07/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: G31MX Series
dmi.board.vendor: Foxconn
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM:
dmi.product.name: OEM
dmi.product.version: OEM
dmi.sys.vendor: OEM
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Jan  3 14:44:05 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.3

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


** Tags: apport-bug bionic i386 ubuntu
-- 
comp starts with error
https://bugs.launchpad.net/bugs/1896402
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

Re: [Desktop-packages] [Question #692926]: Webkitgtk stable release 2.30 update in ubuntu

2020-09-20 Thread Manfred Hampl

Question #692926 on webkit2gtk in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/webkit2gtk/+question/692926

Status: Open => Needs information

Manfred Hampl requested more information:
Why do you need that version of webkitgtk in focal?
What is the benefit of updating it in focal?

-- 
You received this question notification because your team Desktop
Packages is subscribed to the question.

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

[Desktop-packages] [Bug 1896397] Re: [UIFe] Tweak Arabic font

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

** Changed in: language-selector (Ubuntu)
   Status: New => Confirmed

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

Title:
  [UIFe] Tweak Arabic font

Status in language-selector package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up of bug #1891733. After the new default font for
  Arabic had made it to focal, we got some additional feedback at
  . There seems to be a consensus
  to make these adjustments:

  * Replace "Noto Sans Arabic UI" with "Noto Naskh Arabic UI" as
default Arabic font for sans-serif

  * Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1896397/+subscriptions

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

[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected

2020-09-20 Thread Daniel

I am seeing this issue and neither of the proposed fixes to
/etc/default/grub or /etc/gdm3/custom.conf work. I have only one monitor
plugged in to the integrated graphic port of a Dell Precision 3630.
Pressing esc while frozen shows that “A start job is running for Hold
until boot process finishes up (Xmin Xs / no limit)

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

Title:
  booting with splash hangs when external monitors are connected

Status in Plymouth:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  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:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  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/plymouth/+bug/1872159/+subscriptions

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

[Desktop-packages] [Bug 1896397] Re: [UIFe] Tweak Arabic font

2020-09-20 Thread Gunnar Hjalmarsson

The documentation and translation teams have been notified:

https://lists.ubuntu.com/archives/ubuntu-doc/2020-September/020760.html

https://lists.ubuntu.com/archives/ubuntu-
translators/2020-September/007696.html

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

Title:
  [UIFe] Tweak Arabic font

Status in language-selector package in Ubuntu:
  New

Bug description:
  This is a follow-up of bug #1891733. After the new default font for
  Arabic had made it to focal, we got some additional feedback at
  . There seems to be a consensus
  to make these adjustments:

  * Replace "Noto Sans Arabic UI" with "Noto Naskh Arabic UI" as
default Arabic font for sans-serif

  * Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1896397/+subscriptions

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

[Desktop-packages] [Bug 1896397] [NEW] [UIFe] Tweak Arabic font

2020-09-20 Thread Gunnar Hjalmarsson

Public bug reported:

This is a follow-up of bug #1891733. After the new default font for
Arabic had made it to focal, we got some additional feedback at
. There seems to be a consensus to
make these adjustments:

* Replace "Noto Sans Arabic UI" with "Noto Naskh Arabic UI" as
  default Arabic font for sans-serif

* Drop the specification for monospace, and with that fall back
  to DejaVu for Arabic monospace

** Affects: language-selector (Ubuntu)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: New

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

Title:
  [UIFe] Tweak Arabic font

Status in language-selector package in Ubuntu:
  New

Bug description:
  This is a follow-up of bug #1891733. After the new default font for
  Arabic had made it to focal, we got some additional feedback at
  . There seems to be a consensus
  to make these adjustments:

  * Replace "Noto Sans Arabic UI" with "Noto Naskh Arabic UI" as
default Arabic font for sans-serif

  * Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1896397/+subscriptions

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

[Desktop-packages] [Bug 1896394] [NEW] Prevent add to favorite and vise versa when move apps to left or right

2020-09-20 Thread hatsune

Public bug reported:

Gnome dock has serious issue, we cannot move apps to left then it get
added to favorite and if move to right then get removed from favorite
then as result users cannot move apps in dock as preferred.

No one add apps to 'dock favorite' more often then already it's possible
to perform by right click on required app icon and click 'add to
favorite'

Is it possible to address this issue soon, this is most likely erase
some codes rather than implement new feature.

KDE and Windows 10 don't have such issue.

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

** Summary changed:

- Prevent add to favorite and vise verse when move apps to left or right
+ Prevent add to favorite and visa verse when move apps to left or right

** Summary changed:

- Prevent add to favorite and visa verse when move apps to left or right
+ Prevent add to favorite and vise versa when move apps to left or right

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

Title:
  Prevent add to favorite and vise versa when move apps to left or right

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

Bug description:
  Gnome dock has serious issue, we cannot move apps to left then it get
  added to favorite and if move to right then get removed from favorite
  then as result users cannot move apps in dock as preferred.

  No one add apps to 'dock favorite' more often then already it's
  possible to perform by right click on required app icon and click 'add
  to favorite'

  Is it possible to address this issue soon, this is most likely erase
  some codes rather than implement new feature.

  KDE and Windows 10 don't have such issue.

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

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

[Desktop-packages] [Bug 1896393] [NEW] gedit not responding to keystrokes

2020-09-20 Thread Cliff Carson

Public bug reported:

Don't know how to further document this except was is observed during
the gedit session.

While typing information into the gedit window the keystrokes get
delayed 1-2 seconds from the time the keys are struct and when the
character(s) show up on the screen.  It's as if the system was too busy
to service the key input but that doesn't appear to be the case.  This
problem doesn't occur on the current gedit running under 20.04.

Any suggestions on how to document this problem?

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gedit 3.36.2-1
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 20 13:03:43 2020
InstallationDate: Installed on 2020-08-28 (22 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  gedit not responding to keystrokes

Status in gedit package in Ubuntu:
  New

Bug description:
  Don't know how to further document this except was is observed during
  the gedit session.

  While typing information into the gedit window the keystrokes get
  delayed 1-2 seconds from the time the keys are struct and when the
  character(s) show up on the screen.  It's as if the system was too
  busy to service the key input but that doesn't appear to be the case.
  This problem doesn't occur on the current gedit running under 20.04.

  Any suggestions on how to document this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gedit 3.36.2-1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 13:03:43 2020
  InstallationDate: Installed on 2020-08-28 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1896393/+subscriptions

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

[Desktop-packages] [Bug 1723835] Re: Dock - Clicking icon doesn't minimize

2020-09-20 Thread hatsune

See the opensource project: https://github.com/jderose9/dash-to-panel
It works as expected (also same as windows 10)

If developers need better understand then easy to install above and test
it.

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

Title:
  Dock - Clicking icon doesn't minimize

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

Bug description:
  I have open Firefox, it is maximized. Clicking on it's icon in the
  Dock does nothing, I expect it would minimize Firefox. Unity, KDE and
  Windows behave in this manor.

  Window doesn't have to be maximized to show this behavior, clicking
  the icon in the Dock will bring up a selection popup if there are
  multiple instances of that application open, but if there is only one
  it does nothing.

  Tested with Gnome Terminal, Firefox, Chromium, Files, VLC, Terminator,
  all behave the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 19:54:00 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-29 (717 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear

2020-09-20 Thread Evys Ancede Gallardo

In a fresh installation of Ubuntu 20.04 this bug affect all my PCs(3).

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

Title:
  Some desktop icons disappear

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

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

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

[Desktop-packages] [Bug 1896389] [NEW] Problem with Nautilus and Port 22 when a different port is configured

2020-09-20 Thread Volker Wysk

Public bug reported:

I've configured my ssh client(s) to use a port different from 22, in
order to avoid the large number of break-in attempts on the standard
port 22. That's the "Port" setting in /etc/ssh/ssh_config. I've also
configured my ssh servers (different machines) to use that port. That's
also "Port", in /etc/ssh/sshd_config. This works fine.

But now I'm trying to use nautilus to connect via sftp to my website,
using the address:

sftp://username@provider:22/path/to/www/data

The port 22, which is to be used, is provided. The configured new
default port is overridden by it. This works for the sftp command:

sftp sftp://username@provider:22/path/to/www/data

But it doesn't work with nautilus. I get this message (translated back
from German to English):

"The server has refused the connection. This usually is because of a
firewall denies access or the remote service isn't running."

But when I change the default port in /etc/ssh/ssh_config back to 22, it
works!

It looks like nautilus fails to regard the port, which is provided in
the URL (see above).


Ubuntu version: 20.04.1 LTS
Nautilus version: 1:3.36.3-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 20 17:52:29 2020
InstallationDate: Installed on 2020-08-03 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  Problem with Nautilus and Port 22 when a different port is configured

Status in nautilus package in Ubuntu:
  New

Bug description:
  I've configured my ssh client(s) to use a port different from 22, in
  order to avoid the large number of break-in attempts on the standard
  port 22. That's the "Port" setting in /etc/ssh/ssh_config. I've also
  configured my ssh servers (different machines) to use that port.
  That's also "Port", in /etc/ssh/sshd_config. This works fine.

  But now I'm trying to use nautilus to connect via sftp to my website,
  using the address:

  sftp://username@provider:22/path/to/www/data

  The port 22, which is to be used, is provided. The configured new
  default port is overridden by it. This works for the sftp command:

  sftp sftp://username@provider:22/path/to/www/data

  But it doesn't work with nautilus. I get this message (translated back
  from German to English):

  "The server has refused the connection. This usually is because of a
  firewall denies access or the remote service isn't running."

  But when I change the default port in /etc/ssh/ssh_config back to 22,
  it works!

  It looks like nautilus fails to regard the port, which is provided in
  the URL (see above).

  
  Ubuntu version: 20.04.1 LTS
  Nautilus version: 1:3.36.3-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 17:52:29 2020
  InstallationDate: Installed on 2020-08-03 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  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/1896389/+subscriptions

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

[Desktop-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome

Bug tracking in:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821

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

** Summary changed:

- [media-keys] Fn media keys with lag slow/delay on Gnome
+ [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll_Lock" 
keyboards

** Summary changed:

- [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll_Lock" 
keyboards
+ [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" 
keyboards

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

Title:
  [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-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.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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:

[Desktop-packages] [Bug 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper

** Summary changed:

- Gnome-Shell don't free ram when I change a wallpaper
+ [memory leak] Gnome-Shell don't free ram when changing the wallpaper

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

Title:
  [memory leak] Gnome-Shell don't free ram when changing the wallpaper

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

Bug description:
  Sorry for my bad english, here is the link to see the error by
  yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be

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

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

[Desktop-packages] [Bug 1856838] Re: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview

** Summary changed:

- gnome-shell using a lot of RAM after repeatedly opening the overview
+ [memory leak] gnome-shell using a lot of RAM after repeatedly opening the 
overview

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

Title:
  [memory leak] gnome-shell using a lot of RAM after repeatedly opening
  the overview

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Just noticed my gnome-shell was using 3GB RSS. Which seems excessive.
  Spoke to duflu on irc and he suggested I file a bug, and to make sure
  I'm not using any extra extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 10:49:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (681 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago)

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

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

[Desktop-packages] [Bug 1835220] Re: Please support /usr/lib64/sane

2020-09-20 Thread Gunnar Hjalmarsson

sane-backends 1.0.31-1~experimental1 has now migrated to groovy-release.

** Changed in: sane-backends (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  Please support /usr/lib64/sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Bionic:
  Fix Committed
Status in sane-backends source package in Focal:
  Fix Committed
Status in sane-backends source package in Groovy:
  Fix Released
Status in sane-backends package in Baltix:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  [Impact]

  The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
  recognized as a directory for SANE backends. However, some .deb files
  with scanner drivers, typically provided by Brother, install files in
  /usr/lib64/sane.

  This issue has been discussed in bug #1728012, but was broken out from
  there to not block another more important change in bionic.

  sane-backends 1.0.31-1~experimental1 adds support for /usr/lib64/sane,
  and so do the debdiffs attached to this bug report for focal and
  bionic.

  [Test case]

  * Configure an affected scanner with drivers installed via
e.g. brscan2

  * Try to scan with simple-scan

  -> Find that the scanner is not found

  * Install libsane{,1}, libsane-common and sane-utils from
{focal,bionic}-proposed

  * Try to scan again

  -> Scanner found and scanning works

  [Regression risk]

  This only adds a directory to the lib search path via an existing
  patch, so the regression risk should be minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835220/+subscriptions

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

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

I use Ubuntu 20.04.1 (focal), and I have the same problem. I confirm
this bug.

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  New
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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

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

I use Ubuntu 20.04.1, and I have the same problem. I confirm this bug.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 794598] Re: Keyboard Shortcut to Zoom (Ctrl ++) doesn't work until after menu Zoom

2020-09-20 Thread Bug Watch Updater

Launchpad has imported 52 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=526288.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-11-03T19:31:51+00:00 Pjf-y wrote:

User-Agent:   Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) 
Gecko/20091027 Fedora/3.5.4-1.fc11 Firefox/3.5.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) 
Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4 
ThunderBrowse/3.2.6.5

After starting Thunderbird, using the Ctrl-+/- keyboard short cut does
not have any effect on the font size for the message body unless the
menu item (View -> Zoom -> Zoom in/out) is used first to magnify or
decrease the font size. After that, the keyboard short cuts function as
expected.

Reproducible: Always

Steps to Reproduce:
1. Start Thunderbird
2. Try to zoom the message body using Ctrl-+/- (should not work)
3. Use the menu item: View -> Zoom -> Zoom in/out to change the font size for 
the message body
4. The keyboard short cuts will now function as they should

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/0


On 2009-11-04T08:58:35+00:00 7-ludovic wrote:

Anything in Tools -> Error console ?

This WFM on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
rv:1.9.1.6pre) Gecko/20091103 Shredder/3.0pre

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/1


On 2009-11-04T17:32:47+00:00 Pjf-y wrote:

I have to apologize for not doing my homework first. Thunderbird only
shows this behavior when the lightning add-on is enabled, otherwise the
keyboard short cuts work as advertised. I'm running Lightning pre 1 on
Fedora 11. I could not test with a more recent lightning as it does not
appear to work.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/2


On 2009-11-05T15:14:01+00:00 Standard8 wrote:

I see this, but only if you've opened the calendar tab first.

Opening the View -> Zoom sub-menu is enough to clear the error.

This seems to be a result of the way lightning is overlaying the menus -
cmd_fullZoom* is now tab-implementation based so maybe it needs to be
updated to the new way of doing things. This is the bit I suspect is
getting in the way:

http://hg.mozilla.org/releases/comm-1.9.1/annotate/7fee9d989390/calendar/base/content
/calendar-common-sets.js#l263

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/3


On 2009-11-05T18:56:58+00:00 Philipp-bugzilla wrote:

Yeah, we never really adapted our command controller to be fully tab
specific. It would be nice to fix this for the beta. Not sure if we
should block on it though. There are a few other bugs open with similar
issues (i.e commands firing in both calendar tab and tasks tab, or
calendar and mail tab, etc.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/4


On 2009-11-05T20:56:59+00:00 Philipp-bugzilla wrote:

I have the feeling this may be a Thunderbird bug in the command
controller code. I've locally changed things so that the command
controller is no longer injected into the document and only provided via
the tab API, but still the zoom commands are disabled on startup as soon
as the calendar controller *supports* the command.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/5


On 2009-11-05T21:37:39+00:00 Standard8 wrote:

So the calendar code may still be a problem (depending on how it manages
its controllers at the moment), but you're right, Thunderbird is wrong -
it isn't updating the view menu when we switch tabs, it only does that
in view_init() which is when the view menu is opened... I think there's
something we do for tabs around somewhere.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/6


On 2009-12-02T12:48:46+00:00 Ssitter wrote:

Bug 521026 mentions a similar issue with Thunderbird (with and without 
Lightning). The F8 key only works after opening the View menu once. 
Maybe the root cause of this bug and Bug 521026 is the same.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/794598/comments/7

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-20 Thread Treviño

@ Cristiano Nunes,

Interesting, not sure how this is related... I will try to reproduce
that, although it seems unrelated to the fix, and probably something
upstream too.

Feel free to open another bug though (if you can using ubuntu-bug with
the crash file and debug symbols).

In any case we can handle it as regression in bug #1896332

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-20 Thread Treviño

@ Marco Giannini,

for 20.10 the fix was ready even before, I didn't advertise it as it's
in a PPA with some more stuff as per the pipewire3 transition (build-
only for now).

But you can grab it at https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4265.1/

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

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

2020-09-20 Thread Víctor

Public bug reported:

When I was playing Desperado III in Steam, the game closed and I went
back to desktop.

I typed this command to try to help you. I think that the problem is
Geoclue, that finish the process and next restart the process but I
don't know.

I haven't got any GPS localization system in my PC.

pitx@Pitx-PC:~$ journalctl -e
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 processe>
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of p>
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded.
sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. Shutti>
sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded.
sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe>
sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by gnome-sh>
sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Activati>
sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice.
sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps-org.gnome.Terminal.sl>
sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server...
sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Successf>
sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server.
sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 launched>
sep 20 16:13:49 Pitx-PC systemd[1704]: gnome-launched-org.gnome.Terminal.deskto>
lines 986-1008/1008 (END)
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of 
process 13161 owned by '1000' RT at priority 10.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded.
sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. 
Shutting down..
sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded.
sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by 
gnome-shell.
sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.1031' (uid=1000 pid=13505>
sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice.
sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice 
apps-org.gnome.Terminal.slice.
sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server...
sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] 
Successfully activated service 'org.gnome.Terminal'
sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server.
sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 launched 
by gnome-terminal-server process 13508.
sep 20 16:13:49 Pitx-PC systemd[1704]: 
gnome-launched-org.gnome.Terminal.desktop-13502.scope: Succeeded.
~

~
~
~
~
lines 986-1008/1008 (END)
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of 
process 13161 owned by '1000' RT at priority 10.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 
processes of 2 users.
sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]:

[Desktop-packages] [Bug 1896383] [NEW] The Text is Garbled in Detail Window

2020-09-20 Thread Mikel

Public bug reported:

*** COSMETIC ISSUE 

This issue occurs using the Budgie desktop on Ubuntu 20.04LTS.

The package using during the failure was:

gnome-control-center:
  Installed: 1:3.36.4-0ubuntu1
  Candidate: 1:3.36.4-0ubuntu1
  Version table:
 *** 1:3.36.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.36.1-1ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

As you can see on the supplied attachment, there are references to
"Hardware Address" and "Last Used."

The line containing "Last Used  Today" is being displayed over the
"Connect automatically" selection.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Sun Sep 20 09:07:35 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-09-20 (0 days ago)
InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-09-20 08-31-58.png"
   
https://bugs.launchpad.net/bugs/1896383/+attachment/5412637/+files/Screenshot%20from%202020-09-20%2008-31-58.png

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

Title:
  The Text is Garbled in Detail Window

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

Bug description:
  *** COSMETIC ISSUE 

  This issue occurs using the Budgie desktop on Ubuntu 20.04LTS.

  The package using during the failure was:

  gnome-control-center:
Installed: 1:3.36.4-0ubuntu1
Candidate: 1:3.36.4-0ubuntu1
Version table:
   *** 1:3.36.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  As you can see on the supplied attachment, there are references to
  "Hardware Address" and "Last Used."

  The line containing "Last Used  Today" is being displayed over the
  "Connect automatically" selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Sun Sep 20 09:07:35 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-09-20 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1569068] Re: mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: assertion failed: (!e->dead)

2020-09-20 Thread Norbert

** Changed in: mate-settings-daemon (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407:
  glib_defer_free: assertion failed: (!e->dead)

Status in mate-settings-daemon package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-settings-daemon.  This problem was most recently seen
  with version 1.12.1-2build1, the problem page at
  https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7
  contains more details.

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

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

[Desktop-packages] [Bug 956834] Re: gnome-file-share-properties states to receive files over bluetooth in Downloads folder, while it actually receives in Public folder

2020-09-20 Thread Norbert

** Changed in: mate-user-share (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-file-share-properties states to receive files over bluetooth in
  Downloads folder, while it actually receives in Public folder

Status in gnome-user-share package in Ubuntu:
  Fix Released
Status in mate-user-share package in Ubuntu:
  Incomplete

Bug description:
  In gnome-file-share-properties, the option to enable receiving files
  over bluetooth is labeled “Receive files in Downloads folder over
  Bluetooth”. In fact, however, it receives files in Public folder.

  I am not exactly sure which is the desired behavior (Downloads folder
  would actually make sense to me, but one could also argue in favor of
  Public folder, which can be shared over Bluetooth). But either way,
  the label and the behavior should match.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-user-share 3.0.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Fri Mar 16 11:24:16 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
  SourcePackage: gnome-user-share
  UpgradeStatus: Upgraded to precise on 2012-01-22 (53 days ago)

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

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

[Desktop-packages] [Bug 1395301] Re: Inconsistent terminology for Bluetooth pairing

2020-09-20 Thread Norbert

** Changed in: mate-user-share (Ubuntu)
   Status: New => Incomplete

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

Title:
  Inconsistent terminology for Bluetooth pairing

Status in gnome-user-share package in Ubuntu:
  Fix Released
Status in mate-user-share package in Ubuntu:
  Incomplete

Bug description:
  The "Personal File Sharing Preferences" window has two sections
  relating to Bluetooth, and those use different terminology (and user
  interface features) to describe Bluetooth pairing, both from one
  another and from the main Bluetooth settings.

  Under "Share Files over Bluetooth", the requirement for pairing is
  controlled by a tickbox labelled "Require remote devices to bond with
  this computer", while under "Receive Files over Bluetooth", it's
  controlled by a pop-up menu labelled "Accept files:" with options
  "Always" and "Only for set up devices".  As far as I can tell from the
  docuementation (which disagrees slightly about how the user interface
  should look), these controls have equivalent effects and control
  whether files can be respectively browsed or sent by unpaired devices.
  Meanwhile, the Bluetooth indicator menu uses the phrase "Set-up [sic]
  New Device", the Bluetooth pane of System Settings describes certain
  devices as "Paired", and the Ubuntu Desktop Guide explains how to
  "Connect your computer to a Bluetooth device" but helpfully explains
  that "This is also called pairing the Bluetooth devices".

  Personally, I think that both of these settings should be tickboxes,
  and their labels should both be phrased in terms of "paired" deviced,
  since that's standard Bluetooth terminology.  For consistency with the
  Ubuntu Desktop Guide, perhaps "connected" would be better (but I think
  it's less obvious what it means).

  PS: I've just found the "Control sharing over Bluetooth" page of the
  Ubuntu Desktop Guide, which adds to the fun by introducing "trusted
  devices", which are apparently yet another way of talking about paired
  devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-user-share 3.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Nov 22 10:53:26 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-file-share-properties
  InstallationDate: Installed on 2010-06-09 (1626 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: gnome-user-share
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (98 days ago)

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

-- 
Mailing list: https://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] [Question #692926]: Webkitgtk stable release 2.30 update in ubuntu

2020-09-20 Thread Rachitha

Question #692926 on webkit2gtk in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/webkit2gtk/+question/692926

Rachitha posted a new comment:
Can latest stable version of webkitgtk be ported to 20.04 atleast given
that Ubuntu  20.10 is not released yet

-- 
You received this question notification because your team Desktop
Packages is subscribed to the question.

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-20 Thread Marco Giannini

As for Ubuntu 20.10, what is the timing for the arrival of the patch?
Will it take some time after arriving on 20.04 or will they be
contextual? (yes, the bug is also present in the development branch I'm
testing)

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1896377] [NEW] My Dell wireless mouse stops after a while.

2020-09-20 Thread Satya.lin

Public bug reported:

My Dell wireless mouse stops working after a while. Sometimes it does
not work at all. I have to unplug dongle and put again to work.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 20 16:17:16 2020
DistUpgraded: 2018-09-02 08:57:59,590 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f9]
InstallationDate: Installed on 2017-02-26 (1301 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Dell Inc. Inspiron 7537
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=80dcea6d-1a75-47ed-ba9d-48393d1219fa ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-02 (749 days ago)
dmi.bios.date: 10/31/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0XJGC1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0XJGC1:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: Shark Bay ULT
dmi.product.name: Inspiron 7537
dmi.product.sku: Inspiron 7537
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  My Dell wireless mouse stops after a while.

Status in xorg package in Ubuntu:
  New

Bug description:
  My Dell wireless mouse stops working after a while. Sometimes it does
  not work at all. I have to unplug dongle and put again to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 16:17:16 2020
  DistUpgraded: 2018-09-02 08:57:59,590 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f9]
  InstallationDate: Installed on 2017-02-26 (1301 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=80dcea6d-1a75-47ed-ba9d-48393d1219fa ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (749 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0XJGC1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0XJGC1:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev:

[Desktop-packages] [Bug 1896375] [NEW] 25% cpu always for gnome-shell

2020-09-20 Thread AKHIL GOSWAMI

Public bug reported:

Tasks: 308 total,   1 running, 307 sleeping,   0 stopped,   0 zombie
%Cpu(s):  9.5 us,  3.6 sy,  0.0 ni, 86.3 id,  0.5 wa,  0.0 hi,  0.1 si,  0.0 st
MiB Mem :   3841.7 total,159.0 free,   1895.3 used,   1787.4 buff/cache
MiB Swap:   7628.0 total,   7603.7 free, 24.2 used.   1624.8 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND  
  
   2423 akhil 20   0 4310384 312188 115812 S  24.8   7.9  33:36.18 
gnome-shell
   2153 root  20   0  238576  82840  50104 S  12.6   2.1  10:59.90 Xorg 
  
   4193 akhil 20   0  938912 119056  82000 S   9.9   3.0  10:03.15 
gnome-control-c
   5308 akhil 20   0  977816  54544  40272 S   3.3   1.4   0:17.72 
gnome-terminal-
   1337 root -51   0   0  0  0 S   2.6   0.0   3:44.30 
irq/40-nvidia  
  1 root  20   0  168984  12960   8392 S   0.3   0.3   0:12.09 systemd  
  
210 root  20   0   0  0  0 S   0.3   0.0   0:01.63 
usb-storage
952 root  20   0  418364  20028  16836 S   0.3   0.5   0:09.29 
NetworkManager

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 20 16:07:16 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-08-09 (41 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  25% cpu always for gnome-shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Tasks: 308 total,   1 running, 307 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  9.5 us,  3.6 sy,  0.0 ni, 86.3 id,  0.5 wa,  0.0 hi,  0.1 si,  0.0 
st
  MiB Mem :   3841.7 total,159.0 free,   1895.3 used,   1787.4 buff/cache
  MiB Swap:   7628.0 total,   7603.7 free, 24.2 used.   1624.8 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND
 2423 akhil 20   0 4310384 312188 115812 S  24.8   7.9  33:36.18 
gnome-shell
 2153 root  20   0  238576  82840  50104 S  12.6   2.1  10:59.90 Xorg   

 4193 akhil 20   0  938912 119056  82000 S   9.9   3.0  10:03.15 
gnome-control-c
 5308 akhil 20   0  977816  54544  40272 S   3.3   1.4   0:17.72 
gnome-terminal-
 1337 root -51   0   0  0  0 S   2.6   0.0   3:44.30 
irq/40-nvidia  
1 root  20   0  168984  12960   8392 S   0.3   0.3   0:12.09 
systemd
  210 root  20   0   0  0  0 S   0.3   0.0   0:01.63 
usb-storage
  952 root  20   0  418364  20028  16836 S   0.3   0.5   0:09.29 
NetworkManager

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 16:07:16 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-08-09 (41 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1896373] [NEW] Hitting Enter can extract files in wrong place

2020-09-20 Thread abi

Public bug reported:

Steps to reproduce:

Open a zip file

Select 'Extract'

In the file browser, navigate to a directory _that contains some other
directories_

Hit Enter

What happens: Files in the zip file are extracted and placed in the
first sub-directory of the directory you are currently in.

Expected behaviour: Files in the zip file are extracted and placed in
the directory you are currently in. This was what happened in prior
versions.

With reference to the screenshot attached, if I use the mouse to click
the Extract button, the files are extracted to Documents as expected.
However, if I press the Enter key, the files are extracted to Test
Directory.

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

** Attachment added: "Screenshot from 2020-09-20 10-35-36.png"
   
https://bugs.launchpad.net/bugs/1896373/+attachment/5412585/+files/Screenshot%20from%202020-09-20%2010-35-36.png

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

Title:
  Hitting Enter can extract files in wrong place

Status in file-roller package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  Open a zip file

  Select 'Extract'

  In the file browser, navigate to a directory _that contains some other
  directories_

  Hit Enter

  What happens: Files in the zip file are extracted and placed in the
  first sub-directory of the directory you are currently in.

  Expected behaviour: Files in the zip file are extracted and placed in
  the directory you are currently in. This was what happened in prior
  versions.

  With reference to the screenshot attached, if I use the mouse to click
  the Extract button, the files are extracted to Documents as expected.
  However, if I press the Enter key, the files are extracted to Test
  Directory.

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

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

[Desktop-packages] [Bug 1891345] Re: Update to 3.37.90

This bug was fixed in the package orca - 3.38.0-1ubuntu1

---
orca (3.38.0-1ubuntu1) groovy; urgency=medium

  * Merge with Debian (LP: #1891345). Remaining changes:
+ debian/patches/unity-a11y.patch: add hacks to better work with Unity
  * Drop lowering of gst related dependencies to suggests, no longer present
in Debian.
  * control: Bump BD on at-spi2-atk, needed to have libatk1.0-dev available.
Previous versions missed this, which caused configuring to fail.  This is
just to ensure we go to dep-wait, and can be reverted for future uploads.

orca (3.38.0-1) unstable; urgency=medium

  * New upstream release.

orca (3.37.90-1ubuntu1) groovy; urgency=medium

  * New upstream release.
  * patches/gettext-macro-version-0.19: Allow building with gettext 0.19.

orca (3.37.90-1) experimental; urgency=medium

  * New upstream beta release.

orca (3.37.2-1) experimental; urgency=medium

  * New upstream alpha release.

orca (3.37.1-1) experimental; urgency=medium

  * New upstream alpha release.

orca (3.36.6-1) unstable; urgency=medium

  * New upstream release.

orca (3.36.5-1) unstable; urgency=medium

  * New upstream release (Closes: #968248)

orca (3.36.4-1) unstable; urgency=medium

  [ Samuel Thibault ]
  * New upstream release.
  * rules: Drop now-default -Wl,--as-needed option
  * control: Bump Standards-Version to 4.5.0 (no change)
  * gbp.conf: Import from upstream tags.

  [ Dmitry Shachnev ]
  * rules: Also drop -Wl,-z,defs and hardening=+all.

orca (3.36.3-1) unstable; urgency=medium

  * New upstream release.
  * patches/no-default-tty7: braille: remove fallback on VT 7.
  * control: Update alioth list domain.
  * control: Drop python3-gst-1.0, gstreamer0.10-plugins-base recommends, we
already depend on newer packages.

 -- Iain Lane   Mon, 14 Sep 2020 18:15:36 +0100

** Changed in: orca (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Update to 3.37.90

Status in orca package in Ubuntu:
  Fix Released

Bug description:
  Update to 3.37.90

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

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

[Desktop-packages] [Bug 1895898] Re: Thunderbird 78.2.2-ubuntu does not show folders etc.