date:20200809

Yes please do try Nvidia driver 440. And certainly don't upgrade the
whole OS unless you can afford the time and risk.

If the problem persists then please run the commands in comment #4. And
come to think of it, please also check /var/crash for any crash files.

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

Title:
  Freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
  1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
  2. Desired result: Drop down menu appears with options to open Chromium 
browser 
  3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
  4. Current workaround:
  When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but the 
drop-down menu remains frozen in place. Next, the frozen drop-down menu can now 
be closed by clicking on the "Activities" menu on the upper-left corner of the 
desktop and then clicking on the icon with the frozen drop-down menu. These 
actions close the frozen drop-down menu and restore normal operation of the 
Gnome III for a while until the bug pops up again. This bug has become 
especially common now rendering the desktop almost unusable and I'm thinking of 
replacing Gnome III due to this.
  Thanks, Phil

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:82:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:37:36 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
  InstallationDate: Installed on 2018-06-01 (798 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Supermicro X9DR3-F
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DR3-F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X9DR3-F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list:

[Desktop-packages] [Bug 1890891] Re: Dock icons don't appear or appear delayed if you have none pinned

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

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

Title:
  Dock icons don't appear or appear delayed if you have none pinned

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

Bug description:
  when no one program is pinned and no one open dock stop working
  normally. When I open program it appear only 10 sec later as well for
  closing. restarting with alt + f2 is solving problem until all
  programs again unpinned and closed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 16:08:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H V2-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:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H V2
  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.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/gnome-shell-extension-ubuntu-dock/+bug/1890891/+subscriptions

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

[Desktop-packages] [Bug 1890891] Re: Dock icons don't appear or appear delayed if you have none pinned

** Summary changed:

- dock
+ Dock icons don't appear or appear delayed if you have none pinned

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: groovy

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

Title:
  Dock icons don't appear or appear delayed if you have none pinned

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

Bug description:
  when no one program is pinned and no one open dock stop working
  normally. When I open program it appear only 10 sec later as well for
  closing. restarting with alt + f2 is solving problem until all
  programs again unpinned and closed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 16:08:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H V2-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:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H V2
  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.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/gnome-shell-extension-ubuntu-dock/+bug/1890891/+subscriptions

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

[Desktop-packages] [Bug 1890891] Re: dock

2020-08-09 Thread Andrei

** Attachment added: "settings.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1890891/+attachment/5400277/+files/settings.txt

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

Title:
  dock

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

Bug description:
  when no one program is pinned and no one open dock stop working
  normally. When I open program it appear only 10 sec later as well for
  closing. restarting with alt + f2 is solving problem until all
  programs again unpinned and closed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 16:08:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H V2-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:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H V2
  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.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/gnome-shell-extension-ubuntu-dock/+bug/1890891/+subscriptions

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

[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

2020-08-09 Thread mattrosencrantz

I just experienced this crash as well, but it was after being logged in
for hours.

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.36.3-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 
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/.

  Similar error:
  https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd

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

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

[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

** Description changed:

  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.
  
  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.
  
  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305
  
  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41
  
  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  ucm-implement-CardNumberByName-substitution.patch
  ucm-fix-the-possible-buffer-overflow-substitution.patch
  ucm-simplify-get_by_card-in-parser.c.patch
  ucm-implement-AlwaysTrue-Condition.Type.patch
  ucm-Allow-empty-strings-in-var-.-substitutions.patch
  ucm-substitution-remove-duplicate-allow_empty-assign.patch
  ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch
  ucm-substitute-the-merged-tree-completely.patch
  add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control
  add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols
  
  [Test Case]
  On the AMD Renoir machines:
  * Boot the system with these updated packages (already backported kernel
  drivers to Focal and oem-5.6 kernels), open the gnome-control-center
   - we could see the digital mic in the input device tab, and only one
  input device

[Desktop-packages] [Bug 1890891] Re: dock

2020-08-09 Thread Andrei

** Attachment added: "2020-08-10 08-39-27.mkv"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1890891/+attachment/5400276/+files/2020-08-10%2008-39-27.mkv

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

Title:
  dock

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

Bug description:
  when no one program is pinned and no one open dock stop working
  normally. When I open program it appear only 10 sec later as well for
  closing. restarting with alt + f2 is solving problem until all
  programs again unpinned and closed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 16:08:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H V2-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:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H V2
  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.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/gnome-shell-extension-ubuntu-dock/+bug/1890891/+subscriptions

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

[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

2020-08-09 Thread Dani

I don't know if this can help, but for me, the fail only happens after
login and then I never see it again.

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.36.3-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 
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/.

  Similar error:
  https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd

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

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

[Desktop-packages] [Bug 1882938] Re: Procedure for printing booklet does not state application program

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

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

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

Title:
  Procedure for printing booklet does not state application program

Status in gnome-user-docs package in Ubuntu:
  Expired

Bug description:
  Ubuntu 18.04.4

  
  On the Help page 
,
 the procedure for printing booklets with a single-sided printer does not tell 
the reader what program the instructions refer to. It is not possible to carry 
out the procedure without this information.

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

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

Re: [Desktop-packages] [Bug 1890843] Re: Freeze

2020-08-09 Thread Phil Marsh

Hi Daniel,
Thanks so much for your email and for your efforts looking into this for me!
The idea of upgrading to 20.04 is well-taken but involves substantial
effort to bring up my servers. Therefore, I will first try upgrading my
Nvidia to say libnvidia-cfg1-440 and libnvidia-common-440 etc because
these are the latest Nvidia packages as listed in my Synaptic app on Ubuntu
18.04? Does that make sense?
I will back up my OS prior as I alway maintain a nightly backup of my OS
via ZFS snapshots.
Thanks again and best,
Phil

On Sun, Aug 9, 2020 at 7:40 PM Daniel van Vugt <1890...@bugs.launchpad.net>
wrote:

> We also recommend upgrading to Ubuntu 20.04 if you can. It seems to have
> fewer issues than 18.04 still does. Although we do try to provide fixes
> for both, some fixes will go under the radar and only appear in newer
> versions.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1890843
>
> Title:
>   Freeze
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
>   1. double left mouse click on launcher icon on left toolbar (usually
> happens with Chromium Browser icon)
>   2. Desired result: Drop down menu appears with options to open Chromium
> browser
>   3. Actual result when bug appears: Drop down menu appears then whole
> desktop freezes. No further mouseclicks on display work. Dropdown menu
> remains frozen on display.
>   4. Current workaround:
>   When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but
> the drop-down menu remains frozen in place. Next, the frozen drop-down menu
> can now be closed by clicking on the "Activities" menu on the upper-left
> corner of the desktop and then clicking on the icon with the frozen
> drop-down menu. These actions close the frozen drop-down menu and restore
> normal operation of the Gnome III for a while until the bug pops up again.
> This bug has become especially common now rendering the desktop almost
> unusable and I'm thinking of replacing Gnome III due to this.
>   Thanks, Phil
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
>   Uname: Linux 4.15.0-112-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> nvidia_modeset nvidia
>   .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory:
> '/proc/driver/nvidia/gpus/:82:00.0'
>   .proc.driver.nvidia.registry: Binary: ""
>   .proc.driver.nvidia.version:
>NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14
> 01:01:53 PDT 2020
>GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
>   ApportVersion: 2.20.9-0ubuntu7.16
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Aug  7 12:37:36 2020
>   DistUpgraded: Fresh install
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1)
> (prog-if 00 [VGA controller])
>  Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
>   InstallationDate: Installed on 2018-06-01 (798 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   MachineType: Supermicro X9DR3-F
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic
> root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/31/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 3.0a
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: X9DR3-F
>   dmi.board.vendor: Supermicro
>   dmi.board.version: 0123456789
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Supermicro
>   dmi.chassis.version: 0123456789
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: X9DR3-F
>   dmi.product.version: 0123456789
>   dmi.sys.vendor: Supermicro
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2~18.04.1
>   version.libgl1-mesa-dri:

[Desktop-packages] [Bug 1558768] Re: gvfsd-trash causing high CPU-load when try to empty trash with thousands of files

2020-08-09 Thread Humphrey van Polanen Petel

reported upstream at https://gitlab.gnome.org/GNOME/gvfs/-/issues/503

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #503
   https://gitlab.gnome.org/GNOME/gvfs/-/issues/503

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

Title:
  gvfsd-trash causing high CPU-load when try to empty trash with
  thousands of files

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 16.04 (Xenial Xerus) Daily Build
  - AMD64
  - Unity

  Steps to reproduce:
  - a folder with thousands of files (here about 15000 files with a overall 
size of 1.5 GB)
  - delete files to trash
  - right-click at the trash icon
  - click empty trash

  A dialog "Dateioperationen" shows "vorbereiten" (it's German, I think
  in English the dialog has the title "file operations" and shows the
  text "prepare").

  This happens at this point:
  - the dialog remains unchanged
  - the process gvfsd-trash consumes up to 75% CPU, see output of top

  After 30 minutes of waiting for any reaction I killed the process. The
  trash still contains all the files.

  jan@janvm160464:~$ top

  top - 20:17:24 up 31 min,  1 user,  load average: 1,94, 1,97, 1,68
  Tasks: 244 gesamt,   5 laufend, 239 schlafend,   0 gestoppt,   0 Zombie
  %CPU(s): 85,1 be, 14,6 sy,  0,0 ni,  0,0 un,  0,0 wa,  0,0 hi,  0,3 si,  0,0 
st
  KiB Spch :  4037984 gesamt,  2142152 frei,   900784 belegt,   995048 
Puff/Cache
  KiB Swap:0 gesamt,0 frei,0 belegt.  3028940 verfü 
Spch 

PID USER  PR  NIVIRTRESSHR S %CPU %MEM ZEIT+ BEFEHL 
  
   1760 jan   20   0  454696  24448   7840 R 69,1  0,6  20:05.18 
gvfsd-trash  
   1690 jan   20   0  781012  71096  36440 S 12,0  1,8   6:13.42 nautilus   
  
   2649 jan   20   0  660088  41700  30328 S 10,3  1,0   0:04.29 gedit  
  
315 root  20   0   32236   2936   2500 R  3,3  0,1   1:06.21 
systemd-jou+ 
825 root  20   0  383184  77448  31492 S  1,3  1,9   0:15.84 Xorg   
  
   1543 jan   20   0 1254876 189468  65780 S  1,3  4,7   0:19.38 compiz 
  
641 syslog20   0  256380   3364   2684 S  1,0  0,1   0:16.81 rsyslogd   
  
   1521 jan   20   0  567508  32776  25756 S  0,7  0,8   0:01.16 
unity-panel+ 
   1448 jan   20   0   39728316 12 S  0,3  0,0   0:00.13 
upstart-dbu+ 
   2258 root  20   0   0  0  0 S  0,3  0,0   0:00.23 
kworker/u12+ 
   2695 jan   20   0   48912   3868   3136 R  0,3  0,1   0:00.01 top
  
  1 root  20   0  119720   5664   3780 S  0,0  0,1   0:02.72 systemd
  
  2 root  20   0   0  0  0 S  0,0  0,0   0:00.00 kthreadd   
  
  3 root  20   0   0  0  0 R  0,0  0,0   0:01.45 
ksoftirqd/0  
  5 root   0 -20   0  0  0 S  0,0  0,0   0:00.00 
kworker/0:0H 
  7 root  20   0   0  0  0 R  0,0  0,0   0:06.15 rcu_sched  
  
  8 root  20   0   0  0  0 S  0,0  0,0   0:00.00 rcu_bh

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

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

[Desktop-packages] [Bug 1798828] Re: gvfsd-trash fills up memory (uses about 1 GB) if Trash contains thousands of files

2020-08-09 Thread Humphrey van Polanen Petel

reported upstream at https://gitlab.gnome.org/GNOME/gvfs/-/issues/503

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #503
   https://gitlab.gnome.org/GNOME/gvfs/-/issues/503

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

Title:
  gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
  thousands of files

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
  thousands of files (I had ~8000)

  I noticed this on Ubuntu 16.04 64-bit with GNOME Shell installed:
  ~$ ps aux |grep -i trash
  uni0231910  6.2 20.0 1541900 789352 ?  Sl   12:53  10:11 
/usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0

  Problem can be "solved" by emptying Trash bin.

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

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

[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

This is the pulseaudio debdiff for Groovy.

thx.


** Patch added: "pulseaudio_13.99.1-1ubuntu9.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889217/+attachment/5400275/+files/pulseaudio_13.99.1-1ubuntu9.debdiff

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

This is the alsa-lib debdiff for Groovy.

thx.


** Patch added: "alsa-lib_1.2.2-2.3ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889217/+attachment/5400273/+files/alsa-lib_1.2.2-2.3ubuntu2.debdiff

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1890956] Re: Mouse and keyboard stop working after suspend

Please:

1. Reboot.

2. Suspend and reproduce the problem.

3. Reboot again.

4. Run:

   journalctl -b-1 > prevboot.txt

   and attach the resulting text file here.


** Package changed: gdm3 (Ubuntu) => xserver-xorg-input-libinput (Ubuntu)

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

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

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

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

** Changed in: xserver-xorg-input-libinput (Ubuntu)
   Status: New => Incomplete

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

Title:
  Mouse and keyboard stop working after suspend

Status in libinput package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  dm3:
    Installed: 3.34.1-1ubuntu1
    Candidate: 3.34.1-1ubuntu1
    Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Booting off of a live usb, the trackpad, external mouse, and internal
  keyboard stop responding to input after suspend. On my updated
  install, the laptop trackpad works, but the other two inputs do not
  after suspend/wake. I can log in using the on screen keyboard.
  Unplugging the mouse and plugging it in does not fix it. The inputs
  don't respond while logged in either. Only a reboot fixes it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  9 14:00:59 2020
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2020-06-20 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

This is alsa-ucm-conf debdiff for Groovy.

thx.


** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889217/+attachment/5400274/+files/alsa-ucm-conf_1.2.2-1ubuntu2.debdiff

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1890908] Re: all the video could not be played on ubuntu Wayland environment

Please open a Terminal window and then launch your video player from
there by running 'vlc'. If the problem still happens, what do you see in
the Terminal window?

** Package changed: totem (Ubuntu) => vlc (Ubuntu)

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

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

Title:
  all the video could not be played on ubuntu Wayland environment

Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  I recently installed amdgpu pro driver.it works perfectly than
  ordinary inbuild amd drivers in linux kernal.every video players
  including VLC media player and ubuntu video player could not play any
  videos!but they are able to work in Gnome,ubuntu,Ubuntu budgie
  environments.the problem is in ubuntu Wayland environment.ubuntu video
  player is unable to start in ubuntu Wayland  environment,VLC
  automatically closes without warning when i open any vido file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 21:27:43 2020
  InstallationDate: Installed on 2020-06-20 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  LogAlsaMixer:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1890954] Re: Gnome assigns java app's windows to Visual Studio Code even after I quit visual studio code

First we need to confirm if this is a general gnome-shell problem or
unique to ubuntu-dock. Please open the 'Extensions' app and disable
'Ubuntu Dock'. Now does the same bug occur with the regular GNOME dock?


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

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-ubuntu-dock (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/1890954

Title:
  Gnome assigns java app's windows to Visual Studio Code even after I
  quit visual studio code

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

Bug description:
  This happens after I close Visual Studio's windows while the PC is
  stuttering loading and writing data to the HDD.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Aug  9 13:27:04 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-07-06 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890891] Re: dock

Please run this command:

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

and then attach the resulting text file here.

Please also attach a video of the problem if you can. Or even a photo or
screenshot of exactly where it is happening.


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

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

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (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/1890891

Title:
  dock

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

Bug description:
  when no one program is pinned and no one open dock stop working
  normally. When I open program it appear only 10 sec later as well for
  closing. restarting with alt + f2 is solving problem until all
  programs again unpinned and closed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 16:08:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H V2-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:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H V2
  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.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/gnome-shell-extension-ubuntu-dock/+bug/1890891/+subscriptions

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

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

^^^
That means the bug is "Fix Released". If the exact fix can be identified then
we would be able to provide a fix to 18.04.

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

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

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

Status in gnome-control-center package in Ubuntu:
Fix Released

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

Steps to reproduce this bug:

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

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

or 5. Reboot.

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

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

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

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

[Desktop-packages] [Bug 1890957] Re: My Night Light doesn't work at all.

** Tags added: nvidia

** Summary changed:

- My Night Light doesn't work at all.
+ [nvidia] My Night Light doesn't work at all.

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

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

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

[Desktop-packages] [Bug 1890866] Re: Ubuntu 20.04 don't recognize my USB 3.0 Monitor (Works well in Win10)

We can't track bugs in 3rd party drivers that didn't come from Ubuntu.
So that covers Xorg sessions. But please try selecting 'Ubuntu on
Wayland' from the login screen, which should support DisplayLink and is
supported by the official Ubuntu packages.


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

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

** Tags added: displaylink

** Package changed: ubuntu => mutter (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/1890866

Title:
  Ubuntu 20.04 don't recognize my USB 3.0 Monitor (Works well in Win10)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a USB 3.0 Portable Monitor that works well under Win10, but
  when I reboot the same laptop under Ubuntu 20.04, it's not
  recognized...

  Downloaded the Asus MB169B+ Driver:
  https://www.asus.com/ca-en/Monitors/MB169BPlus/HelpDesk_Download/
  Version 5.3.1 2020/06/15
  
https://dlcdnets.asus.com/pub/ASUS/LCD%20Monitors/MB16AP/ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

  Extracted the zip file:
  ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

  Ran the command to make it executable:
  chmod 755 displaylink-driver-5.3.1.34.run

  Executed the file:
  sudo ./displaylink-driver-5.3.1.34.run

  Install completed, rebooted the machine

  Monitor still in idle mode (orange button - if it was recognized, it
  would be white)

  FYI - I don't have a graphic card, just the one embedded in the Intel
  i5 6th gen

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 23:57:14 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: evdi, 1.7.0, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:81cb]
  InstallationDate: Installed on 2020-04-28 (101 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=981629fe-8e85-4ada-bacb-8fa11c48b000 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81CB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 60.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd11/26/2019:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CB:rvrKBCVersion60.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY Notebook
  dmi.product.sku: W7E04UA#ABL
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1890863] Re: Display does not come on after suspend

After the problem happens again and you power cycle, please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


** Tags added: amdgpu

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Changed in: xserver-xorg-video-amdgpu (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/1890863

Title:
  Display does not come on after suspend

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

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  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/xserver-xorg-video-amdgpu/+bug/1890863/+subscriptions

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

[Desktop-packages] [Bug 1890865] Re: Nouveau X.org: Stale texture data and flicker in small SDL2 program, but nvidia-440 works

** Summary changed:

- Nouveau X.org: Stale texture data and flicker in small SDL2 program
+ Nouveau X.org: Stale texture data and flicker in small SDL2 program, but 
nvidia-440 works

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

** Tags added: nouveau

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

Title:
  Nouveau X.org: Stale texture data and flicker in small SDL2 program,
  but nvidia-440 works

Status in linux package in Ubuntu:
  New

Bug description:
  Video of bug: https://youtu.be/O0__VNN9G_o

  At 0:11 in the video you see old web browser data showing up in my
  program.

  At 0:19 when I close a window in my program the texture for my piano key 
letters
  flicker. By luck the texture for my keys sometimes flickers to stuff 
previously
  displayed on my desktop. This flickering is linked to my mouse 
movement/placement.

  When I run my program with the proprietary 440 NVIDIA driver things work fine.
  I am on Ubuntu budgie 20.04 using XFCE on X.org X11.

  The SDL2 program source:

  https://github.com/kevinacahalan/piano_waterfall

  git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Aug  7 23:35:05 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251]
  InstallationDate: Installed on 2020-05-05 (95 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: Dell Inc. OptiPlex 3010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=5fe179e5-be36-426b-9297-8ef7a1af2c0c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 042P49
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/31/2013:svnDellInc.:pnOptiPlex3010:pvr01:rvnDellInc.:rn042P49:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 3010
  dmi.product.version: 01
  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
  xserver.bootTime: Fri Aug  7 21:38:07 2020
  xserver.configfile: default
  xserver.errors: client bug: timer event11 debounce short: scheduled expiry is 
in the past (-2ms), your system is too slow
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1890866] [NEW] Ubuntu 20.04 don't recognize my USB 3.0 Monitor (Works well in Win10)

You have been subscribed to a public bug:

I have a USB 3.0 Portable Monitor that works well under Win10, but when
I reboot the same laptop under Ubuntu 20.04, it's not recognized...

Downloaded the Asus MB169B+ Driver:
https://www.asus.com/ca-en/Monitors/MB169BPlus/HelpDesk_Download/
Version 5.3.1 2020/06/15
https://dlcdnets.asus.com/pub/ASUS/LCD%20Monitors/MB16AP/ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

Extracted the zip file:
ASUS_MB_Series_driver_for_Ubuntu_5.3.1.zip

Ran the command to make it executable:
chmod 755 displaylink-driver-5.3.1.34.run

Executed the file:
sudo ./displaylink-driver-5.3.1.34.run

Install completed, rebooted the machine

Monitor still in idle mode (orange button - if it was recognized, it
would be white)

FYI - I don't have a graphic card, just the one embedded in the Intel i5
6th gen

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  7 23:57:14 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: evdi, 1.7.0, 5.4.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81cb]
InstallationDate: Installed on 2020-04-28 (101 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=981629fe-8e85-4ada-bacb-8fa11c48b000 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81CB
dmi.board.vendor: HP
dmi.board.version: KBC Version 60.27
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd11/26/2019:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CB:rvrKBCVersion60.27:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
dmi.product.name: HP ENVY Notebook
dmi.product.sku: W7E04UA#ABL
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug displaylink focal ubuntu
-- 
Ubuntu 20.04 don't recognize my USB 3.0 Monitor (Works well in Win10)
https://bugs.launchpad.net/bugs/1890866
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

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

[Desktop-packages] [Bug 1890843] Re: Freeze

We also recommend upgrading to Ubuntu 20.04 if you can. It seems to have
fewer issues than 18.04 still does. Although we do try to provide fixes
for both, some fixes will go under the radar and only appear in newer
versions.

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

Title:
  Freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
  1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
  2. Desired result: Drop down menu appears with options to open Chromium 
browser 
  3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
  4. Current workaround:
  When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but the 
drop-down menu remains frozen in place. Next, the frozen drop-down menu can now 
be closed by clicking on the "Activities" menu on the upper-left corner of the 
desktop and then clicking on the icon with the frozen drop-down menu. These 
actions close the frozen drop-down menu and restore normal operation of the 
Gnome III for a while until the bug pops up again. This bug has become 
especially common now rendering the desktop almost unusable and I'm thinking of 
replacing Gnome III due to this.
  Thanks, Phil

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:82:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:37:36 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
  InstallationDate: Installed on 2018-06-01 (798 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Supermicro X9DR3-F
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DR3-F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X9DR3-F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1890843] Re: Freeze

Please attach a photo of the problem if you can, and also run:

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

and attach the resulting text file here.


** Summary changed:

- Xorg freeze
+ Freeze

** Package changed: xorg (Ubuntu) => gnome-shell (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/1890843

Title:
  Freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
  1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
  2. Desired result: Drop down menu appears with options to open Chromium 
browser 
  3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
  4. Current workaround:
  When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but the 
drop-down menu remains frozen in place. Next, the frozen drop-down menu can now 
be closed by clicking on the "Activities" menu on the upper-left corner of the 
desktop and then clicking on the icon with the frozen drop-down menu. These 
actions close the frozen drop-down menu and restore normal operation of the 
Gnome III for a while until the bug pops up again. This bug has become 
especially common now rendering the desktop almost unusable and I'm thinking of 
replacing Gnome III due to this.
  Thanks, Phil

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:82:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:37:36 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
  InstallationDate: Installed on 2018-06-01 (798 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Supermicro X9DR3-F
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DR3-F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X9DR3-F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list:

[Desktop-packages] [Bug 1890843] Re: Freeze

Sorry that Xorg log attached seems to be from 2018 so is not relevant to
this bug. It's probably still a good idea to install a newer Nvidia
driver. If that doesn't solve it then please run:

  journalctl -b0 > journal-0.txt
  journalctl -b-1 > journal-1.txt
  journalctl -b-2 > journal-2.txt
  gsettings list-recursively org.gnome.shell > settings.txt

and attach the resulting text files here.

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

Title:
  Freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
  1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
  2. Desired result: Drop down menu appears with options to open Chromium 
browser 
  3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
  4. Current workaround:
  When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but the 
drop-down menu remains frozen in place. Next, the frozen drop-down menu can now 
be closed by clicking on the "Activities" menu on the upper-left corner of the 
desktop and then clicking on the icon with the frozen drop-down menu. These 
actions close the frozen drop-down menu and restore normal operation of the 
Gnome III for a while until the bug pops up again. This bug has become 
especially common now rendering the desktop almost unusable and I'm thinking of 
replacing Gnome III due to this.
  Thanks, Phil

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:82:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:37:36 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
  InstallationDate: Installed on 2018-06-01 (798 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Supermicro X9DR3-F
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DR3-F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X9DR3-F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau:

[Desktop-packages] [Bug 1890843] Re: Freeze

Oh, actually, I think I can see the problem in your logs. You have a
proprietary Nvidia kernel driver installed but Xorg is using the
(unstable) open source driver.

So the driver is not properly installed AND it seems to be the wrong
version. Please install Nvidia driver version 440, which you should be
able to do via the 'Additional Drivers' app. Then reboot. If the problem
continues after that then please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

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

Title:
  Freeze

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
  1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
  2. Desired result: Drop down menu appears with options to open Chromium 
browser 
  3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
  4. Current workaround:
  When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but the 
drop-down menu remains frozen in place. Next, the frozen drop-down menu can now 
be closed by clicking on the "Activities" menu on the upper-left corner of the 
desktop and then clicking on the icon with the frozen drop-down menu. These 
actions close the frozen drop-down menu and restore normal operation of the 
Gnome III for a while until the bug pops up again. This bug has become 
especially common now rendering the desktop almost unusable and I'm thinking of 
replacing Gnome III due to this.
  Thanks, Phil

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:82:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:37:36 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
  InstallationDate: Installed on 2018-06-01 (798 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Supermicro X9DR3-F
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DR3-F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X9DR3-F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1

[Desktop-packages] [Bug 1890802] Re: Big performance degradation in X11 + 4K resolution + fractional scaling in second monitor compared to Wayland

This is expected. Fractional scaling in Xorg sessions works by rendering
at a higher resolution than your screen(s). So that increases the
likelihood of stuttering compared to integer scaling.

That specific issue will never be fixed because it's a required trade-
off to get fractional scaling working in Xorg. HOWEVER, general
performance will increase a lot in future versions like Ubuntu 20.10 so
that hopefully will be enough to offset and eliminate all the problems
you see.

As for fractional scaling making things slower than not scaling, that is
expected and can't be fixed. If you can then please use Wayland instead.

** Tags added: xrandr-scaling

** Changed in: mutter (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Big performance degradation in X11 + 4K resolution + fractional
  scaling in second monitor compared to Wayland

Status in mutter package in Ubuntu:
  Won't Fix

Bug description:
  Laptop: Lenovo ThinkPad L480
  Graphics: Intel UHD Graphics 620 (KBL GT2)
  Second monitor: Philips 276E8VJSB/00 4K UHD

  There is a big performance degradation in an X11 session + 4K
  resolution + 125% fractional scaling in the second monitor compared to
  a Wayland session. The mouse cursor moves very slow, dragging Windows
  is very slow, scrolling in Firefox is very laggy, so everything
  becomes unusable. The performance degradation applies in both displays
  even though fractional scaling is only applied in the second 4K
  monitor.

  Whereas in Wayland, the performance is much better in 4K resolution +
  fractional scaling in the second monitor, the mouse cursor and
  dragging windows are a lot smoother. I just sometimes notice a slight
  jump in the mouse cursor but only in the second monitor, the built-in
  monitor behaves normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:00:26 2020
  InstallationDate: Installed on 2020-04-26 (102 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890001] Re: Random stuttering while in game

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

That's definitely still bug 1849142 coming from:

  /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com

Are you sure you disabled 'Ubuntu AppIndicators' in the 'Extensions'
app?

Remember to use the 'Extensions' app and not 'Gnome Tweaks'.

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

Title:
  Random stuttering while in game

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Updated kernel to 5.7.12 and updated nvidia driver to 450 yesterday
  but only experiencing this today.

  Random stuttering while playing minecraft, no clue what's causing it
  but I checked system monitor and it shows random spikes of a cpu
  thread to 100% and some spikes staying at 100% for a prolonged period.

  It may be related to me updating my video driver that is not
  recommended so I will see if switching down will resolve the issue.  I
  never had this issue on driver 440.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.7.12-050712-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .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  450.57  Sun Jul  5 14:42:25 
UTC 2020
   GCC version:  gcc version 10.2.0 (GCC)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  1 13:57:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 
2080 Rev. A] [1462:3726]
  InstallationDate: Installed on 2020-07-31 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.12-050712-lowlatency 
root=UUID=76f51654-be39-4436-80da-a240e8149ca5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390 AORUS MASTER-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSMASTER-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z390 AORUS MASTER
  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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1890650] Re: Activities button, Alt-F1, and super not working after upgrade to 20.04

The issue was probably caused by one of these:

org.gnome.shell enabled-extensions ['permanent-
notificati...@bonzini.gnu.org', 'places-menu@gnome-shell-
extensions.gcampax.github.com', 'panel-
o...@berend.de.schouwer.gmail.com', 'user-theme@gnome-shell-
extensions.gcampax.github.com', 'window-list@gnome-shell-
extensions.gcampax.github.com', 'launch-new-instance@gnome-shell-
extensions.gcampax.github.com', 'native-window-placement@gnome-shell-
extensions.gcampax.github.com', 'screenshot-window-sizer@gnome-shell-
extensions.gcampax.github.com', 'workspace-indicator@gnome-shell-
extensions.gcampax.github.com', 'windowsNavigator@gnome-shell-
extensions.gcampax.github.com', 'drive-menu@gnome-shell-
extensions.gcampax.github.com', 'audio-output-switcher@anduchs',
'disconnect-w...@kgshank.net']

In future please be sure to remove extensions before reporting bugs to
gnome-shell.


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

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

Title:
  Activities button, Alt-F1, and super not working after upgrade to
  20.04

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  If I hit the Activities button, all open applications are hidden.
  There is no way to get the applications to display again. The
  application I select is started, and shows up on the vertical bar in
  the left with an orange dot by it.

  What magic is needed to bring the applications back?

  They are still there. I see them when I go to log out. Logging out is
  the only option for restoring Gnome.

  The same problem happens if I hit Alt-F1 or Super. Shouldn't these
  toggle?

  The only way to get a screen shot it with my phone. Sorry for the
  quality. You can see on the left that I started gimp.Up to 19.10, when
  I used "Activities", it would launch the app and then return to my
  running applications.

  Originally asked here:

  https://askubuntu.com/questions/1264414/activities-button-alt-f1-and-
  super-not-working-after-upgrade-to-20-04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.23
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  6 13:29:43 2020
  InstallationDate: Installed on 2018-10-14 (661 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-08-03 (2 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1888120] Re: Headphones detected like Speakers and Volume Problem

There is no difference between the signal output for headphones or for
speakers. The software cannot ever know which is plugged in, and
actually should not behave differently in either case.

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

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

Title:
  Headphones detected like Speakers and Volume Problem

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I bought a Kyus Headphones, this model exactly:
  https://www.pccomponentes.com/krom-kyus-auriculares-gaming

  and when I go to Settings/Sound in Ubuntu 20.04 LTS, I can watch
  Speakers - USB Audio Device, not Headphones.

  In Windows if the system detect the headphones like speakers, the
  sound is louder and upset, I think that Ubuntu should have a similar
  problem.

  Another problem is the control volume. When I change the volume using
  a key combination to up volume and down volume. If I up the volume
  when I have got 0 level, the volume doesn't ear in the two first steps
  that I pulsed UP volume. Other problem is, that if I press up volume
  it change a lot with only one press of up volume. This generate the
  situation of volume too low and when press up, the volume is too high.

  
  Thanks for your time.

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

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

[Desktop-packages] [Bug 1888425] Re: Ubuntu Freezy - Probably Gnome-Shell Bug

Please follow these instructions in case the freeze is a consequence of
something crashing:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Tags added: nvidia

** Summary changed:

- Ubuntu Freezy - Probably Gnome-Shell Bug
+ [nvidia] Ubuntu Freezy - Probably Gnome-Shell 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/1888425

Title:
  [nvidia] Ubuntu Freezy - Probably Gnome-Shell Bug

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM.

  Ubuntu sometimes freezes and I can't do nothing. I need to reboot the
  system pressing reset button.

  Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game 
in Steam. 
  When I select one game and change to another selecting the other, Ubuntu 
freezes. But it doesn't happen always.

  I read that could be a problem with Ryzen CPUs, but I don't know.

  Sorry and thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 22:11:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-24 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed

The issue is continued in bug 1886059.

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

Title:
  gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost'' failed

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's
  duplicated across multiple problem reports according to locale:

  https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c
  https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b
  https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7
  https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0

  [Test Case]

  None known. The plan is to just continue monitoring crash reports.
  Still, we are confident this is the fix because:

   * The offending source code in libx11 tells us it is :) and
   * The crash only started in Ubuntu with gnome-shell 3.34, which is the
     exact release in which XInitThreads was removed from mutter.

  [Regression Potential]

  Low. We add a single function call that tells libX11 to enable thread
  safety. This is the same as what we had in bionic, cosmic and disco,
  so it's well tested.

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

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

[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker

** Tags removed: eoan
** Tags added: focal

** Changed in: pulseaudio (Ubuntu)
   Status: Won't Fix => Confirmed

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

Title:
  System volume slider only works between ~90% and 100% with a USB 2.0
  speaker

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is only with my USB 2.0 speaker[1] - with other devices, it works
  fine and the slider's 0% corresponds to silent and 100% full. With my
  USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
  Device', it only has an effect between about 90% and 100%.

  I took a video of the problem and uploaded it here:

  http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

  [1]
  
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 23 10:00:17 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-07-19 (156 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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

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

[Desktop-packages] [Bug 1795021] Re: gsd-xsettings high memory usage

2020-08-09 Thread Yogeshwer Sharma

This makes my Ubuntu installation hard to use after a day of use.

Is there any workaround for this? Any help or pointer would be
appreciated.

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

Title:
  gsd-xsettings high memory usage

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

Bug description:
  gsd-xsettings is using ~700MB of memory. I think there could be some
  memory leak because I don't remember it ever happening before.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Sep 28 18:42:46 2018
  InstallationDate: Installed on 2017-08-21 (403 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected

the issue of computer frozen probably is caused by graphic driver,
please add nomodeset in the bootargs or install the nvidia-driver-450
instead of in-tree driver nouveau.

And please install 20.04 and upgrade all packages to the latest version,
I believe the internal mic will work.

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

Title:
  [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not
  detected

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I 
have no internal mic detected.
  The GNOME settings sound entry list is empty. Speaker sound is working 
properly.

  When hooking a microphone enabled headphone on the jack plug, the
  headphones mic is then detected, but there is now no sound output on
  the headphone.

  I've been looking for a few similar issues on recent (HP or not)
  laptops and found a few similar issues :

  Bug #1523100
  Bug #1837821

  so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx 
hardware.
  I already tryed quite a few of the workaroubds/fix available here and there 
(e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module 
etc. none with success)

  I'm available to test/provide any additional needed data.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mathieu1719 F pulseaudio
   /dev/snd/controlC0:  mathieu1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 13:33:14 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Only some of inputs are working
  Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R92 Ver. 01.03.04
  dmi.board.name: 860F
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 65.23.00
  dmi.chassis.asset.tag: 5CD944676Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook 15 G6
  dmi.product.sku: 6VD99AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591

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

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

[Desktop-packages] [Bug 1268182] Re: Computer name changed

2020-08-09 Thread Michael Terry

To Vej's points:

> Fix the problem, that accepting the changed hostname is not persistent

It *should* already be persistent. In the sense that each time duplicity
backs up, it writes the current hostname to the manifest and checks
against that going forward.

I think it just looks like it's not persistent because the fqdn can
frequently change.

> Find a solution for the problem, that the hostname from
socket.getfqdn() does not always match the one from socket.gethostname()

I've proposed a MR upstream to use gethostname instead of getfqdn. With
this change, hopefully we don't need to do anything on our end.

https://gitlab.com/duplicity/duplicity/-/merge_requests/24

I'll close this deja-dup ticket, since I think we can just let duplicity
handle this.

** Changed in: deja-dup
   Status: Confirmed => Invalid

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Computer name changed

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  I am/was using Deja-Dup (version 26.0)  on Fedora 19, I modified my router 
settings to use openDNS instead of my ISP's DNS. 
  Then the next time I ran Deja-dup I had the message:-

  The existing backup is of a computer named
  advancedsearch.virginmedia.com, but the current
  computer's name is Zotac-Zbox-ID82. If this is
  unexpected, you should backup to a different location.

  Since I wasn't asked to specify a computer name, and the underlying
  "duplicity" (version: 0.6.22) would appear to get the machine name
  from the wrong file, I understand that the computer name is kept in
  two files (a bad practice in my mind).

  So can the interface be changed to show and or allow one to specify
  what hostname is used?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1268182/+subscriptions

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

[Desktop-packages] [Bug 1890967] [NEW] Jumper EZpad touchpad registered as mouse

2020-08-09 Thread Todd France

Public bug reported:

The touchpad on my "Jumper EZPad S6 Pro" registers as a mouse and can not be 
disabled while typing.
Diagnostics attached.


FWIW I'd be content with a workrauond to disable while typing; otherwise I'm 
contnet w/ touchpad functionality.

** Affects: xserver-xorg-input-libinput (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "diagnostics"
   https://bugs.launchpad.net/bugs/1890967/+attachment/5400253/+files/bug

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

Title:
  Jumper EZpad touchpad registered as mouse

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  The touchpad on my "Jumper EZPad S6 Pro" registers as a mouse and can not be 
disabled while typing.
  Diagnostics attached.

  
  FWIW I'd be content with a workrauond to disable while typing; otherwise I'm 
contnet w/ touchpad functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1890967/+subscriptions

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

2020-08-09 Thread crvi

Find whether you are running ubuntu in x11 mode or wayland mode. The
following could help:

https://unix.stackexchange.com/questions/202891/how-to-know-whether-
wayland-or-x11-is-being-used

If you are running in wayland mode, can you logout and login in x11
mode, and see if the issue happens. "mmkeys" plugin was written for x11.
It might need to be modified to support wayland.

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1880744] Re: package emacs-gtk (not installed) failed to install/upgrade: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 26.3~1.git96

emacs26-common 26.3~1.git96dd019-kk1+19.10
emacs26-nox 26.3~1.git96dd019-kk1+19.10

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

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


** Changed in: emacs (Ubuntu)
   Status: New => Invalid

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

Title:
  package emacs-gtk (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package
  emacs26-nox 26.3~1.git96dd019-kk1+19.10

Status in emacs package in Ubuntu:
  Invalid

Bug description:
  Hey,

  I upgraded to ubuntu 20 and a red little minus sign popped up on my top right 
corner about unmet package dependencies. I have tried all the commands like 
"sudo dpkg --configure -a" "sudo apt install -f" but nothing seems to solve my 
problem.
  This is a big problem because I cant install new packages on my laptop 
without solving this first.
  Please reply as soon as possible.

  
  The error message:
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   emacs : Depends: emacs-gtk (>= 1:26.3) but it is not installed or
emacs-lucid (>= 1:26.3) but it is not installed or
emacs-nox (>= 1:26.3) but it is not installed
   emacs-bin-common : Depends: emacs-common (= 1:26.3+1-1ubuntu2) but it is not 
installed
   emacs-el : Depends: emacs-common (= 1:26.3+1-1ubuntu2) but it is not 
installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: emacs-gtk (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   emacs-common:amd64: Install
   emacs-gtk:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue May 26 20:45:47 2020
  ErrorMessage: trying to overwrite '/usr/share/emacs/26.3/etc/DOC', which is 
also in package emacs26-nox 26.3~1.git96dd019-kk1+19.10
  InstallationDate: Installed on 2020-04-20 (35 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: emacs
  Title: package emacs-gtk (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/emacs/26.3/etc/DOC', which is also in package emacs26-nox 
26.3~1.git96dd019-kk1+19.10
  UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago)

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

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

[Desktop-packages] [Bug 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)

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

** Changed in: nvidia-prime (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia+amdgpu] System sometimes starts with a black screen with
  Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works
  perfectly)

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed Ubuntu on a laptop that has a Ryzen APU (with
  Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first
  issue that this kind of setup gives on a fresh install is that that
  PRIME render offloading doesn't work, I presume that Ubuntu currently
  sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia
  but that's another separate issue. As a workaround I created an Xorg
  configuration (attached in this report) that sets up both GPUs (with
  the appropiate BusIDs), after such configuration is applied the system
  boots fine with AMD integrated graphics being used and the ability to
  switch to Nvidia with PRIME render off-loading.

  The problem comes when I try to use the computer the next day, then it
  gives me a black screen without having the ability to switch to a tty,
  the boot log doesn't throw any errors I just see a black screen after
  Xorg tries to start. I can make it work again by entering in recovery
  mode, logging into a root console and switching between "nvidia" and
  "on-demand" modes using prime-select (I set it up to "on-demand"
  profile after installing Ubuntu).

  For the moment I cannot provide any relevant logs since it's now
  working fine (and I don't remember seeing any errors on Xorg logs),
  also I don't really know where to look for this kind of issues.

  My system information:
  -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 
440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  -RAM: 8 GB
  -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4)
  -Xorg 1.20.8-2ubuntu2

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

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

[Desktop-packages] [Bug 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia+amdgpu] System sometimes starts with a black screen with
  Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works
  perfectly)

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed Ubuntu on a laptop that has a Ryzen APU (with
  Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first
  issue that this kind of setup gives on a fresh install is that that
  PRIME render offloading doesn't work, I presume that Ubuntu currently
  sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia
  but that's another separate issue. As a workaround I created an Xorg
  configuration (attached in this report) that sets up both GPUs (with
  the appropiate BusIDs), after such configuration is applied the system
  boots fine with AMD integrated graphics being used and the ability to
  switch to Nvidia with PRIME render off-loading.

  The problem comes when I try to use the computer the next day, then it
  gives me a black screen without having the ability to switch to a tty,
  the boot log doesn't throw any errors I just see a black screen after
  Xorg tries to start. I can make it work again by entering in recovery
  mode, logging into a root console and switching between "nvidia" and
  "on-demand" modes using prime-select (I set it up to "on-demand"
  profile after installing Ubuntu).

  For the moment I cannot provide any relevant logs since it's now
  working fine (and I don't remember seeing any errors on Xorg logs),
  also I don't really know where to look for this kind of issues.

  My system information:
  -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 
440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  -RAM: 8 GB
  -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4)
  -Xorg 1.20.8-2ubuntu2

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

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

[Desktop-packages] [Bug 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)

2020-08-09 Thread Juan Pablo

I have a very similar problem, today I asked a question on ask ubuntu


https://askubuntu.com/questions/1265779/video-issues-with-amd-igpu-and-nvidia-gpu-in-an-aspire-a715-41g-laptop

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

Title:
  [nvidia+amdgpu] System sometimes starts with a black screen with
  Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works
  perfectly)

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed Ubuntu on a laptop that has a Ryzen APU (with
  Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first
  issue that this kind of setup gives on a fresh install is that that
  PRIME render offloading doesn't work, I presume that Ubuntu currently
  sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia
  but that's another separate issue. As a workaround I created an Xorg
  configuration (attached in this report) that sets up both GPUs (with
  the appropiate BusIDs), after such configuration is applied the system
  boots fine with AMD integrated graphics being used and the ability to
  switch to Nvidia with PRIME render off-loading.

  The problem comes when I try to use the computer the next day, then it
  gives me a black screen without having the ability to switch to a tty,
  the boot log doesn't throw any errors I just see a black screen after
  Xorg tries to start. I can make it work again by entering in recovery
  mode, logging into a root console and switching between "nvidia" and
  "on-demand" modes using prime-select (I set it up to "on-demand"
  profile after installing Ubuntu).

  For the moment I cannot provide any relevant logs since it's now
  working fine (and I don't remember seeing any errors on Xorg logs),
  also I don't really know where to look for this kind of issues.

  My system information:
  -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 
440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  -RAM: 8 GB
  -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4)
  -Xorg 1.20.8-2ubuntu2

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

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

[Desktop-packages] [Bug 1890908] Re: all the video could not be played on ubuntu Wayland environment

2020-08-09 Thread Daniel Letzeisen

Note that proprietary AMD drivers do not support "AMD A6-7310 APU with
AMD Radeon R4 Graphics" in modern versions of Ubuntu. So what exactly
did you install (please give a link) and why?

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

Title:
  all the video could not be played on ubuntu Wayland environment

Status in totem package in Ubuntu:
  New

Bug description:
  I recently installed amdgpu pro driver.it works perfectly than
  ordinary inbuild amd drivers in linux kernal.every video players
  including VLC media player and ubuntu video player could not play any
  videos!but they are able to work in Gnome,ubuntu,Ubuntu budgie
  environments.the problem is in ubuntu Wayland environment.ubuntu video
  player is unable to start in ubuntu Wayland  environment,VLC
  automatically closes without warning when i open any vido file.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 21:27:43 2020
  InstallationDate: Installed on 2020-06-20 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  LogAlsaMixer:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1890750] Re: Permission Denied when using SMB share as storage location

2020-08-09 Thread Michael Terry

Huh, that's odd. Looks like a permission error when downloading a
metadata file from the SMB server. I'm not sure if it couldn't read or
couldn't write, from that error message.

But I guess if it's transient... it's all good. If you see this again,
please re-open or file a new ticket.

Thanks for the report!

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

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

Title:
  Permission Denied when using SMB share as storage location

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  1. Ubuntu release

  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2. Package Version

  $ apt-cache policy deja-dup
  deja-dup:
Installed: 40.7-0ubuntu1
Candidate: 40.7-0ubuntu1
Version table:
   *** 40.7-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   40.6-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3.  What I expected to happen

  Configure an SMB share as the network location to save my backups.  I
  am using the same share that works with the Gnome File manager.

  4.  What happens instead:

  I get a permission denied error when trying to use a SMB share as the
  storage location.

  This share is mountable and read/writeable through the same path when
  accessing it with the Gnome File manager.  Its unclear from the error
  what causes the failure or what I should be doing differently. I set
  the path to smb://mycloudex2ultra.local/bkup/, the folder to deja-dup
  and enter the correct username, domain, and password in the pop up
  dialog.

  Running with DEJA_DUP_DEBUG=1 shows the path as

  DUPLICITY: . Args: /usr/bin/duplicity --include=/home/tomg/.cache
  /deja-dup/metadata --exclude=/home/tomg/Downloads
  --exclude=/home/tomg/.local/share/Trash --exclude=/home/tomg/.cache
  /deja-dup --exclude=/home/tomg/.cache --include=/home/tomg
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=/home/tomg/snap/*/*/.cache
  --exclude=/home/tomg/.var/app/*/cache --exclude=** --dry-run
  --volsize=25 / gio+smb://mycloudex2ultra.local/winston-bkup/deja-dup
  --verbosity=9 --archive-dir=/home/tomg/.cache/deja-dup --tempdir=/tmp
  --log-fd=26

  
  and reveals this error:

  DUPLICITY: DEBUG 1
  DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
  DUPLICITY: .   File "/usr/lib/python3/dist-packages/duplicity/backend.py", 
line 376, in inner_retry
  DUPLICITY: . return fn(self, *args)
  DUPLICITY: .   File "/usr/lib/python3/dist-packages/duplicity/backend.py", 
line 570, in get
  DUPLICITY: . self.backend._get(remote_filename, local_path)
  DUPLICITY: .   File 
"/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 150, in 
_get
  DUPLICITY: . self.__copy_file(source_file, target_file)
  DUPLICITY: .   File 
"/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 121, in 
__copy_file
  DUPLICITY: . source.copy(target,
  DUPLICITY: .  gi.repository.GLib.GError: g-io-error-quark: Permission denied 
(14)
  DUPLICITY: . 

  DUPLICITY: WARNING 1
  DUPLICITY: . Attempt 1 failed. Error: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1890750/+subscriptions

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

[Desktop-packages] [Bug 1817480] Re: Emacs color-theme package is gone from version 40.1

2020-08-09 Thread nowakd

Not sure if that should be a bug anymore. In Ubuntu 19 and 20 I have
started to use melpa which allows to install custom and safe color
themes.

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

Title:
  Emacs color-theme package is gone from version 40.1

Status in emacs-goodies-el package in Ubuntu:
  Confirmed

Bug description:
  It seems that color-theme and other packages are missing from between
  versions 40.1 and 36.3ubuntu1 which is breaking existing emacs
  customizations. Any chance these could be reverted back? or a
  different package could be provided?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs-goodies-el/+bug/1817480/+subscriptions

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

[Desktop-packages] [Bug 1873429] Re: Problem with printing in 20.04 version

2020-08-09 Thread apetrelli

I have a a similar problem, but under Kubuntu 20.04, with 19.10 it printed fine.
My model is Epson ET 2650.

This bug may be related:
https://bugzilla.redhat.com/show_bug.cgi?id=1818110

When adding a new printer directly in CUPS I see the following errors:

E [09/Aug/2020:22:46:39 +0200] copy_model: empty PPD file
E [09/Aug/2020:22:46:39 +0200] [Client 145] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://antonio@localhost:631/printers/EPSON_ET-2650_Series) from localhost.
E [09/Aug/2020:22:46:42 +0200] [CGI] Unable to create PPD file: Could not poll 
sufficient capability info from the printer 
(ipp://EPSON%20ET-2650%20Series._ipp._tcp.local/, 
ipp://EPSONE9D612.local:631/ipp/print) via IPP!
E [09/Aug/2020:22:46:42 +0200] copy_model: empty PPD file
E [09/Aug/2020:22:46:42 +0200] [Client 145] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://antonio@localhost:631/printers/EPSON_ET-2650_Series) from localhost.
E [09/Aug/2020:22:46:46 +0200] [CGI] Unable to create PPD file: Could not poll 
sufficient capability info from the printer 
(ipp://EPSON%20ET-2650%20Series._ipp._tcp.local/, 
ipp://EPSONE9D612.local:631/ipp/print) via IPP!
E [09/Aug/2020:22:46:46 +0200] copy_model: empty PPD file
E [09/Aug/2020:22:46:46 +0200] [Client 145] Returning IPP 
server-error-internal-error for CUPS-Add-Modify-Printer 
(ipp://antonio@localhost:631/printers/EPSON_ET-2650_Series) from localhost.


** Bug watch added: Red Hat Bugzilla #1818110
   https://bugzilla.redhat.com/show_bug.cgi?id=1818110

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

Title:
  Problem with printing in 20.04 version

Status in cups package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Desktop-packages] [Bug 1890935] Re: sudoku in ubuntu20.04 keeps crashing

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

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

Title:
  sudoku in ubuntu20.04 keeps crashing

Status in gnome-sudoku package in Ubuntu:
  New

Bug description:
  after playing for a few minutes, the sudoku puzzle in ubuntu 20.04
  frequently crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: sudoku (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
  CurrentDesktop: GNOME
  Date: Sun Aug  9 02:15:03 2020
  InstallationDate: Installed on 2016-01-26 (1656 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudoku
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890958] [NEW] exfat month modification time increasing by simple consulting with "properties"

2020-08-09 Thread Pierre Wilch

Public bug reported:

Ubuntu 20.04, every updates done.
Each time I insert the same SDXC (64 GB, exFAT) card in my PC and show the 
modification time of always the same file by right clicking on it and then 
selecting "properties" in nautilus I notice that the month modification time 
has increased with 1 month. And one year more when jumping from december to 
january.
So, after several times inserting this card, that video file made april 28th 
2020 shows now the modification time june 28th 2021, 14 months later.
The modification time is important. It must be hold right.

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

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

Title:
  exfat month modification time increasing by simple consulting with
  "properties"

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, every updates done.
  Each time I insert the same SDXC (64 GB, exFAT) card in my PC and show the 
modification time of always the same file by right clicking on it and then 
selecting "properties" in nautilus I notice that the month modification time 
has increased with 1 month. And one year more when jumping from december to 
january.
  So, after several times inserting this card, that video file made april 28th 
2020 shows now the modification time june 28th 2021, 14 months later.
  The modification time is important. It must be hold right.

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

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

[Desktop-packages] [Bug 1890957] Re: My Night Light doesn't work at all.

2020-08-09 Thread Marcin D

** Information type changed from Public to Public Security

** Information type changed from Public Security to Private Security

** Information type changed from Private Security to Public Security

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

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

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

[Desktop-packages] [Bug 1890957] [NEW] My Night Light doesn't work at all.

2020-08-09 Thread Marcin D

*** This bug is a security vulnerability ***

Private security bug reported:

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

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

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


** Tags: amd64 apport-bug focal

** Attachment added: "Zrzut ekranu z 2020-08-09 21-10-59.png"
   
https://bugs.launchpad.net/bugs/1890957/+attachment/5400204/+files/Zrzut%20ekranu%20z%202020-08-09%2021-10-59.png

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

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

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

[Desktop-packages] [Bug 1890956] [NEW] Mouse and keyboard stop working after suspend

2020-08-09 Thread Trevor Schauls

Public bug reported:

Description:Ubuntu 20.04.1 LTS
Release:20.04
dm3:
  Installed: 3.34.1-1ubuntu1
  Candidate: 3.34.1-1ubuntu1
  Version table:
 *** 3.34.1-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

Booting off of a live usb, the trackpad, external mouse, and internal
keyboard stop responding to input after suspend. On my updated install,
the laptop trackpad works, but the other two inputs do not after
suspend/wake. I can log in using the on screen keyboard. Unplugging the
mouse and plugging it in does not fix it. The inputs don't respond while
logged in either. Only a reboot fixes it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  9 14:00:59 2020
ExecutablePath: /usr/lib/gdm3/gdm-x-session
InstallationDate: Installed on 2020-06-20 (50 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Description changed:

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  dm3:
-   Installed: 3.34.1-1ubuntu1
-   Candidate: 3.34.1-1ubuntu1
-   Version table:
-  *** 3.34.1-1ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.34.1-1ubuntu1
+   Candidate: 3.34.1-1ubuntu1
+   Version table:
+  *** 3.34.1-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
- 
- Booting off of a live usb, the trackpad, external mouse, and internal 
keyboard stop responding to input. On my updated install, the laptop trackpad 
works, but the other two inputs do not. I can log in using the on screen 
keyboard. Unplugging the mouse and plugging it in does not fix it. The inputs 
don't respond while logged in either. Only a reboot fixes it.
+ Booting off of a live usb, the trackpad, external mouse, and internal
+ keyboard stop responding to input after suspend. On my updated install,
+ the laptop trackpad works, but the other two inputs do not after
+ suspend/wake. I can log in using the on screen keyboard. Unplugging the
+ mouse and plugging it in does not fix it. The inputs don't respond while
+ logged in either. Only a reboot fixes it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  9 14:00:59 2020
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2020-06-20 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
-  SHELL=/bin/bash
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  XDG_RUNTIME_DIR=
+  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Mouse and keyboard stop working after suspend

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  dm3:
    Installed: 3.34.1-1ubuntu1
    Candidate: 3.34.1-1ubuntu1
    Version table:
   *** 3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Booting off of a live usb, the trackpad, external mouse, and internal
  keyboard stop responding to input after suspend. On my updated
  install, the laptop trackpad works, but the other two inputs do not
  after suspend/wake. I can log in using the on screen keyboard.
  Unplugging the mouse and plugging it in does not fix it. The inputs
  don't respond while logged in either. Only a reboot fixes it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  9 14:00:59 2020
  ExecutablePath: /usr/lib/gdm3/gdm-x-session
  InstallationDate: Installed on 2020-06-20 (50 days ago)
  InstallationMedia: Ubuntu 20.04 LTS

[Desktop-packages] [Bug 1890935] Re: sudoku in ubuntu20.04 keeps crashing

2020-08-09 Thread sally

The ID of the uploaded sudoku crash file is:
1cf1f4b9-da64-11ea-b278-fa163e983629

I also attach the crash file


** Attachment added: "_usr_games_gnome-sudoku.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1890935/+attachment/5400199/+files/_usr_games_gnome-sudoku.1000.crash

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

Title:
  sudoku in ubuntu20.04 keeps crashing

Status in gnome-sudoku package in Ubuntu:
  Incomplete

Bug description:
  after playing for a few minutes, the sudoku puzzle in ubuntu 20.04
  frequently crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: sudoku (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
  CurrentDesktop: GNOME
  Date: Sun Aug  9 02:15:03 2020
  InstallationDate: Installed on 2016-01-26 (1656 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudoku
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1890954] [NEW] Gnome assigns java app's windows to Visual Studio Code even after I quit visual studio code

2020-08-09 Thread Seija Kijin

Public bug reported:

This happens after I close Visual Studio's windows while the PC is
stuttering loading and writing data to the HDD.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Aug  9 13:27:04 2020
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2020-07-06 (33 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-08-09 13-31-30.png"
   
https://bugs.launchpad.net/bugs/1890954/+attachment/5400195/+files/Screenshot%20from%202020-08-09%2013-31-30.png

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

Title:
  Gnome assigns java app's windows to Visual Studio Code even after I
  quit visual studio code

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This happens after I close Visual Studio's windows while the PC is
  stuttering loading and writing data to the HDD.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Aug  9 13:27:04 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-07-06 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1888425] Re: Ubuntu Freezy - Probably Gnome-Shell Bug

And I have got this headphones connected: https://www.pccomponentes.com
/krom-kyus-auriculares-gaming

I have installed PulseAudio to change the sound card which is providing
me the sound. For example, if I am playing DOTA 2, sometimes, the
operating system detect may Family 17h... sound card and I don't get the
sound in my headphones, for that I need to change in PulseAudio to
change the sound to the soundcard used in headphones.

It seems and ALSA audio bug.

A few months ago, I had got a similar problem with my external
microphone, when I was playing CS:GO, the system freeze, but only happen
when I am using an external microphone.

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

Title:
  Ubuntu Freezy - Probably Gnome-Shell Bug

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM.

  Ubuntu sometimes freezes and I can't do nothing. I need to reboot the
  system pressing reset button.

  Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game 
in Steam. 
  When I select one game and change to another selecting the other, Ubuntu 
freezes. But it doesn't happen always.

  I read that could be a problem with Ryzen CPUs, but I don't know.

  Sorry and thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 22:11:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-24 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1888425] Re: Ubuntu Freezy - Probably Gnome-Shell Bug

I was playing DOTA 2 in Steam when the bug appeared.

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

Title:
  Ubuntu Freezy - Probably Gnome-Shell Bug

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM.

  Ubuntu sometimes freezes and I can't do nothing. I need to reboot the
  system pressing reset button.

  Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game 
in Steam. 
  When I select one game and change to another selecting the other, Ubuntu 
freezes. But it doesn't happen always.

  I read that could be a problem with Ryzen CPUs, but I don't know.

  Sorry and thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 22:11:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-24 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1888425] Re: Ubuntu Freezy - Probably Gnome-Shell Bug

And here the other file attached.

Thanks.

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888425/+attachment/5400194/+files/lspcik.txt

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

Title:
  Ubuntu Freezy - Probably Gnome-Shell Bug

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM.

  Ubuntu sometimes freezes and I can't do nothing. I need to reboot the
  system pressing reset button.

  Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game 
in Steam. 
  When I select one game and change to another selecting the other, Ubuntu 
freezes. But it doesn't happen always.

  I read that could be a problem with Ryzen CPUs, but I don't know.

  Sorry and thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 22:11:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-24 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1888425] Re: Ubuntu Freezy - Probably Gnome-Shell Bug

Hi again,
My PC has frozen again, I give you the logs to fix it after restart the PC.


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888425/+attachment/5400193/+files/prevboot.txt

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

Title:
  Ubuntu Freezy - Probably Gnome-Shell Bug

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have got a Ryzen 7 2700X, Nvidia GTX 1080 Ti and 16 GB RAM.

  Ubuntu sometimes freezes and I can't do nothing. I need to reboot the
  system pressing reset button.

  Usually Ubuntu (I think that Gnome-shell) freezes when I am selecting a game 
in Steam. 
  When I select one game and change to another selecting the other, Ubuntu 
freezes. But it doesn't happen always.

  I read that could be a problem with Ryzen CPUs, but I don't know.

  Sorry and thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  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.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 22:11:08 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-24 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment

2020-08-09 Thread Kenneth Zadeck

One more comment: atril works just fine and is a perfectly good work
around.

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

Title:
  Opening a pdf from Zotero in evince, I got "failed to load backend for
  'application/pdf': libnss3.so: failed to load shared object mapping
  segment

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Opening a pdf file from Zotero in evince, I got "failed to load
  backend for 'application/pdf': libnss3.so: failed to load shared
  object mapping segment" and the file won't open. When opening the file
  from its location in Nautilus, that works properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 10:17:17 2020
  InstallationDate: Installed on 2019-02-21 (398 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago)

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

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

[Desktop-packages] [Bug 1876219] Re: iris driver for old cpu

2020-08-09 Thread K van Murfi

Same problem here (Ubuntu 20.04, i915 driver, Skylake Intel(R) Core(TM) 
i7-6500U CPU @ 2.50GHz
) :
- glxgears and vlc both give a black window
- /usr/bin/kcmshell5 kcm_networkmanagementreturns a segfault.

'export MESA_LOADER_DRIVER_OVERRIDE=i965' seems to solve all this. Many
thanks to Chenxi Wu  for this trick.

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

Title:
  iris driver for old cpu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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

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

[Desktop-packages] [Bug 1890750] Re: Permission Denied when using SMB share as storage location

2020-08-09 Thread Tom Georgoulias

A recent update resolved this issue, but I'm not sure which package
corrected it.  I applied them all in a batch and noticed later that the
backups started working again.

Feel free to close this.

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

Title:
  Permission Denied when using SMB share as storage location

Status in deja-dup package in Ubuntu:
  New

Bug description:
  1. Ubuntu release

  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  2. Package Version

  $ apt-cache policy deja-dup
  deja-dup:
Installed: 40.7-0ubuntu1
Candidate: 40.7-0ubuntu1
Version table:
   *** 40.7-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   40.6-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3.  What I expected to happen

  Configure an SMB share as the network location to save my backups.  I
  am using the same share that works with the Gnome File manager.

  4.  What happens instead:

  I get a permission denied error when trying to use a SMB share as the
  storage location.

  This share is mountable and read/writeable through the same path when
  accessing it with the Gnome File manager.  Its unclear from the error
  what causes the failure or what I should be doing differently. I set
  the path to smb://mycloudex2ultra.local/bkup/, the folder to deja-dup
  and enter the correct username, domain, and password in the pop up
  dialog.

  Running with DEJA_DUP_DEBUG=1 shows the path as

  DUPLICITY: . Args: /usr/bin/duplicity --include=/home/tomg/.cache
  /deja-dup/metadata --exclude=/home/tomg/Downloads
  --exclude=/home/tomg/.local/share/Trash --exclude=/home/tomg/.cache
  /deja-dup --exclude=/home/tomg/.cache --include=/home/tomg
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=/home/tomg/snap/*/*/.cache
  --exclude=/home/tomg/.var/app/*/cache --exclude=** --dry-run
  --volsize=25 / gio+smb://mycloudex2ultra.local/winston-bkup/deja-dup
  --verbosity=9 --archive-dir=/home/tomg/.cache/deja-dup --tempdir=/tmp
  --log-fd=26

  
  and reveals this error:

  DUPLICITY: DEBUG 1
  DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
  DUPLICITY: .   File "/usr/lib/python3/dist-packages/duplicity/backend.py", 
line 376, in inner_retry
  DUPLICITY: . return fn(self, *args)
  DUPLICITY: .   File "/usr/lib/python3/dist-packages/duplicity/backend.py", 
line 570, in get
  DUPLICITY: . self.backend._get(remote_filename, local_path)
  DUPLICITY: .   File 
"/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 150, in 
_get
  DUPLICITY: . self.__copy_file(source_file, target_file)
  DUPLICITY: .   File 
"/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 121, in 
__copy_file
  DUPLICITY: . source.copy(target,
  DUPLICITY: .  gi.repository.GLib.GError: g-io-error-quark: Permission denied 
(14)
  DUPLICITY: . 

  DUPLICITY: WARNING 1
  DUPLICITY: . Attempt 1 failed. Error: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1890750/+subscriptions

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

[Desktop-packages] [Bug 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment

2020-08-09 Thread Kenneth Zadeck

I have the same (or at least a very similar) problem.On a fully up
to date xubuntu 20-04 system, when i run evince and click on a link, it
fails to follow that link in my browser.This kind of thing happens
when you are reading a technical paper and want to follow one of the
references and click on the doi or url.

When i click on the link i get a box that i cannot copy from that says:
Failed to launch preferred application for category "WebBrowser".

Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-2
/exo-helper-2"(Permission denied).

Did I say that it is annoying that i could not copy the text in this
box!!

The output of the ldd command you asked for is attached.

I should also point out that this worked fine under xubuntu 18.04.


** Attachment added: "the output of  ldd -r `which evince` that you asked for."
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+attachment/5400167/+files/xx

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

Title:
  Opening a pdf from Zotero in evince, I got "failed to load backend for
  'application/pdf': libnss3.so: failed to load shared object mapping
  segment

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Opening a pdf file from Zotero in evince, I got "failed to load
  backend for 'application/pdf': libnss3.so: failed to load shared
  object mapping segment" and the file won't open. When opening the file
  from its location in Nautilus, that works properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 10:17:17 2020
  InstallationDate: Installed on 2019-02-21 (398 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago)

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

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

[Desktop-packages] [Bug 1460032] Re: sudoku crashes

** Package changed: sudoku (Ubuntu) => gnome-sudoku (Ubuntu)

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

Title:
  sudoku crashes

Status in gnome-sudoku package in Ubuntu:
  Incomplete

Bug description:
  sudoku frequently crashes after several minutes in ubuntu 15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: sudoku (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri May 29 03:54:20 2015
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudoku
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (35 days ago)

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

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

[Desktop-packages] [Bug 1890935] Re: sudoku in ubuntu20.04 keeps crashing

(see bug 1326343)

** Package changed: sudoku (Ubuntu) => gnome-sudoku (Ubuntu)

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

Title:
  sudoku in ubuntu20.04 keeps crashing

Status in gnome-sudoku package in Ubuntu:
  Incomplete

Bug description:
  after playing for a few minutes, the sudoku puzzle in ubuntu 20.04
  frequently crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: sudoku (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
  CurrentDesktop: GNOME
  Date: Sun Aug  9 02:15:03 2020
  InstallationDate: Installed on 2016-01-26 (1656 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudoku
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1460032] [NEW] sudoku crashes

You have been subscribed to a public bug:

sudoku frequently crashes after several minutes in ubuntu 15.04

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: sudoku (not installed)
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: i386
CurrentDesktop: Unity
Date: Fri May 29 03:54:20 2015
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sudoku
UpgradeStatus: Upgraded to vivid on 2015-04-23 (35 days ago)

** Affects: gnome-sudoku (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: apport-bug i386 vivid
-- 
sudoku crashes
https://bugs.launchpad.net/bugs/1460032
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-sudoku in Ubuntu.

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

[Desktop-packages] [Bug 1890935] [NEW] sudoku in ubuntu20.04 keeps crashing

You have been subscribed to a public bug:

after playing for a few minutes, the sudoku puzzle in ubuntu 20.04
frequently crashes

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: sudoku (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
CurrentDesktop: GNOME
Date: Sun Aug  9 02:15:03 2020
InstallationDate: Installed on 2016-01-26 (1656 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sudoku
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-sudoku (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal
-- 
sudoku in ubuntu20.04 keeps crashing
https://bugs.launchpad.net/bugs/1890935
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-sudoku in Ubuntu.

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

[Desktop-packages] [Bug 1890939] [NEW] [snap] The SUID sandbox helper binary was found, but is not configured correctly.

2020-08-09 Thread Alex Muntada

Public bug reported:

The chromium snap version 1260 has the wrong mode for chrome-sandbox, as
it happened also in bug #1854091:

```
$ /snap/bin/chromium
[4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID 
sandbox helper binary was found, but is not configured correctly. Rather than 
run without sandboxing I'm aborting now. You need to make sure that 
/snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root 
and has mode 4755.
Trace/breakpoint trap
$ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe 
(32)
```

I have reverted it to the previous version (1244) and this one works
(and has the right mode for chromium-sandbox).

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


** Tags: snap

** Tags added: snap

** Summary changed:

- The SUID sandbox helper binary was found, but is not configured correctly.
+ [snap] The SUID sandbox helper binary was found, but is not configured 
correctly.

** Description changed:

  The chromium snap version 1260 has the wrong mode for chrome-sandbox, as
- it happened also in bug #1854091):
- 
+ it happened also in bug #1854091:
  
  ```
  $ /snap/bin/chromium
  [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID 
sandbox helper binary was found, but is not configured correctly. Rather than 
run without sandboxing I'm aborting now. You need to make sure that 
/snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root 
and has mode 4755.
  Trace/breakpoint trap
  $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken 
pipe (32)
  ```
  
  I have reverted it to the previous version (1244) and this one works
  (and has the right mode for chromium-sandbox).

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

Title:
  [snap] The SUID sandbox helper binary was found, but is not configured
  correctly.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The chromium snap version 1260 has the wrong mode for chrome-sandbox,
  as it happened also in bug #1854091:

  ```
  $ /snap/bin/chromium
  [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID 
sandbox helper binary was found, but is not configured correctly. Rather than 
run without sandboxing I'm aborting now. You need to make sure that 
/snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root 
and has mode 4755.
  Trace/breakpoint trap
  $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken 
pipe (32)
  ```

  I have reverted it to the previous version (1244) and this one works
  (and has the right mode for chromium-sandbox).

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

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

[Desktop-packages] [Bug 1875124] Re: Lock screen hangs after entering password

2020-08-09 Thread Efthimios Chaskaris

I think I have a workaround, if the problem is the same as the one I'm
facing. Press the user button on the bottom right where you enter your
password, the lock screen changes colors , re enter the password and
login will be successful.

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

Title:
  Lock screen hangs after entering password

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Running the newest release of ubuntu (20.04LTS).

  I entered my password to log in after the lock screen had engaged
  automatically and it accepted my password (greying out the buttons)
  but didn't log in.

  Five minutes later it still hadn't changed so I went to another TTY
  and killed the gnome-terminal process. X started up again, and allowed
  me to log in with no issues after that.

  Intentionally locking the screen did not trigger the bug.

  This could be a serious problem for anyone not already familiar with
  linux as this would force a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 20:28:57 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1875124] Re: Lock screen hangs after entering password