[Desktop-packages] [Bug 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake

[Tessa]

and here's another new wrinkle... it looks like after my machine has
been put to sleep and woken up a few times, it now creates a new dummy
audio device each time, until my system is full of dummy audio devices.

seriously what is up with sleep/wake and pulse in ubuntu 20.04??

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

Title:
  pulseaudio has is buggy with hdmi audio and sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Desktop-packages] [Bug 1891712] Re: nautilus takes ages to start up when not already running

[Tessa]

ok well, this is exceptionally weird. I was seeing some issues with my
wine install where the internal state was all messed up and it was just
hanging starting apps and so I blew it away and rebuilt it, and now
I can't reproduce this nautilus issue.

Is there any connection between nautilus and wine? I can't think of why
that would be, but here we are, and I'm very confused.

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

Title:
  nautilus takes ages to start up when not already running

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I'm filing this bug separately because it appears to be distinct from
  #1063282, but the root cause may be similar.

  when I start nautilus and it's not already running, it can take an
  extremely long time to start, up to even 2m before a file browser
  appears. as well, opening certainly locations (like the trash, or
  network shares) can also take another huge span of time before they
  complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-lowlatency 5.4.44
  Uname: Linux 5.4.0-42-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:21:04 2020
  InstallationDate: Installed on 2020-07-15 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1892136] [NEW] reverse prime produces corrupted output on specific resolutions

[Aleksander Miera]

Public bug reported:

The issue has initially been discovered for resolution 1366x768 on a
DisplayLink (evdi)-backed device, but applies also to UDL, as well as
reverse prime setups (rendering on Intel, output through NVidia).

The issue manifests with 1366x768 and several other resolutions only,
due to the fact that the GPU seems to use 64-aligned framebuffer stride.
This is "accidentally" fine with the most popular VGA resolutions (e.g.
assuming 32bits/4bytes per pixel and FullHD, the stride would be 1920*4
-> 7680, which is divisible by 64 w/o a remainder, yet 1366*4=5464,
5464/64 = 85.375). The proposed fix is to update the stride with the
GPU-provided value instead of the Xorg-calculated one at the stage of
sharing the pixmap between GPUs. Doing that at earlier stage would
probably require distinguishing between allocation of a FB and a generic
pixmap, which is the same for Xorg.

Issue for sure was seen on 18.04 and 19.04, probably still there for
20.04.

Upstream report:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/889

And posted (not yet integrated) fix:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496

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

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

Title:
  reverse prime produces corrupted output on specific resolutions

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The issue has initially been discovered for resolution 1366x768 on a
  DisplayLink (evdi)-backed device, but applies also to UDL, as well as
  reverse prime setups (rendering on Intel, output through NVidia).

  The issue manifests with 1366x768 and several other resolutions only,
  due to the fact that the GPU seems to use 64-aligned framebuffer
  stride. This is "accidentally" fine with the most popular VGA
  resolutions (e.g. assuming 32bits/4bytes per pixel and FullHD, the
  stride would be 1920*4 -> 7680, which is divisible by 64 w/o a
  remainder, yet 1366*4=5464, 5464/64 = 85.375). The proposed fix is to
  update the stride with the GPU-provided value instead of the Xorg-
  calculated one at the stage of sharing the pixmap between GPUs. Doing
  that at earlier stage would probably require distinguishing between
  allocation of a FB and a generic pixmap, which is the same for Xorg.

  Issue for sure was seen on 18.04 and 19.04, probably still there for
  20.04.

  Upstream report:
  https://gitlab.freedesktop.org/xorg/xserver/-/issues/889

  And posted (not yet integrated) fix:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496

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

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

[Desktop-packages] [Bug 1892133] [NEW] cursor flickers/disappears and windows resize or move randomly

[Barmak Nassirian]

Public bug reported:

Ubuntu 20.04 natively installed on 2013 Google Pixel Chromebook (i.e.,
it is the only OS on machine)

Installation went fine, but after a few minutes of use, the cursor
begins to act up--flickering and sometimes disappearing altogether. Even
more problematic: Firefox windows resize on their own or move. Sometime
moving the cursor moves the resized windows (as if I am clicking and
holding the menu bar) and sometimes not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 75.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  barmak 1859 F pulseaudio
BuildID: 20200403170909
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 19 01:44:02 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
DefaultProfileThemes: extensions.sqlite corrupt or missing
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
InstallationDate: Installed on 2020-08-19 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
 default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp3s0 scope link metric 1000 
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.237 metric 600
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=75.0/20200403170909 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2020
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.12
dmi.board.name: Link
dmi.board.vendor: GOOGLE
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.12:bd06/04/2020:svnGOOGLE:pnLink:pvr1.0:rvnGOOGLE:rnLink:rvr1.0:cvnGOOGLE:ct9:cvr:
dmi.product.name: Link
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

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


** Tags: amd64 apport-bug focal

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

Title:
  cursor flickers/disappears and windows resize or move randomly

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 natively installed on 2013 Google Pixel Chromebook (i.e.,
  it is the only OS on machine)

  Installation went fine, but after a few minutes of use, the cursor
  begins to act up--flickering and sometimes disappearing altogether.
  Even more problematic: Firefox windows resize on their own or move.
  Sometime moving the cursor moves the resized windows (as if I am
  clicking and holding the menu bar) and sometimes not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 75.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  barmak 1859 F pulseaudio
  BuildID: 20200403170909
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 19 01:44:02 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:733
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-08-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric

[Desktop-packages] [Bug 1591323] Re: No low battery notification, shutdown without warning

[Launchpad Bug Tracker]

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

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

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

Title:
  No low battery notification, shutdown without warning

Status in gnome-power-manager package in Ubuntu:
  Expired

Bug description:
  After upgrading to ubuntu 16.04 system no longer notifies about low
  battery and performs shutdown without warning.

  And behaviour is not even by org.gnome.settings-daemon.plugins.power.*
  settings.

  time_policy is false, which should use percentage, but this is not
  case.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: notify-osd 0.9.35+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 10 20:37:26 2016
  DesktopSession: 'ubuntu'
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2015-03-17 (451 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUSTeK COMPUTER INC. G551JM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=6b3d8536-3be5-44ce-9d55-0e9d910dd18e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+13ubuntu3
   libgl1-mesa-glx  11.2.0-1ubuntu2
   libdrm2  2.4.67-1ubuntu0.16.04.1
   xserver-xorg-video-intel N/A
   xserver-xorg-video-ati   N/A
  SourcePackage: notify-osd
  UpgradeStatus: Upgraded to xenial on 2016-04-12 (59 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G551JM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG551JM.204:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnG551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G551JM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1883516] Re: display is freezing randomly

[Launchpad Bug Tracker]

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

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

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

Title:
  display is freezing randomly

Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  My display is freezing randomly, while the system seems to be running,
  since music is playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:58:54 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:505f]
  InstallationDate: Installed on 2020-04-24 (51 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20J5S00C00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=47fb22f8-4f7e-4824-80f7-5db5105765e0 ro intel_idle.max_cstate=1 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0GET63W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J5S00C00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0GET63W(1.63):bd02/24/2018:svnLENOVO:pn20J5S00C00:pvrThinkPadL470:rvnLENOVO:rn20J5S00C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L470
  dmi.product.name: 20J5S00C00
  dmi.product.sku: LENOVO_MT_20J5_BU_Think_FM_ThinkPad L470
  dmi.product.version: ThinkPad L470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1883516] Re: display is freezing randomly

[Launchpad Bug Tracker]

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

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

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

Title:
  display is freezing randomly

Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  My display is freezing randomly, while the system seems to be running,
  since music is playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:58:54 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:505f]
  InstallationDate: Installed on 2020-04-24 (51 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20J5S00C00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=47fb22f8-4f7e-4824-80f7-5db5105765e0 ro intel_idle.max_cstate=1 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0GET63W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J5S00C00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0GET63W(1.63):bd02/24/2018:svnLENOVO:pn20J5S00C00:pvrThinkPadL470:rvnLENOVO:rn20J5S00C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L470
  dmi.product.name: 20J5S00C00
  dmi.product.sku: LENOVO_MT_20J5_BU_Think_FM_ThinkPad L470
  dmi.product.version: ThinkPad L470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1884201] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  when I'm trying to install chromium, it said that snap changes are in
  progress and that's why the installation process can't go through. so
  i aborted all snap changes and then tried installation. Though the app
  was installed it said that it couldn't find the following directory
  "user/share/appdata".

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun 19 12:23:01 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-06-17 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Anthony Wong]

** Tags added: originate-from-1887127 originate-from-1887878 sutton

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
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:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

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

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

[Desktop-packages] [Bug 1892031] Re: Xorg crash

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Changed in: xorg-server (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/1892031

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  One day ago it crashed during using it and restarted by itself. Today
  when I started my computer it began to flash black

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 18 15:15:40 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094]
 Subsystem: Acer Incorporated [ALI] Device [1025:1094]
  InstallationDate: Installed on 2019-09-15 (337 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b571 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8d196740-0a4f-4a2b-ab15-be5c76196c92 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd08/02/2016:svnAcer:pnAspireE5-575G:pvrV1.12:rvnAcer:rnIronman_SK:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-575G
  dmi.product.sku: Aspire E5-575G_115F_1.12
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1888085] Re: Fehler : Ubuntu 18.04.4 LTS

[Daniel van Vugt]

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

This is another duplicate of bug 1773859.

** This bug has been marked a duplicate of bug 1773859
   Upgrades to 18.04 fail due to systemd-shim

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

Title:
  Fehler : Ubuntu 18.04.4 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  Fehler : Ubuntu 18.04.4 LTS

  
  Details
  Do you want to start the upgrade?

  1 package is going to be removed

  To prevent data loss close all open applications and  documents

  
  Details: Remove (1)  systemd-shim-shim for systemd

  
  Could not install 'systemd-shim'

  The upgrade will continue but the 'systemd-shim' package may not be in
  a working state. Please consider submitting a bug report about it.

  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  Could not install the upgrades

  
  The upgrade has aborted. Your system could be in an unusable state. A 
recovery will run now (dpkg --configure -a).

  
  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 18 23:15:19 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
  InstallationDate: Installed on 2020-07-17 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-78LMT-USB3 R2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: sex
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 R2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jul 18 01:11:31 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input  USB Keyboard   KEYBOARD, id 8
   input  USB Keyboard   KEYBOARD, id 9
   inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1892107] Re: NETWORK IS BEAKING THE OS

[Daniel van Vugt]

We can keep this bug about your networking (wifi?) problems.

Although looking at your kernel log there appears to be a separate
issue: Your 'SanDisk SSD PLUS 120GB' is experiencing hardware faults
which may indeed break the OS. That problem is not related to
networking. I suggest you try replacing the 'SanDisk SSD PLUS 120GB' or
just unplug it if you don't need it. Hopefully the problem is just that
drive and not the motherboard. But again, your disk problem is separate
and unrelated to wifi problems.

** Package changed: xorg (Ubuntu) => bcmwl (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/1892107

Title:
  NETWORK IS BEAKING THE OS

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Hello, my Uuntu 20.04 has a problem, I've formatted it countless times
  and this error always occurs.

  I'm doing something, the system simply informs that there is no
  internet, and it really runs out of internet and if I try to connect
  in my hand, it simply locks the entire system, leaving the fan
  running.

  I use Ubuntu, as my computer is a Macbook pro 2012 and will no longer
  receive a system update.

  Macbook pro 13" i7 mid 2012 original network card.

  
  From what I noticed, it looks like a loop is occurring, but I couldn't get 
any more details due to the crash.

  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
  NonfreeKernelModules: wl
  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: Tue Aug 18 20:37:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fa]
  InstallationDate: Installed on 2020-07-16 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Apple Inc. MacBookPro9,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=b1280c6f-f86c-494d-b8f0-1ceed5d31914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 233.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvr233.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2020-08-18T20:29:26.081990
  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/bcmwl/+bug/1892107/+subscriptions

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

[Desktop-packages] [Bug 1892094] Re: Nvidia Desktop Brightness Reset on Blank Screen

[Daniel van Vugt]

I doubt GNOME has any intention to support this use case, but in case
I'm wrong please:

1. Verify the bug still happens in Ubuntu 20.04 and

2. Report the bug upstream at:
https://gitlab.gnome.org/GNOME/mutter/issues

** Tags added: bionic

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

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Nvidia Desktop Brightness Reset on Blank Screen
+ Xrandr brightness and gamma settings not remembered on power resume

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

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Xrandr brightness and gamma settings not remembered on power resume

Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Incomplete

Bug description:
  Brightness Reset to Maximum on Nvidia GPU Desktop when setting on
  Blank Screen

  The Desktop LED Monitor brightness or Gamma level is not preserved and
  reset when I set gnome-control-center setting on Power to Blank
  Screen.

  I try to post as much details as possible.

  -I did a test by setting Nvidia X Server Color Correction and set any
  brightness and gamma.It get reset when Power Saving Blank Screen time
  active which I had set 10 minutes to save power by auto turning off
  the display.

  -The second test was by installing a Brightness Controller which use
  Xrandr but same result of getting reset when I set Blank Screen.I also
  manually set xrandr --output DVI-D-0 –brightness 0.5 --gamma
  0.5:0.5:0.5 an value get reset after the trigger from blank screen.

  -Third test by selecting Nouveau open source but same result of
  getting reset when I set Blank Screen.

  -Forth test ,  manually turn off the monitor ‘xset dpms force off’ it
  doesn’t trigger the brightness reset.

  Since the system is using Desktop GPU , the folder on xblacklight is
  empty without config files.

  The flow 
  > Set brightness >  Power Saving Blank Screen time active > Brightness reset 
> External Monitor dim and Turn Off > Press any keyboard button to wakeup the 
display > Brightness Stay at reset value of Full 100% brightness.

  The details I had tested , I suspect gsd-power may have related to this 
issue.This is happen before which I had find a solution to other brightness 
reset happen when every restart , delete a files upon restart , open a web 
browser with and play a video stream, login and logout , suspend and Power 
Saving Blank Screen.
  All of this are affected by gsd-color.Which I had found a link a fix 
suggestion
  https://github.com/LordAmit/Brightness/issues/102#issuecomment-374253884 by 
disable  /usr/lib/gnome-settings-daemon/gsd-color on startup.

  The only left is Power Saving Blank Screen still get reset when it get 
active.I am not too sure whether it is related to gsd-power , I did disable it 
but it also disable Power Saving Blank Screen together.
  It just goes to screensaver mode and did not turn off the monitor.

  I do not have any basic on gsd-power code
  https://gitlab.gnome.org/starnight/gnome-settings-
  daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power
  /gsd-power-manager.c Not knowing which line did it callback and get
  reset , presumably ‘GSD_POWER_IDLE_MODE_BLANK’ ?

  Fresh Install

  OS : Ubuntu 18.04.4
  Architecture: amd64 
  Nvidia : GTX 1050
  Driver : NVIDIA Driver Version: 440.100
  uname : 5.4.0-42-generic
  DisplayManager: gdm3

  Journalctl log when blank screen active.

  nvidia-settings[19556]: PRIME: is it supported? no
  nvidia-settings[19556]: PRIME: No offloading required. Abort
  nvidia-settings[19556]: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed
  Check that logind is properly installed and pam_systemd is getting used at 
login.
  gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.
  gnome-screensav[1551]: Source ID 19140 was not found when attempting to 
remove it
  gnome-session-binary[1521]: WARNING: Could not get session path for session. 
Check that logind is properly installed and pam_systemd is getting used at 
login.
  gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get 
session path for session. Check that logind is properly installed and 
pam_systemd is getting used at login.

  Reading the log shows somewhere it trigger brightness reset.The Nvidia
  Setting prime message is show because I am using a desktop dedicated
  GPU without using nvidia prime for 

[Desktop-packages] [Bug 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

[Daniel van Vugt]

Those are different profiles "ldac" and "sbc", so are actually different
bugs to this. I suggest logging those as new bugs after 5.8.0 becomes
the standard kernel in groovy (soon). If they are bugs at all (ie. you
are sure your headphones support LDAC and SBC).


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

** No longer affects: bluez (Ubuntu)

** Tags added: a2dp

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

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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

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

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

[Daniel van Vugt]

Indeed, if you prefer long term stability then you should stay on 20.04.

We will be backporting some performance fixes to 20.04 as soon as it is
safe to do so. In fact a couple are coming in mutter 3.36.4 and another
in 3.36.5...

If you want to make 4K significantly faster on 20.04 in a safe way right
now, then I recommend forcing it to use the old Intel driver which is
better at frequency scaling. Just edit /etc/environment and add a new
line:

  MESA_LOADER_DRIVER_OVERRIDE=i965

and then reboot.

-- 
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 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures

[Daniel van Vugt]

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

** Tags removed: eoan
** Tags added: fixed-in-81 fixed-upstream

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
  scrolling with touchpad and touch gestures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

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

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

[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures

[Bug Watch Updater]

** Changed in: firefox
   Status: Confirmed => Fix Released

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
  scrolling with touchpad and touch gestures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

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

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

[Desktop-packages] [Bug 1551949]

[Gerard]

Yes, please; let's get back to the core issue. The Firefox print
function does not save functioning hyperlinks when the output is PDF. I
dislike having to switch to Chromium (I use Linux) to create a PDF with
functioning hyperlinks. Can we please get Firefox to create a PDF with
hyperlinks that work? As far as I'm concerned, it can be under either
the 'Save Page As ...' menu item or the 'Print ...' menu item this bug
was opened under. Thanks!

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

Title:
  Printing to PDF file loses URLs/links

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. File -> Print...
  2. Select "Print to File".
  3. Enter the file name.
  4. Enter the save-to folder.
  5. Leave the output format as-is, or select PDF if it's not the default.
  6. Hit the Print button.
  7. Open the resulting PDF in any PDF viewer.

  
  Actual results:

  The URLs within the document are not actually hyperlinks.  They are
  simply text, coloured blue and underlined.

  
  Expected results:

  Any clickable links on the original e-mail message should be retained
  when converting the document to PDF format.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: thunderbird 1:38.5.1+build2-0ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colan  2383 F pulseaudio
   /dev/snd/controlC0:  colan  2383 F pulseaudio
  BuildID: 20160106101030
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Mar  1 15:53:53 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.140  
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1abc004a-043e-4a15-bdc0-45ade2150908
  Plugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  Profiles: Profile0 (Default) - LastVersion=38.5.1/20160106101030 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   rhythmbox-mozilla 3.2.1-1ubuntu3.1
   adobe-flashplugin 1:20160209.1-0ubuntu0.15.10.1
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-1abc004a-043e-4a15-bdc0-45ade2150908
   bp-c8c94f9f-0c39-42d2-97ac-f2c7d2150713
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to wily on 2015-11-30 (92 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Desktop-packages] [Bug 1697122]

[Pulsebot]

Pushed by abutkov...@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6c7f2177e485
[Linux] Enable XInput2 on Gtk 3.24 and newer, r=botond

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
  scrolling with touchpad and touch gestures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

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

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

[Desktop-packages] [Bug 1697122]

[Apavel-2]

https://hg.mozilla.org/mozilla-central/rev/6c7f2177e485

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
  scrolling with touchpad and touch gestures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

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

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

[Desktop-packages] [Bug 1697122]

[Stransky]

Created attachment 9169828
Bug 1207700 [Linux] Enable XInput2 on Gtk 3.24 and newer, r?botond

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
  scrolling with touchpad and touch gestures

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version:  Kubuntu 17.04
  Firefox version: 53.0.3+build1-0ubuntu0.17.04.2

  In Firefox, two-finger scroll gestures on a touchpad are interpreted
  as scroll wheel rotations, and the content scrolls three lines at a
  time. This is inappropriate behavior for touchpad scrolling; it should
  scroll pixel-by-pixel.

  Firefox already has the ability to do this, you just need to turn it
  on by running the program with MOZ_USE_XINPUT2=1 in the environment:
  for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to
  /etc/environment or something like that.

  Turning on this behavior yields a large usability improvement for
  laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be
  permanently added to the packaging such that it's always present when
  Firefox runs. This is what Fedora does, and it results in a much
  improved experience for the laptop user.

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

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

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

[daleli]

This bug affects me a lot. I visit this page everyday to see whether if
someone fix it. :(

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  Apport

[Desktop-packages] [Bug 1801205] Re: Can't mount veracrypt volumes

[Daniel Jenkins]

Ubuntu 20.04 one of the main feature was to mount Veracrypt volumes with
Gnome disk... Mmm... 2 years later and noup.

Tails had solve this since that time.

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

Title:
  Can't mount veracrypt volumes

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Using mount from nautilus (open with) or right from Gnome Disk, the
  file in question is "mounted" as a loop device. Therefore, no opening
  of that container nor questions about how to open the file.

  This is Ubuntu 18.10 from 18.04. Already tried 18.10 on a VM (Live
  session) and Gnome on Xorg & Wayland.

  Also tryed Tail in order to see the Veracrypt property working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-disk-utility 3.30.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov  1 18:35:17 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-08 (146 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to cosmic on 2018-10-30 (2 days ago)

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

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

[Desktop-packages] [Bug 1878515] Re: Encoding issue when translating locale modifiers

[Gunnar Hjalmarsson]

** Changed in: gnome-desktop3 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Encoding issue when translating locale modifiers

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

Bug description:
  [Impact]

  When gettext translate locale modifiers, the output encoding is not
  set to UTF-8, so non-ascii letters are replaced with question marks. A
  fix has been committed upstream, and the proposed fix cherry picks
  that commit.

  [Test Case]

  * Install the Serbian language, switch to Serbian — Latin, and relogin

  * Open Settings -> Region & Language and find that the current
  language is not labeled correctly

  * Upgrade libgnome-desktop-3-19 and friends from focal-proposed

  * Open Settings -> Region & Language and find that the current
  language label is now correct

  [Regression Potential]

  Negligible

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

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

[Desktop-packages] [Bug 1892107] Re: NETWORK IS BEAKING THE OS

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  NETWORK IS BEAKING THE OS

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello, my Uuntu 20.04 has a problem, I've formatted it countless times
  and this error always occurs.

  I'm doing something, the system simply informs that there is no
  internet, and it really runs out of internet and if I try to connect
  in my hand, it simply locks the entire system, leaving the fan
  running.

  I use Ubuntu, as my computer is a Macbook pro 2012 and will no longer
  receive a system update.

  Macbook pro 13" i7 mid 2012 original network card.

  
  From what I noticed, it looks like a loop is occurring, but I couldn't get 
any more details due to the crash.

  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
  NonfreeKernelModules: wl
  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: Tue Aug 18 20:37:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fa]
  InstallationDate: Installed on 2020-07-16 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Apple Inc. MacBookPro9,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=b1280c6f-f86c-494d-b8f0-1ceed5d31914 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 233.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvr233.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2020-08-18T20:29:26.081990
  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/xorg/+bug/1892107/+subscriptions

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

[Desktop-packages] [Bug 1892108] Re: ping prints ip address octets backwards on host redirect

[Åge Strand]

Possible culprit might be the pr_icmph function in ping.c, lines 1250 -
1259:

{
struct sockaddr_in sin = {
.sin_family = AF_INET,
.sin_addr =  {
icp ? icp->un.gateway : info
}
};

printf(_("(New nexthop: %s)\n"), pr_addr(&sin, sizeof 
sin));
}

Are you sure the variables used for .sin_addr input are guaranteed to be
in network byte order?

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

Title:
  ping prints ip address octets backwards on host redirect

Status in iputils package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Just noticed a weird thing with ping on Ubuntu 20.04, which I recently
  updated to.

  This is what I get when pinging a host on my network:

  user@ubuntu2004:~$ ping 10.156.0.63
  PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data.
  From 10.15.0.1 icmp_seq=2 Redirect Host(New nexthop: 2.0.15.10)

  The ubuntu2004 machine is located in the 10.15.0.x network.
  10.15.0.1 is a DSL router.
  10.15.0.2 is a firewall between multiple networks.
  10.156.0.63 is a machine on a different local network.

  All traffic not destined for the internet is routed from 10.15.0.1 to
  10.15.0.2, so I would expect the printout to read "New nexthop:
  10.15.0.2".

  However, as you can see this is not the case. Instead the octets are
  printed in reverse order.

  To verify this I tried the same on another machine in the same
  network, running Ubuntu 18.04:

  user@ubuntu1804:~$ ping 10.156.0.63
  PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data.
  From 10.15.0.1: icmp_seq=2 Redirect Host(New nexthop: 10.15.0.2)

  As you can see, the printout is correct here: "New nexthop: 10.15.0.2"

  I further verified the discrepancy by using tcpdump to interpret the
  ICMP packets on the ubuntu2004 machine, and there seems to be no
  problem for tcpdump to display the correct IP address.

  My assumption is that there is something wrong in the print function
  which displays the IP address for a host redirect.

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

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

[Desktop-packages] [Bug 1892108] [NEW] ping prints ip address octets backwards on host redirect

[Åge Strand]

Public bug reported:

Description:Ubuntu 20.04.1 LTS
Release:20.04

Just noticed a weird thing with ping on Ubuntu 20.04, which I recently
updated to.

This is what I get when pinging a host on my network:

user@ubuntu2004:~$ ping 10.156.0.63
PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data.
>From 10.15.0.1 icmp_seq=2 Redirect Host(New nexthop: 2.0.15.10)

The ubuntu2004 machine is located in the 10.15.0.x network.
10.15.0.1 is a DSL router.
10.15.0.2 is a firewall between multiple networks.
10.156.0.63 is a machine on a different local network.

All traffic not destined for the internet is routed from 10.15.0.1 to
10.15.0.2, so I would expect the printout to read "New nexthop:
10.15.0.2".

However, as you can see this is not the case. Instead the octets are
printed in reverse order.

To verify this I tried the same on another machine in the same network,
running Ubuntu 18.04:

user@ubuntu1804:~$ ping 10.156.0.63
PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data.
>From 10.15.0.1: icmp_seq=2 Redirect Host(New nexthop: 10.15.0.2)

As you can see, the printout is correct here: "New nexthop: 10.15.0.2"

I further verified the discrepancy by using tcpdump to interpret the
ICMP packets on the ubuntu2004 machine, and there seems to be no problem
for tcpdump to display the correct IP address.

My assumption is that there is something wrong in the print function
which displays the IP address for a host redirect.

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

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

Title:
  ping prints ip address octets backwards on host redirect

Status in iputils package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Just noticed a weird thing with ping on Ubuntu 20.04, which I recently
  updated to.

  This is what I get when pinging a host on my network:

  user@ubuntu2004:~$ ping 10.156.0.63
  PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data.
  From 10.15.0.1 icmp_seq=2 Redirect Host(New nexthop: 2.0.15.10)

  The ubuntu2004 machine is located in the 10.15.0.x network.
  10.15.0.1 is a DSL router.
  10.15.0.2 is a firewall between multiple networks.
  10.156.0.63 is a machine on a different local network.

  All traffic not destined for the internet is routed from 10.15.0.1 to
  10.15.0.2, so I would expect the printout to read "New nexthop:
  10.15.0.2".

  However, as you can see this is not the case. Instead the octets are
  printed in reverse order.

  To verify this I tried the same on another machine in the same
  network, running Ubuntu 18.04:

  user@ubuntu1804:~$ ping 10.156.0.63
  PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data.
  From 10.15.0.1: icmp_seq=2 Redirect Host(New nexthop: 10.15.0.2)

  As you can see, the printout is correct here: "New nexthop: 10.15.0.2"

  I further verified the discrepancy by using tcpdump to interpret the
  ICMP packets on the ubuntu2004 machine, and there seems to be no
  problem for tcpdump to display the correct IP address.

  My assumption is that there is something wrong in the print function
  which displays the IP address for a host redirect.

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

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

[Desktop-packages] [Bug 1892107] [NEW] NETWORK IS BEAKING THE OS

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello, my Uuntu 20.04 has a problem, I've formatted it countless times
and this error always occurs.

I'm doing something, the system simply informs that there is no
internet, and it really runs out of internet and if I try to connect in
my hand, it simply locks the entire system, leaving the fan running.

I use Ubuntu, as my computer is a Macbook pro 2012 and will no longer
receive a system update.

Macbook pro 13" i7 mid 2012 original network card.


>From what I noticed, it looks like a loop is occurring, but I couldn't get any 
>more details due to the crash.

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
NonfreeKernelModules: wl
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: Tue Aug 18 20:37:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa]
InstallationDate: Installed on 2020-07-16 (33 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Apple Inc. MacBookPro9,2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=b1280c6f-f86c-494d-b8f0-1ceed5d31914 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/10/2020
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 233.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvr233.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
mtime.conffile..etc.apport.crashdb.conf: 2020-08-18T20:29:26.081990
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu
-- 
NETWORK IS BEAKING THE OS
https://bugs.launchpad.net/bugs/1892107
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

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

[Rodney Graff]

Did confirm the print doctor warning.

Some of the files it is trying to access are in fact locked.

Do not know why or if this makes any difference for actually using the
printer or scanner.

Kindest regards; Scorch.

** Attachment added: "Print Doctor Warns these files are locked"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5402621/+files/Locked.png

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

Title:
  cups hplip not install printer

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

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

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

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

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

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

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

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

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

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

[Rodney Graff]

I have similar problems. See:
https://answers.launchpad.net/hplip/+question/692399

Running the latest version of Kubuntu and just tried to install brand
new HP think tank 551 MFP.

Does involve similar warnings from print doctor saying it cannot access
some files.

| PERMISSION |
--

USB Smart_Tank_Plus_550 Required - - OK Node:'/dev/bus/usb/003/002'
Perm:' root lp rw- rw- rw- rw- r--'

Checking Permissions

Checking for Configured Queues
warning: Fail to read ppd=/etc/cups/ppd/Smart_Tank_Plus_550.ppd file
warning: Insufficient permission to access file 
/etc/cups/ppd/Smart_Tank_Plus_550.ppd
warning: Could not complete Queue(s) configuration check

Checking for HP Properitery Plugin's
No plug-in printers are configured.

Diagnose completed... "

Is this entire issue due to a problem with folder permissions preventing
an application or driver from accessing needed folders or files?

Please respond.

Kindest regards;
Scorch.

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

Title:
  cups hplip not install printer

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

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

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

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

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

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

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

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

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

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

[Rodney Graff]

I have similar problems. See:
https://answers.launchpad.net/hplip/+question/692399

Running the latest version of Kubuntu and just tried to install brand
new HP think tank 551 MFP.

Does involve similar warnings from print doctor saying it cannot access
some files.

| PERMISSION |
--

USB Smart_Tank_Plus_550 Required - - OK Node:'/dev/bus/usb/003/002'
Perm:' root lp rw- rw- rw- rw- r--'

Checking Permissions

Checking for Configured Queues
warning: Fail to read ppd=/etc/cups/ppd/Smart_Tank_Plus_550.ppd file
warning: Insufficient permission to access file 
/etc/cups/ppd/Smart_Tank_Plus_550.ppd
warning: Could not complete Queue(s) configuration check

Checking for HP Properitery Plugin's
No plug-in printers are configured.

Diagnose completed... "

Is this entire issue due to a problem with folder permissions preventing
an application or driver from accessing needed folders or files?

Please respond.

Kindest regards;
Scorch

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

Title:
  cups hplip not install printer

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

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

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

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

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

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

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

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

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

[Desktop-packages] [Bug 1892085] Re: Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab

[Mateusz Stachowski]

The Opera snap has exactly the same problem.

Firefox snap shows the correct cursors.

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

Title:
  Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait
  and cursor:grab

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  0. In an Ubuntu 20.04 live session or new installation, install the
  Chromium snap and Google's Chrome deb packages.

  1. In both browsers, try the MDN cursor demos at
  https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor:
  wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;"
  button, then move the mouse over the blue box on the right to see the
  cursor set by that CSS option.) Or any view any page that sets these
  cursors with CSS such as

  - cursor: grab
  - Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
  - Google Sheets, e.g. hovering over a highlighted cell's border
  - cursor: wait
  - NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

  2. Observe that in Chromium, the CSS-set wait spinner and grab hand
  cursors are using the Adwaita theme, instead of the Ubuntu-default
  Yaru theme. The correct Yaru theme cursors are used in Chrome and
  other apps. (Note that for the cursor:grab examples, the Adwaita grab
  cursor [black hand] is shown when *hovering*, but the correct Yaru
  cursor [white hand] is shown once you click down, since this is no
  longer set by cursor:grab.)

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

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

[Desktop-packages] [Bug 1892085] Re: Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab

[Launchpad Bug Tracker]

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

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

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

Title:
  Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait
  and cursor:grab

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  0. In an Ubuntu 20.04 live session or new installation, install the
  Chromium snap and Google's Chrome deb packages.

  1. In both browsers, try the MDN cursor demos at
  https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor:
  wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;"
  button, then move the mouse over the blue box on the right to see the
  cursor set by that CSS option.) Or any view any page that sets these
  cursors with CSS such as

  - cursor: grab
  - Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
  - Google Sheets, e.g. hovering over a highlighted cell's border
  - cursor: wait
  - NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

  2. Observe that in Chromium, the CSS-set wait spinner and grab hand
  cursors are using the Adwaita theme, instead of the Ubuntu-default
  Yaru theme. The correct Yaru theme cursors are used in Chrome and
  other apps. (Note that for the cursor:grab examples, the Adwaita grab
  cursor [black hand] is shown when *hovering*, but the correct Yaru
  cursor [white hand] is shown once you click down, since this is no
  longer set by cursor:grab.)

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

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

[Desktop-packages] [Bug 1891822] Re: Libreoffice-calc crashes on menu selection

[Brent Rose]

Not sure how much of the initial part of the log you want to see but these are 
the last few lines of the normal startup of the computer, then opening 
libreoffice and selecting Tools>customize and having it crash. If you want any 
of the log entries before this then let me know:
...
Aug 18 17:50:04  systemd-timesyncd[572]: Initial synchronization to time 
server 91.189.91.157:123 (ntp.ubuntu.com).
Aug 18 17:50:06  systemd[1]: systemd-hostnamed.service: Succeeded.
Aug 18 17:50:10  systemd[1]: systemd-timedated.service: Succeeded.
Aug 18 17:50:14  systemd[1]: blueman-mechanism.service: Succeeded.
Aug 18 17:52:13  systemd[1]: Starting Daily apt upgrade and clean 
activities...
Aug 18 17:52:16  systemd[1]: apt-daily-upgrade.service: Succeeded.
Aug 18 17:52:16  systemd[1]: Finished Daily apt upgrade and clean 
activities.
Aug 18 17:54:59  systemd[1518]: Started VTE child process 2287 launched by 
mate-terminal process 2280.
Aug 18 17:55:14  audit[2324]: AVC apparmor="ALLOWED" operation="open" 
profile="libreoffice-soffice" name="/run/user/1000/ICEauthority" pid=2324 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:14  kernel: kauditd_printk_skb: 29 callbacks suppressed
Aug 18 17:55:14  kernel: audit: type=1400 audit(1597787714.236:41): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/run/user/1000/ICEauthority" pid=2324 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:14  kernel: audit: type=1400 audit(1597787714.236:42): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/run/user/1000/ICEauthority" pid=2324 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:14  kernel: audit: type=1400 audit(1597787714.236:43): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/run/user/1000/ICEauthority" pid=2324 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:14  kernel: audit: type=1400 audit(1597787714.236:44): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/run/user/1000/ICEauthority" pid=2324 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:14  audit[2324]: AVC apparmor="ALLOWED" operation="open" 
profile="libreoffice-soffice" name="/run/user/1000/ICEauthority" pid=2324 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:14  audit[2324]: AVC apparmor="ALLOWED" operation="open" 
profile="libreoffice-soffice" name="/run/user/1000/ICEauthority" pid=2324 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:14  audit[2324]: AVC apparmor="ALLOWED" operation="open" 
profile="libreoffice-soffice" name="/run/user/1000/ICEauthority" pid=2324 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug 18 17:55:44  systemd[1518]: Started VTE child process 2347 launched by 
mate-terminal process 2280.

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

Title:
  Libreoffice-calc crashes on menu selection

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  From the menu bar in Libreoffice-calc 6.4.4.2 (Build ID:
  1:6.4.4-0ubuntu0.20.04.1), selecting Tools>Customize will crash the
  application. Issue happens on various computers, desktop and laptop
  and this is with a fresh intsall of Mate 20.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.4-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: MATE
  Date: Sun Aug 16 17:28:12 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-08-14 (2 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866419] Re: gnome-shell displays date incorrectly for nl_NL locale

[Gunnar Hjalmarsson]

** Changed in: gnome-desktop3 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: gnome-desktop3 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-translations
   Status: New => Fix Released

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

Title:
  gnome-shell displays date incorrectly for nl_NL locale

Status in gnome-desktop:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Eoan:
  Won't Fix
Status in gnome-desktop3 source package in Focal:
  Fix Released

Bug description:
  I am running the regular edition of Ubuntu. I have my system set to
  the nl_NL locale. The clock display on the top bar of gnome-shell is
  displayed as "vr mrt 6 23:45:01". While the individual parts are
  translated correctly, the order is not. It should be "vr 6 mrt
  23:45:01".

  Steps to reproduce:
  - Install in Dutch
  - Observe that the clock in the top bar shows the month name before the day.

  Other notes:
  - Bug is present in at least 18.04, 19.04, 19.10 and the upcoming 20.04
  - Adding/removing parts to the date (like weekday, seconds, etc.) using 
gnome-tweaks does not make any difference: all combinations have this wrong 
date order.

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

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

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

[Daniel Letzeisen]

A patch has been proposed upstream:
https://gitlab.gnome.org/esoleyman/cheese/-/commit/81f9be8b6c6208b8d88badead94eb5d5da0bfb63

Test version in my PPA (works for me on Xubuntu):
https://launchpad.net/~dtl131/+archive/ubuntu/mediahacks2/+packages

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

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

Status in cheese package in Ubuntu:
  Triaged

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

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

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

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

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

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

[Desktop-packages] [Bug 1892093] Re: mem_encrypt=on makes radeon driver crash during startup

[Avamander]

Dmesg output of encountering non-working graphics

** Attachment added: "dmesg2"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1892093/+attachment/5402600/+files/dmesg2

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

Title:
  mem_encrypt=on makes radeon driver crash during startup

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  lspci output:

  08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658]

  dmesg error output:

  [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x3010C)=0xCAFEDEAD)
  radeon :08:00.0: disabling GPU acceleration

  kernel parameters with issue:

  quiet splash amd_iommu=on mem_encrypt=on

  Issue appears on kernels 5.4.0-26-generic 5.4.0-40-generic
  5.4.0-42-generic 5.6.0-1021-oem

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

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

[Desktop-packages] [Bug 1892093] [NEW] mem_encrypt=on makes radeon driver crash during startup

[Avamander]

Public bug reported:

lspci output:

08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658]

dmesg error output:

[drm:cik_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x3010C)=0xCAFEDEAD)
radeon :08:00.0: disabling GPU acceleration

kernel parameters with issue:

quiet splash amd_iommu=on mem_encrypt=on

Issue appears on kernels 5.4.0-26-generic 5.4.0-40-generic
5.4.0-42-generic 5.6.0-1021-oem

** Affects: xserver-xorg-video-ati (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  mem_encrypt=on makes radeon driver crash during startup

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  lspci output:

  08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
  [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658]

  dmesg error output:

  [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x3010C)=0xCAFEDEAD)
  radeon :08:00.0: disabling GPU acceleration

  kernel parameters with issue:

  quiet splash amd_iommu=on mem_encrypt=on

  Issue appears on kernels 5.4.0-26-generic 5.4.0-40-generic
  5.4.0-42-generic 5.6.0-1021-oem

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

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

[Desktop-packages] [Bug 1892094] [NEW] Nvidia Desktop Brightness Reset on Blank Screen

[ubuserone]

Public bug reported:

Brightness Reset to Maximum on Nvidia GPU Desktop when setting on Blank
Screen

The Desktop LED Monitor brightness or Gamma level is not preserved and
reset when I set gnome-control-center setting on Power to Blank Screen.

I try to post as much details as possible.

-I did a test by setting Nvidia X Server Color Correction and set any
brightness and gamma.It get reset when Power Saving Blank Screen time
active which I had set 10 minutes to save power by auto turning off the
display.

-The second test was by installing a Brightness Controller which use
Xrandr but same result of getting reset when I set Blank Screen.I also
manually set xrandr --output DVI-D-0 –brightness 0.5 --gamma 0.5:0.5:0.5
an value get reset after the trigger from blank screen.

-Third test by selecting Nouveau open source but same result of getting
reset when I set Blank Screen.

-Forth test ,  manually turn off the monitor ‘xset dpms force off’ it
doesn’t trigger the brightness reset.

Since the system is using Desktop GPU , the folder on xblacklight is
empty without config files.

The flow 
> Set brightness >  Power Saving Blank Screen time active > Brightness reset > 
> External Monitor dim and Turn Off > Press any keyboard button to wakeup the 
> display > Brightness Stay at reset value of Full 100% brightness.

The details I had tested , I suspect gsd-power may have related to this 
issue.This is happen before which I had find a solution to other brightness 
reset happen when every restart , delete a files upon restart , open a web 
browser with and play a video stream, login and logout , suspend and Power 
Saving Blank Screen.
All of this are affected by gsd-color.Which I had found a link a fix suggestion
https://github.com/LordAmit/Brightness/issues/102#issuecomment-374253884 by 
disable  /usr/lib/gnome-settings-daemon/gsd-color on startup.

The only left is Power Saving Blank Screen still get reset when it get active.I 
am not too sure whether it is related to gsd-power , I did disable it but it 
also disable Power Saving Blank Screen together.
It just goes to screensaver mode and did not turn off the monitor.

I do not have any basic on gsd-power code
https://gitlab.gnome.org/starnight/gnome-settings-
daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power/gsd-
power-manager.c Not knowing which line did it callback and get reset ,
presumably ‘GSD_POWER_IDLE_MODE_BLANK’ ?

Fresh Install

OS : Ubuntu 18.04.4
Architecture: amd64 
Nvidia : GTX 1050
Driver : NVIDIA Driver Version: 440.100
uname : 5.4.0-42-generic
DisplayManager: gdm3

Journalctl log when blank screen active.

nvidia-settings[19556]: PRIME: is it supported? no
nvidia-settings[19556]: PRIME: No offloading required. Abort
nvidia-settings[19556]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Check that logind is properly installed and pam_systemd is getting used at 
login.
gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get session 
path for session. Check that logind is properly installed and pam_systemd is 
getting used at login.
gnome-screensav[1551]: Source ID 19140 was not found when attempting to remove 
it
gnome-session-binary[1521]: WARNING: Could not get session path for session. 
Check that logind is properly installed and pam_systemd is getting used at 
login.
gnome-session[1521]: gnome-session-binary[1521]: WARNING: Could not get session 
path for session. Check that logind is properly installed and pam_systemd is 
getting used at login.

Reading the log shows somewhere it trigger brightness reset.The Nvidia
Setting prime message is show because I am using a desktop dedicated GPU
without using nvidia prime for laptop check to  switching between build
in intel gpu and nvidia.

In which way I could fix brightness reset when I need to set Blank
Screen to turn off the monitor to save power ?

I did another test by manually turn off the monitor ‘xset dpms force
off’ it doesn’t trigger the brightness reset.It only happen when it is
set with a timer at setting blank screen to 1-15 minutes and which it
call for a PID which unknown and I assume gsd-power that trigger the
reset.

The most I can find is the gsd-power code
https://gitlab.gnome.org/starnight/gnome-settings-
daemon/blob/c64c243e345cb92ed0c197a377767bcbf1704c1b/plugins/power/gsd-
power-manager.c .I am nor expert on daemon.service pin point the
trigger.


I did a search at askubuntu , ubuntu forum and ask around at ubuntu irc channel 
but did not get any similar result.
Either it happen in my system or it happen to everyone using Nvidia dedicated 
GPU on desktop.I may need someone who using them willing to help on testing out 
whether it happen on everyone.

Any solution to fix brightness reset but retain power saving on monitor
turn off automatically with blank screen ?

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


** Tags: blank brightness color nvidia power screen

-- 
You received this bug notification

[Desktop-packages] [Bug 1892093] [NEW] mem_encrypt=on makes radeon driver crash during startup

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

lspci output:

08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658]

dmesg error output:

[drm:cik_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x3010C)=0xCAFEDEAD)
radeon :08:00.0: disabling GPU acceleration

kernel parameters with issue:

quiet splash amd_iommu=on mem_encrypt=on

Issue appears on kernels 5.4.0-26-generic 5.4.0-40-generic
5.4.0-42-generic 5.6.0-1021-oem

** Affects: xserver-xorg-video-ati (Ubuntu)
 Importance: Undecided
 Status: New

-- 
mem_encrypt=on makes radeon driver crash during startup
https://bugs.launchpad.net/bugs/1892093
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xserver-xorg-video-ati 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 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

[Kyrylo Bohdanenko]

One more update. Using mainline kernel v5.8.1 from here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/

There is a definite improvement in connectivity. However, the originally
reported issue is still there, and I am getting these in my
/var/log/syslog (w/ custom pulseaudio-module-bluetooth):

sie 18 21:43:01 k-laptop pulseaudio[921]: Refused to switch profile to 
a2dp_sink_ldac: Not connected
sie 18 21:43:13 k-laptop pulseaudio[921]: Refused to switch profile to 
a2dp_sink_sbc: Not connected
sie 18 21:43:16 k-laptop pulseaudio[921]: Refused to switch profile to 
a2dp_sink_ldac: Not connected

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

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1892087] [NEW] screenshot a select area does not work

[LittleBigBrain]

Public bug reported:

Shift+Prt Scrn or invoke the screenshot app then select the `select the area to 
grab`. After area selected the save dialogue does not show up.
screenshot a window or desktop works as normal.
ubuntu 20.04

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

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

Title:
  screenshot a select area does not work

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Shift+Prt Scrn or invoke the screenshot app then select the `select the area 
to grab`. After area selected the save dialogue does not show up.
  screenshot a window or desktop works as normal.
  ubuntu 20.04

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

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

[Desktop-packages] [Bug 1891648] Re: Cannot switch to A2DP profile w/o restarting bluetooth.service [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

[Kyrylo Bohdanenko]

Found this bug report on kernel's bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=204765

There are bluetooth-related entries from journalctl -x:

sie 18 21:14:25 k-laptop bluetoothd[11444]: RFCOMM server failed for Headset 
Voice gateway: rfcomm_bind: Address already in use (98)
sie 18 21:14:25 k-laptop bluetoothd[11444]: RFCOMM server failed for 
:1.36/Profile/HSPHSProfile/1108--1000-8000-00805f9b34fb: rfcomm_bind: 
Address already in use (98)
sie 18 21:14:25 k-laptop dbus-daemon[655]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
sie 18 21:14:25 k-laptop kernel: debugfs: File 'le_min_key_size' in directory 
'hci0' already present!
sie 18 21:14:25 k-laptop kernel: debugfs: File 'le_max_key_size' in directory 
'hci0' already present!


I do have similar symptoms, so it might be the bug. Since Groovy's
kernel version is 5.4, has the fix been backported?

** Bug watch added: Linux Kernel Bug Tracker #204765
   https://bugzilla.kernel.org/show_bug.cgi?id=204765

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

Title:
  Cannot switch to A2DP profile w/o restarting bluetooth.service
  [pulseaudio: Refused to switch profile to a2dp_sink: Not connected]

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting to any Bluetooth device, PulseAudio fails to change
  its profile to A2DP (and leaves it in HSP/HFP).

  The following is appended to /var/log/syslog when trying to change
  profile in pavucontrol:

  Aug 14 14:59:02 k-laptop pulseaudio[18882]: Refused to switch profile
  to a2dp_sink: Not connected

  I'm currently using patched pulseaudio-modules-bt from here:
  https://github.com/EHfive/pulseaudio-modules-bt. But the problem
  persists with both packages.

  The working workaround I found is:

sudo systemctl restart bluetooth.service
bluetoothctl

  # list device MACs
  devices

  # use a MAC from the list above
  connect 

  After doing this, it is possible to switch to A2DP profile in
  pavucontrol. But such restart is required each time device is
  connected.

  I'm using
  Kubuntu 20.10 (development branch)
  pulseaudio: 1:13.99.1-1ubuntu8
  pulseaudio-modules-bluetooth: 1:13.99.1-1ubuntu8-9git+20200812~dfeee4f
but also reproducible with 1:13.99.1-1ubuntu8

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu8
  ProcVersionSignature: Ubuntu 5.4.0-43.47-generic 5.4.55
  Uname: Linux 5.4.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kyrboh19544 F pulseaudio
   /dev/snd/pcmC0D0c:   kyrboh19544 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kyrboh19544 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 14 15:06:43 2020
  InstallationDate: Installed on 2020-08-07 (6 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (3 days ago)
  dmi.bios.date: 05/22/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.2
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1892085] [NEW] Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab

[Alexander Browne]

Public bug reported:

0. In an Ubuntu 20.04 live session or new installation, install the
Chromium snap and Google's Chrome deb packages.

1. In both browsers, try the MDN cursor demos at
https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor: wait
and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;" button,
then move the mouse over the blue box on the right to see the cursor set
by that CSS option.) Or any view any page that sets these cursors with
CSS such as

- cursor: grab
- Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
- Google Sheets, e.g. hovering over a highlighted cell's border
- cursor: wait
- NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

2. Observe that in Chromium, the CSS-set wait spinner and grab hand
cursors are using the Adwaita theme, instead of the Ubuntu-default Yaru
theme. The correct Yaru theme cursors are used in Chrome and other apps.
(Note that for the cursor:grab examples, the Adwaita grab cursor [black
hand] is shown when *hovering*, but the correct Yaru cursor [white hand]
is shown once you click down, since this is no longer set by
cursor:grab.)

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

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

Title:
  Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait
  and cursor:grab

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  0. In an Ubuntu 20.04 live session or new installation, install the
  Chromium snap and Google's Chrome deb packages.

  1. In both browsers, try the MDN cursor demos at
  https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor:
  wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;"
  button, then move the mouse over the blue box on the right to see the
  cursor set by that CSS option.) Or any view any page that sets these
  cursors with CSS such as

  - cursor: grab
  - Accuweather/mapbox radar maps, e.g. 
https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794
  - Google Sheets, e.g. hovering over a highlighted cell's border
  - cursor: wait
  - NYT video pages while the video loads, e.g. 
https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html

  2. Observe that in Chromium, the CSS-set wait spinner and grab hand
  cursors are using the Adwaita theme, instead of the Ubuntu-default
  Yaru theme. The correct Yaru theme cursors are used in Chrome and
  other apps. (Note that for the cursor:grab examples, the Adwaita grab
  cursor [black hand] is shown when *hovering*, but the correct Yaru
  cursor [white hand] is shown once you click down, since this is no
  longer set by cursor:grab.)

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

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

[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[spinylumpsucker]

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

I'm adding an observation here because the NetworkManager work-around
thread is here and not in #1676547.

Confirmed with additional information: Ubuntu 20.04 workstation ISO
(downloaded August 2020) exhibits the issue when run in the LiveCD
"Trial" mode. The Gnome "Settings" UI does not by default show the
"Wired" menu by default even if the underlying NIC is not servicing
DHCP. The network icon is also missing from the top status bar.

This behavior differs from Ubuntu 16.04 & 18.04 LiveCD ISO images.

In my test cases, copying /usr/lib/NetworkManager/conf.d/10-globally-
managed-devices.conf to /etc/NetworkManager/conf.d and then setting
"unmanaged-devices=all" followed by restarting NetworkManager causes the
menu to appear.

It is worth pointing out that once installed the menu appears as
expected once rebooted, so this issue is specific to the LiveCD instance
and not the installed instance.

I'm not going to try to guess why the developers decided to hide this
functionality in the LiveCD, but I for one am disappointed because I am
working in a mixed DHCP/VLAN network environment where static IP
addresses are the rule rather than the exception.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Rafael César Neves]

Same issue here with Sony WH-CH710N on a fresh install of Ubuntu 20.04.1
LTS kernel 5.4.0-42-generic

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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

[Desktop-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Released
Status in nvidia-settings source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to collect information about X server
    crashes from coredumpctl, when available.
  - Updated the nvidia-drm kernel module for compatibility with the
    removal of the DRIVER_PRIME flag in recent Linux kernel versions.
  - Enabled parallel GLSL shader linking by default; i.e., allow
    GL_ARB_parallel_shader_compile to work without first calling
    glMaxShaderCompilerThreadsARB().
  - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC
    Compatible monitors on supported GPUs.For more details, see
    "Configuring Multiple Display Devices on One X Screen" in the README.
    Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast
    extensions.For more details, see the "Configuring SLI and Multi-GPU
    F

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

[Amr Ibrahim]

I really hope that performance-related fixes could be backported to
Ubuntu 20.04 so that I would not have to upgrade to 20.10. I have never
upgraded to a non-LTS release since Trusty 14.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rafael César Neves]

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

Same issue here with Sony WH-CH710N on a fresh install of Ubuntu 20.04.1
LTS kernel 5.4.0-42-generic

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1880832] Re: [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

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

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

Title:
  [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  New
Status in wslu source package in Bionic:
  New
Status in wslu source package in Eoan:
  Won't Fix

Bug description:
  [Impact]

  The package is already released in focal/groovy but it still affects
  eoan/bionic/xenial, a SRU is needed.

  [Test Case]

   * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates
   * Run the autopktest in a WSL environment where the user name contains space.
   * Verify the other individual bugs fixed by the SRU.

  [Regression Potential]

  * There is a issue on #1877016 which is already addressed in the next
  release, but I hope to SRU the current packages in order to prevent
  future issues when SRUing.

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

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

[Desktop-packages] [Bug 1888191] Re: udisksd assert failure: malloc_consolidate(): invalid chunk size

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1888191/+attachment/5394238/+files/CoreDump.gz

** Information type changed from Private Security to Public

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

Title:
  udisksd assert failure: malloc_consolidate(): invalid chunk size

Status in udisks2 package in Ubuntu:
  New

Bug description:
  each time I power on my system, this error is appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: udisks2 2.9.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  AssertionMessage: malloc_consolidate(): invalid chunk size
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.core.rules 95-pico.rules 70-snap.vlc.rules
  Date: Mon Jul 13 14:04:15 2020
  ExecutablePath: /usr/libexec/udisks2/udisksd
  InstallationDate: Installed on 2020-03-11 (130 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 10SUSCDT00
  ProcCmdline: /usr/libexec/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=f519d40c-c85a-4d0b-b2c2-a4fa38f74c41 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: udisks2
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fc362b12285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fc362b14278 "malloc_consolidate(): invalid 
chunk size") at malloc.c:5347
   malloc_consolidate (av=av@entry=0x7fc362b43b80 ) at malloc.c:4477
   _int_malloc (av=av@entry=0x7fc362b43b80 , 
bytes=bytes@entry=8216) at malloc.c:3699
   __libc_calloc (n=, elem_size=) at malloc.c:3428
  Title: udisksd assert failure: malloc_consolidate(): invalid chunk size
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1UKT4EA
  dmi.board.name: 312A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305264703953
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1UKT4EA:bd12/16/2019:svnLENOVO:pn10SUSCDT00:pvrThinkCentreM720s:rvnLENOVO:rn312A:rvrSDK0J40697WIN3305264703953:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M720s
  dmi.product.name: 10SUSCDT00
  dmi.product.sku: LENOVO_MT_10SU_BU_Think_FM_ThinkCentre M720s
  dmi.product.version: ThinkCentre M720s
  dmi.sys.vendor: LENOVO
  separator:

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

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

[Desktop-packages] [Bug 1888085] Re: Fehler : Ubuntu 18.04.4 LTS

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Fehler : Ubuntu 18.04.4 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  Fehler : Ubuntu 18.04.4 LTS

  
  Details
  Do you want to start the upgrade?

  1 package is going to be removed

  To prevent data loss close all open applications and  documents

  
  Details: Remove (1)  systemd-shim-shim for systemd

  
  Could not install 'systemd-shim'

  The upgrade will continue but the 'systemd-shim' package may not be in
  a working state. Please consider submitting a bug report about it.

  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  Could not install the upgrades

  
  The upgrade has aborted. Your system could be in an unusable state. A 
recovery will run now (dpkg --configure -a).

  
  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 18 23:15:19 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
  InstallationDate: Installed on 2020-07-17 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-78LMT-USB3 R2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: sex
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 R2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jul 18 01:11:31 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input  USB Keyboard   KEYBOARD, id 8
   input  USB Keyboard   KEYBOARD, id 9
   inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1874818] Re: Please pull Mutter/Wayland fixes

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: mutter (Ubuntu Eoan)
   Status: Fix Committed => 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/1874818

Title:
  Please pull Mutter/Wayland fixes

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  I have upstreamed a GNOME/Wayland desktop freeze fix in:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1209 (master)
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1215 (3.36 branch)
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1216 (3.34 branch)

  [ Impact ]

  I diagnosed the freeze on Mutter 3.34 Ubuntu 19.10 flavour first, with
  DisplayLink hardware. Any DRM driver that may temporarily fail
  drmModePageFlip() calls might trigger this.

  [ Test case ]

  I triggered the freeze particularly by trying to make a DisplayLink
  output the only active output via GNOME display settings. Other
  triggers are possible.

  This fix may help with
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853357 but I
  don't know for sure.

  [ Regression potential ]

  Higher page flips could happen using native backend (wayland)

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

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

[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: nvidia-prime (Ubuntu Eoan)
   Status: Triaged => Won't Fix

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

Title:
  [cosmic+] error booting with prime-select intel: prime-select does not
  update initramfs to blacklist nvidia modules

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Triaged
Status in ubuntu-drivers-common source package in Bionic:
  Triaged
Status in nvidia-prime source package in Eoan:
  Won't Fix
Status in ubuntu-drivers-common source package in Eoan:
  Won't Fix

Bug description:
  when I try to boot with the iGPU selected, DE won't boot, with nvidia 
selected, everithing is fine.
  I tried uninstalling nvidia driver and it allowed my to access without any 
problems and intel is working fine

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-prime 0.8.13
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 16 12:41:26 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-09-25 (20 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+subscriptions

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

[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: ubuntu-drivers-common (Ubuntu Eoan)
   Status: Triaged => Won't Fix

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

Title:
  [cosmic+] error booting with prime-select intel: prime-select does not
  update initramfs to blacklist nvidia modules

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Triaged
Status in ubuntu-drivers-common source package in Bionic:
  Triaged
Status in nvidia-prime source package in Eoan:
  Won't Fix
Status in ubuntu-drivers-common source package in Eoan:
  Won't Fix

Bug description:
  when I try to boot with the iGPU selected, DE won't boot, with nvidia 
selected, everithing is fine.
  I tried uninstalling nvidia driver and it allowed my to access without any 
problems and intel is working fine

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-prime 0.8.13
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 16 12:41:26 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-09-25 (20 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+subscriptions

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

[Desktop-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: ubuntu-meta (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed
Status in ubuntu-meta source package in Eoan:
  Won't Fix

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Desktop-packages] [Bug 1825297] Re: When OSK is present, typing on physical keyboard usually does not trigger the OSK to disappear (X11 only)

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

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

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

Title:
  When OSK is present, typing on physical keyboard usually does not
  trigger the OSK to disappear (X11 only)

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-shell source package in Disco:
  Won't Fix
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in gnome-shell source package in Focal:
  Triaged

Bug description:
  I use a XPS 13 9380 laptop with Disco. When On-Screen-Keyboard is present, 
typing on physical keyboard usually doesn't trigger the OSK to disappear.
  The problem only happen on X11 not on Wayland.

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: mutter (Ubuntu Eoan)
   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/1853357

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1866419] Re: gnome-shell displays date incorrectly for nl_NL locale

[Brian Murray]

The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release

** Changed in: gnome-desktop3 (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

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

Title:
  gnome-shell displays date incorrectly for nl_NL locale

Status in gnome-desktop:
  Fix Released
Status in Ubuntu Translations:
  New
Status in gnome-desktop3 package in Ubuntu:
  Fix Committed
Status in gnome-desktop3 source package in Eoan:
  Won't Fix
Status in gnome-desktop3 source package in Focal:
  Fix Committed

Bug description:
  I am running the regular edition of Ubuntu. I have my system set to
  the nl_NL locale. The clock display on the top bar of gnome-shell is
  displayed as "vr mrt 6 23:45:01". While the individual parts are
  translated correctly, the order is not. It should be "vr 6 mrt
  23:45:01".

  Steps to reproduce:
  - Install in Dutch
  - Observe that the clock in the top bar shows the month name before the day.

  Other notes:
  - Bug is present in at least 18.04, 19.04, 19.10 and the upcoming 20.04
  - Adding/removing parts to the date (like weekday, seconds, etc.) using 
gnome-tweaks does not make any difference: all combinations have this wrong 
date order.

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

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

[Desktop-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"

[Brian Murray]

eoan has reached end of life, so this bug will not be fixed for that
release

** Changed in: software-properties (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

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

Title:
  update-notifier doesn't respect "automatically check for updates:
  Never"

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Eoan:
  Won't Fix

Bug description:
  This has been a long-standing problem with various ubuntu
  installations, and I'm sensing some reticence in doing anything about
  it. This attitude also seems to be purposeful to try to cajole updates
  on people who make bad choices due to confusion/fud/paranoia.

  apt install fails due to:

  E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

  A great deal of networking is taking place despite setting automatic
  upgrades to "never". Cycling this doesn't seem to do anything. This
  action is hostile to programmers and the setting should be respected.

  Wisdom on threads is to let it update until it's out of updates, and
  then it supposedly respects the "never" flag, but the experience I'm
  having is much more non-deterministic. have been using 19.04 for weeks
  now and still get the background notifier using data and getting in
  the way of aptitude package installations. I prefer manual update &&
  upgrade once my code is ready to push.

  Is there another way around this or are people just living with it?

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

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

[Desktop-packages] [Bug 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds

[Brian Murray]

eoan has reached end of life, so this bug will not be fixed for that
release

** Changed in: livecd-rootfs (Ubuntu Eoan)
   Status: Triaged => Won't Fix

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

Title:
  chromium-browser deb->snap transition breaks ubuntukylin image builds

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Triaged
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Released
Status in livecd-rootfs source package in Eoan:
  Won't Fix
Status in ubuntukylin-meta source package in Eoan:
  Fix Released

Bug description:
  From https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881:

  Preparing to unpack 
.../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ...
  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ===> Unable to contact the store, trying every minute for the next 30 minutes
  ===> Still unable to contact the store, trying for another 20 minutes
  ===> Still unable to contact the store, trying for another 10 minutes
  ===> Still unable to contact the store, aborting
  dpkg: error processing archive 
/tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb
 (--unpack):
   new chromium-browser package pre-installation script subprocess returned 
error exit status 1

  It is possible that the flavors should switch to seeding the snap
  instead of the deb.  However, it's unclear to me why the deb is
  failing to talk to the Snap Store, because seeding of snaps DOES work
  from within image builds.

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

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

[Desktop-packages] [Bug 384062] Re: evince-thumbnailer with a 100% CPU usage

[Sudeep K N Holla]

Yes I see this issue. I tried reporting it as new bug but it pointed me to this 
instead.
Deleting the file just fix the issue.

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

Title:
  evince-thumbnailer with a 100% CPU usage

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  Guys,

  There are some complains about evince-thumbnailer with a 100% CPU
  usage, but none of them could be replicated. I think I was able to
  track down the problem.

  Whenever I'm downloading a PDF and saving it on my desktop, the file
  changes at each second and every time it changes, evince-thumbnailer
  tries to create a new thumb for it, then having a 100% CPU usage.

  [INFO]

  Description:  Ubuntu 8.04.2
  Release:  8.04

  evince:
Installed: 2.22.2-0ubuntu2
Candidate: 2.22.2-0ubuntu2
Version table:
   *** 2.22.2-0ubuntu2 0
  500 http://br.archive.ubuntu.com hardy-updates/main Packages
  100 /var/lib/dpkg/status
   2.22.1.1-0ubuntu1 0
  500 http://br.archive.ubuntu.com hardy/main Packages

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

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

[Desktop-packages] [Bug 1892031] Re: Xorg crash

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  One day ago it crashed during using it and restarted by itself. Today
  when I started my computer it began to flash black

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 18 15:15:40 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094]
 Subsystem: Acer Incorporated [ALI] Device [1025:1094]
  InstallationDate: Installed on 2019-09-15 (337 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b571 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8d196740-0a4f-4a2b-ab15-be5c76196c92 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd08/02/2016:svnAcer:pnAspireE5-575G:pvrV1.12:rvnAcer:rnIronman_SK:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-575G
  dmi.product.sku: Aspire E5-575G_115F_1.12
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1892031] [NEW] Xorg crash

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

One day ago it crashed during using it and restarted by itself. Today
when I started my computer it began to flash black

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 18 15:15:40 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094]
   Subsystem: Acer Incorporated [ALI] Device [1025:1094]
InstallationDate: Installed on 2019-09-15 (337 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b571 Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8d196740-0a4f-4a2b-ab15-be5c76196c92 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.12
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd08/02/2016:svnAcer:pnAspireE5-575G:pvrV1.12:rvnAcer:rnIronman_SK:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: KBL
dmi.product.name: Aspire E5-575G
dmi.product.sku: Aspire E5-575G_115F_1.12
dmi.product.version: V1.12
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic crash ubuntu
-- 
Xorg crash
https://bugs.launchpad.net/bugs/1892031
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1892064] [NEW] unable to login google account

[Andre Felipe Machado]

Public bug reported:

deja-dup freeze its backup process, then I found that gnome-control-center 
ubuntu 18.04 is unable to login on google account anymore.
Maybe google changed its API for login accounts.
Regards.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 18 12:30:40 2020
InstallationDate: Installed on 2019-10-17 (306 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  unable to login google account

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

Bug description:
  deja-dup freeze its backup process, then I found that gnome-control-center 
ubuntu 18.04 is unable to login on google account anymore.
  Maybe google changed its API for login accounts.
  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 18 12:30:40 2020
  InstallationDate: Installed on 2019-10-17 (306 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1733321] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original descrip

[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.20.4-2ubuntu2.3

---
network-manager (1.20.4-2ubuntu2.3) eoan; urgency=medium

  * d/t/killswitches-no-urfkill
- Call udevadm settle before nmcli radio wifi
  To make sure that change is updated. (LP: #1733321)

 -- Seyeong Kim   Mon, 20 Apr 2020 22:40:44
-0700

** Changed in: network-manager (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was obse

[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing

[Shiney]

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

Hi,

My version info from snap list

chromium   84.0.4147.105   1260  latest/stablecanonical

Tripped over this issue today as I needed to install windows fonts on a
user PC (they get documents with windows ttf fonts) - did so in
/usr/share/fonts/win so fonts would be available to others and then
chromium failed to load. This answer solved it

https://askubuntu.com/a/1259802

# first close all instances of chromium
sudo rm /var/cache/fontconfig/*
rm ~/.cache/fontconfig/*
sudo fc-cache -r -v
rm -rf ~/snap/chromium/common/.cache/fontconfig/

Bit of a bummer as there are quite a few other machines that need
windows fonts and Chromium.

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

Title:
  [snap] Dialog font missing

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  $ lsb_release -rb
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 01:56 CET
  channels:
    stable:80.0.3987.116 2020-02-19 (1036) 160MB -
    candidate: 80.0.3987.116 2020-02-19 (1036) 160MB -
    beta:  81.0.4044.17  2020-02-17 (1028) 161MB -
    edge:  81.0.4044.17  2020-02-14 (1028) 161MB -
  installed:   80.0.3987.116(1036) 160MB -

  Basic Ubuntu 19.10 installation using "factory default" font settings.

  Expected :
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, the file dialog renders normally.

  What happened instead:
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, all characters in the dialog box are empty squares 
(see attached screenshot).

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

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

[Desktop-packages] [Bug 1891733] Re: Support better Arabic font

[Martin Wimpress]

** Changed in: language-selector (Ubuntu Focal)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Support better Arabic font

Status in Ubuntu Seeds:
  New
Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Focal:
  Confirmed
Status in language-selector source package in Groovy:
  Fix Released

Bug description:
  As per the  discussion.

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

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

[Desktop-packages] [Bug 1891733] Re: Support better Arabic font

[Luna Jernberg]

** Changed in: ubuntu-seeds
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Support better Arabic font

Status in Ubuntu Seeds:
  New
Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Focal:
  Confirmed
Status in language-selector source package in Groovy:
  Fix Released

Bug description:
  As per the  discussion.

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

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

[Desktop-packages] [Bug 1891476] Re: gtkmm3.0 ftbfs in focal

[Martin Wimpress]

** Changed in: gtkmm3.0 (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  gtkmm3.0 ftbfs in focal

Status in gtkmm3.0 package in Ubuntu:
  Confirmed

Bug description:
  seen in a focal test rebuild, all architctures:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19795016

  g++ -std=c++11 -DHAVE_CONFIG_H   -I.. -I../gdk  -I../gtk  -pthread -pthread 
-I/usr/include/atkmm-1.6 -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
-I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 
-I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-I/usr/include/gtk-3.0/unix-print -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DDEMOCODEDIR=\"""\"  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-DGLIBMM_DISABLE_DEPRECATED -DGIOMM_DISABLE_DEPRECATED 
-DGTKMM_DISABLE_DEPRECATED -DGDKMM_DISABLE_DEPRECATED -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o gtk-demo/gtkmm_demo-example_appwindow.o `test -f 
'gtk-demo/example_appwindow.cc' || echo './'`gtk-demo/example_appwindow.cc
  gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’ function uses ‘auto’ type 
specifier without trailing return type
 54 | const auto& demo_columns()
| ^
  gtk-demo/demowindow.cc:54:1: note: deduced return type only available with 
‘-std=c++14’ or ‘-std=gnu++14’
  make[4]: *** [Makefile:733: gtk-demo/gtkmm_demo-demowindow.o] Error 1
  make[4]: *** Waiting for unfinished jobs

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

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

[Desktop-packages] [Bug 1888505] Re: Two-finger touchpad zoom extremely sensitive

[Iain Lane]

** Tags removed: rls-bb-wontfix
** Tags added: rls-bb-notfixing

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

Title:
  Two-finger touchpad zoom extremely sensitive

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Open Calc ->  + 

  Expected behaviour: document viewpan zooms/unzooms at a reasonable
  speed

  Observed behaviour: document viewpan zooms/unzooms from maximum zoom
  in to maximum zoom out in maybe 10-15% of the height of the touchpad,
  i.e. it is unusably oversensitive.

  
  Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of 
Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 14:43:20 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (804 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago)

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

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

[Desktop-packages] [Bug 1888505] Re: Two-finger touchpad zoom extremely sensitive

[Martin Wimpress]

** Tags removed: rls-bb-incoming
** Tags added: rls-bb-wontfix

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

Title:
  Two-finger touchpad zoom extremely sensitive

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Open Calc ->  + 

  Expected behaviour: document viewpan zooms/unzooms at a reasonable
  speed

  Observed behaviour: document viewpan zooms/unzooms from maximum zoom
  in to maximum zoom out in maybe 10-15% of the height of the touchpad,
  i.e. it is unusably oversensitive.

  
  Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of 
Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 14:43:20 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (804 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago)

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

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

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

[Alberto]

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

Same issue here with Sony WH-1000MX2 with Ubuntu 20.04.1 LTS kernel
5.6.0-1021-oem

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Gunnar Hjalmarsson]

@Alkis: I added a comment on the new bug. Let's talk there. This one is
closed.

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original description]

  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

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

[Desktop-packages] [Bug 1891767] Re: Nautilus not showing video thumbnails

[Saurav Sengupta]

Sorry, can't relate times exactly. It was after I installed all the
libav and gstreamer libraries, and it happens every time. Personally, I
don't see a connection with the logs, but it seems to me that the issue
has started after Nautilus was upgraded to 3.37.90. The older ones
(e.g., 3.37.3 or 3.37.1) didn't have the issue.

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

Title:
  Nautilus not showing video thumbnails

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu 20.10 (Groovy) Daily Live, GNOME session (gnome-session)
  on Wayland. Nautilus is no longer showing thumbnails (generated by
  Totem) for some video files, although the Totem thumbnail generator
  (totem-video-thumbnailer) is working. Nautilus is showing thumbnails
  for video files with (Ogg) Theora codec content (even if wrapped in a
  non-Ogg file format, such as mkv), but not for others, although I have
  installed all the required/usual libraries (libav*, gstreamer1*).
  Deleting the thumbnail fail cache (~/.cache/thumbnails/fail/) does not
  help. Installing ffmpegthumbnailer does not help either. This seems to
  be a regression, or maybe some libraries for video files in non-free
  codec formats have not been updated properly. Package versions are as
  follows:-

  Nautilus: 1:3.37.90-1ubuntu1
  Totem: 3.34.1-2ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.37.90-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-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Aug 15 23:47:22 2020
  InstallationDate: Installed on 2020-08-15 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200814)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1891822] Re: Libreoffice-calc crashes on menu selection

[Sebastien Bacher]

Weird, then maybe it's not a segfault type of crash. Could you add the
'journalctl -b 0' directly after triggering the issue?

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

Title:
  Libreoffice-calc crashes on menu selection

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  From the menu bar in Libreoffice-calc 6.4.4.2 (Build ID:
  1:6.4.4-0ubuntu0.20.04.1), selecting Tools>Customize will crash the
  application. Issue happens on various computers, desktop and laptop
  and this is with a fresh intsall of Mate 20.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.4-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: MATE
  Date: Sun Aug 16 17:28:12 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-08-14 (2 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Alkis Georgopoulos]

Hi, this fix caused a regression in ubiquity: LP: #1892014

Ubiquity doesn't put alt_shift_toggle in XKBOPTIONS anymore, so we
cannot switch to e.g. Greek using Alt+Shift, after going through a
normal installation (or even in the live session).

Are users expected to manually run `dpkg-reconfigure keyboard-
configuration` right after a GUI installation of Ubuntu?

E.g. ubuntu-mate-18.04.2-desktop-amd64.iso is affected while 18.04.1
isn't.

Should this issue be resolved in console-setup or in ubiquity?

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original description]

  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

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

[Desktop-packages] [Bug 1891767] Re: Nautilus not showing video thumbnails

[Sebastien Bacher]

Thanks, there is no error in that log. Did you trigger the issue and at
what time exactly (to be able to match the log activity)?

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

Title:
  Nautilus not showing video thumbnails

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu 20.10 (Groovy) Daily Live, GNOME session (gnome-session)
  on Wayland. Nautilus is no longer showing thumbnails (generated by
  Totem) for some video files, although the Totem thumbnail generator
  (totem-video-thumbnailer) is working. Nautilus is showing thumbnails
  for video files with (Ogg) Theora codec content (even if wrapped in a
  non-Ogg file format, such as mkv), but not for others, although I have
  installed all the required/usual libraries (libav*, gstreamer1*).
  Deleting the thumbnail fail cache (~/.cache/thumbnails/fail/) does not
  help. Installing ffmpegthumbnailer does not help either. This seems to
  be a regression, or maybe some libraries for video files in non-free
  codec formats have not been updated properly. Package versions are as
  follows:-

  Nautilus: 1:3.37.90-1ubuntu1
  Totem: 3.34.1-2ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.37.90-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-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Aug 15 23:47:22 2020
  InstallationDate: Installed on 2020-08-15 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200814)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1839380] Re: Nautilus freezes when restoring files and a copy already exists

[Sebastien Bacher]

@James, We understand the difficulties you are facing, but it is better
to raise problems you are having in the support tracker at
https://answers.launchpad.net/ubuntu if you are uncertain if they are
bugs. You can also find help with your problem in the support forum of
your local Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org. For help on reporting
bugs, see https://help.ubuntu.com/community/ReportingBugs.

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

Title:
  Nautilus freezes when restoring files and a copy already exists

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I have trashed the hidden file using nautilus to the trash bin, be it
  the hidden configuration file for XScreenSaver that is compiled from
  source, and it regenerated the hidden file in the same location that I
  have deleted the old copy in.

  I attempted to restore the file, but because the file with the same
  name is originated on the same location, Nautilus freezes. It should
  give me the "Replace file with newer version" dialog so I can decide
  if I want to replace the old file with the new one, or if I want to
  rename the trashed hidden file to another name. It shouldn't freeze.

  Here's the clearer example. Suppose that...

  1. I created a file named "test.txt" on "/home/eofla",
  2. I put it to the trash bin,
  3. I repeated Step 1, and
  4. I attempted to restore the same file that was on the trash.
  5. Nautilus freezes.

  Version of Ubuntu:

  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  Version of Nautilus:

  nautilus:
    Installed: 1:3.32.1-1ubuntu1
    Candidate: 1:3.32.1-1ubuntu1
    Version table:
   *** 1:3.32.1-1ubuntu1 500
  500 http://sy.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  Debug output with "G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus":

  Nautilus-Share-Message: 23:01:44.608: Called "net usershare info" but
  it failed: Failed to execute child process “net” (No such file or
  directory)

  Debug output using "gdb nautilus" with exported environment variables
  of G_DEBUG="all" NAUTILUS_DEBUG="All" (More useful, with stack trace):
  https://paste.ubuntu.com/p/ChpBrDsTtd/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  7 13:43:40 2019
  GsettingsChanges:

  InstallationDate: Installed on 2019-07-21 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

alsa-ucm-conf debdiff for focal

** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/pulseaudio/+bug/1891461/+attachment/5402455/+files/alsa-ucm-conf_1.2.2-1ubuntu0.2.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/1891461

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
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:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

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

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

[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

alsa-ucm-conf debdiff for groovy

** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/pulseaudio/+bug/1891461/+attachment/5402454/+files/alsa-ucm-conf_1.2.2-1ubuntu3.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/1891461

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
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:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

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

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

[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

alsa-lib debdiff for groovy

** Patch added: "alsa-lib_1.2.2-2.3ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/pulseaudio/+bug/1891461/+attachment/5402432/+files/alsa-lib_1.2.2-2.3ubuntu3.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/1891461

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
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:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

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

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

[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620

[Kai-Heng Feng]

alsa-lib debdiff for focal

** Patch added: "alsa-lib_1.2.2-2.1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/pulseaudio/+bug/1891461/+attachment/5402433/+files/alsa-lib_1.2.2-2.1ubuntu1.1.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/1891461

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in alsa-lib package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
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:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its 
chipset. Instead, it's equipped with two USB audio devices, "Main", which is 
for internal speaker and front headset, and "Rear", which is for rear panel 
I/Os.

  However, both USB audio don't really work out of the box. Issues and
  fixes will be described together below.

  [Fix for alsa-lib]
  1) Both USB audio devices don't have S/PDIF port, so we need to disable them:
  
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb

  [Fix for alsa-ucm-conf]
  2) PulseAudio doesn't assign the correct stream for "Main" device, audio 
output stays at "Speaker" after "Headset" is selected. So we need UCM to let 
PulseAudio understand correct stream assignment.
  In addition to that, in order to not let headset port availability invalidate 
speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" 
logically:
  https://github.com/alsa-project/alsa-ucm-conf/pull/42

  [Fix for PulseAudio]
  3) USB audio devices, UAC v2 and v3, support jack detection (insertion 
control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack 
detection doesn't work at userspace level. We need to let PulseAudio be aware 
those jacks:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b

  4) When a headset gets plugged, PulseAudio switches the profile from 
"Speaker" to "Headset" automatically. However, when headset gets unplugged, 
PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" 
profile. We need to fix priorities for profiles that are created from UCM to 
avoid the problem:
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f

  [Test]
  Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are 
all selectable. Sound comes out from speaker even if "Headphone" is chosen. 
Microphone is already selected though there's no microphone plugged.

  With the above fix all applied, open Gnome Control Center -> Sound tab.
  Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down 
menu.
  Plug a headset to front port, "Headphone" and "Microphone" appears and 
automatically becomes default. Unplug the headset, sink switches back to 
"Speaker", and source switches to none.
  Plug line-in, line-out and microphone to the rear panel, jack detection works 
for all three ports, and they all work correctly. Unplug rear line-in, line-out 
or microphone makes the option in dropdown menu disappears.

  On other systems, nothing changed.

  [Regression Potential]
  For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match 
kernel provided profile name, so no other device will be affected.

  For fix 3), if there are UAC v2/v3 devices claim to support jack detection 
but don't really support it, this will make the PulseAudio consider its 
availability to "no".
  AFAIK, the USB audios that have jack ports are mostly docking stations, which 
already have their own UCM profiles or PulseAudio profile-sets, so they are 
unaffected by this change.
  If we ever see this kind of regression, the proper fix is to disable jack 
detection from kernel side.

  For fix 4), if user depends on the old behavior (i.e. switch to
  another card while other profiles are still available), this will
  bring a behavioral change. However, all available profiles will still
  be available after the fix, so users can still be chose the preferred
  profile from the g-c-c dropdown menu.

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

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

[Desktop-packages] [Bug 1891987] [NEW] epson stylus photo rx560 is detected, added, but when printing, task is ending up immediatelly with success

[Didier Roche]

Public bug reported:

Tried with both manufacturer and gutenprint driver:

1. plug an epson stylus photo rx560 via usb
2. add the driver (manufacturer first, retried with gutenprint) autodetected 
our gtk ubuntu specific application.
3. Tried to print with multiple apps: the task is queued and then immediately 
terminated with success. Nothing is printed.


$ lsmod | grep usb
usb_storage77824  1 uas
usblp  24576  0
btusb  57344  0
btrtl  24576  1 btusb
btbcm  16384  1 btusb
btintel24576  1 btusb
bluetooth 581632  31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
usbhid 57344  0
hid   131072  2 usbhid,hid_generic

Logs when adding the printer:
$ tail -f /var/log/syslog 
Aug 18 09:36:00 casanier kernel: [ 2570.342143] usb 1-1: new high-speed USB 
device number 10 using xhci_hcd
Aug 18 09:36:00 casanier kernel: [ 2570.501144] usb 1-1: New USB device found, 
idVendor=04b8, idProduct=0827, bcdDevice= 1.00
Aug 18 09:36:00 casanier kernel: [ 2570.501150] usb 1-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Aug 18 09:36:00 casanier kernel: [ 2570.501154] usb 1-1: Product: USB2.0 
MFP(Hi-Speed)
Aug 18 09:36:00 casanier kernel: [ 2570.501157] usb 1-1: Manufacturer: EPSON
Aug 18 09:36:00 casanier kernel: [ 2570.501159] usb 1-1: SerialNumber: 
LH1010609180813040
Aug 18 09:36:00 casanier kernel: [ 2570.514421] usblp 1-1:1.1: usblp0: USB 
Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0827
Aug 18 09:36:00 casanier kernel: [ 2570.516384] usb-storage 1-1:1.2: USB Mass 
Storage device detected
Aug 18 09:36:00 casanier kernel: [ 2570.516676] scsi host5: usb-storage 1-1:1.2
Aug 18 09:36:00 casanier systemd[1]: Started Configure Plugged-In Printer.
Aug 18 09:36:00 casanier udev-configure-printer: add usb-001-010
Aug 18 09:36:00 casanier udev-configure-printer: device devpath is 
/devices/pci:00/:00:14.0/usb1/1-1
Aug 18 09:36:00 casanier udev-configure-printer: Device already handled
Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: 
Main process exited, code=exited, status=1/FAILURE
Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: 
Failed with result 'exit-code'.
Aug 18 09:36:01 casanier kernel: [ 2571.538832] scsi 5:0:0:0: Direct-Access 
EPSONStylus Storage   1.00 PQ: 0 ANSI: 2
Aug 18 09:36:01 casanier kernel: [ 2571.539702] sd 5:0:0:0: Attached scsi 
generic sg0 type 0
Aug 18 09:36:01 casanier kernel: [ 2571.545241] sd 5:0:0:0: Power-on or device 
reset occurred
Aug 18 09:36:01 casanier kernel: [ 2571.601212] sd 5:0:0:0: [sda] Attached SCSI 
removable disk
^C
$ ls -l /dev/usb/lp0 
crw-rw 1 root lp 180, 0 août  18 09:36 /dev/usb/lp0
$ ls -l /dev/bus/usb/*/*
crw-rw-r--  1 root root189,   0 août  18 08:53 /dev/bus/usb/001/001
crw-rw-r--  1 root root189,   1 août  18 08:53 /dev/bus/usb/001/002
crw-rw-r--  1 root root189,   2 août  18 08:53 /dev/bus/usb/001/003
crw-rw-r--  1 root root189,   3 août  18 08:53 /dev/bus/usb/001/004
crw-rw  1 root plugdev 189,   4 août  18 08:53 /dev/bus/usb/001/005
crw-rw-r--  1 root root189,   5 août  18 08:53 /dev/bus/usb/001/006
crw-rw-r--+ 1 root lp  189,   9 août  18 09:36 /dev/bus/usb/001/010
crw-rw-r--  1 root root189, 128 août  18 08:53 /dev/bus/usb/002/001
$ sudo usb_printerid /dev/usb/lp0
GET_DEVICE_ID string:
MFG:EPSON;CMD:ESCPL2,BDC,D4,D4PX,ESCPR1;MDL:Stylus Photo 
RX560;CLS:PRINTER;DES:EPSON Stylus Photo RX560;
$ lpinfo -v
file cups-brf:/
network socket
network lpd
network http
network beh
network https
network ipp
direct hp
network ipps
direct usb://EPSON/Stylus%20Photo%20RX560?serial=LH1010609180813040&interface=1
direct hpfax

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CupsErrorLog:
 W [18/Aug/2020:09:01:38 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Stylus-Photo-RX560-Gray..\' already exists
 W [18/Aug/2020:09:01:38 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'Stylus-Photo-RX560-RGB..\' already exists
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 18 09:37:40 2020
InstallationDate: Installed on 2020-04-24 (115 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: device for EPSON-Stylus-Photo-RX560: 
usb://EPSON/Stylus%20Photo%20RX560?serial=LH1010609180813040&interface=1
MachineType: Entroware Kratos
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON-Stylus-Photo-RX560.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON-Stylus-Photo-RX560.ppd: Permission denied
ProcEnviron:

[Desktop-packages] [Bug 1891867] Re: zfs not correctly imported at boot

[Didier Roche]

Please run apport-collect to attach logs so that we can debug your setting.
@baling: why subscribing zsys to this bu? There is no mention of zsys being 
used here, it seems directly a manual zfs setup.

** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)

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

Title:
  zfs not correctly imported at boot

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  On a fresh and up-to-date Ubuntu 20.04 amd64 installation I configured
  two encrypted partitions on the same hdd. On these I created a
  stripped zpool. After login I can import and mount the pool without
  problems, but the at-boot import fails after the first partitions is
  available and never tried again.

  zpool version:
  zfs-0.8.3-1ubuntu12.2
  zfs-kmod-0.8.3-1ubuntu12.2
  uname -a:
  Linux hostname 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
  systemd --version
  systemd 245 (245.4-4ubuntu3.2)
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 
default-hierarchy=hybrid

  Relevant logs:
  Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte 
logical blocks: (2.00 TB/1.82 TiB)
  Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Write Protect is off
  Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
  Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read 
cache: enabled, doesn't support DPO or FUA
  Aug 17 07:12:25 hostname kernel:  sdb: sdb1 sdb2
  Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
  Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found ordering 
cycle on cryptsetup.target/start
  Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found 
dependency on systemd-cryptsetup@vol\x2dswap_crypt.service/start
  Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found 
dependency on systemd-random-seed.service/start
  Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found 
dependency on zfs-mount.service/start
  Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found 
dependency on zfs-import.target/start
  Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found 
dependency on zfs-import-cache.service/start
  Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Job 
cryptsetup.target/start deleted to break ordering cycle starting with 
zfs-import-cache.service/start
  Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-mount.service/start
  Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import.target/start
  Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import-cache.service/start
  Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-mount.service/start
  Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import.target/start
  Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import-cache.service/start
  Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-mount.service/start
  Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import.target/start
  Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import-cache.service/start
  Aug 17 07:12:26 hostname systemd[1]: Starting Cryptography Setup for 
sdb1_crypt...
  Aug 17 07:12:26 hostname systemd[1]: Starting Cryptography Setup for 
sdb2_crypt...
  Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-mount.service/start
  Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import.target/start
  Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on 
zfs-import-cache.service/start
  Aug 17 07:12:32 hostname systemd[1]: Finished Cryptography Setup for 
sdb2_crypt.
  Aug 17 07:12:32 hostname systemd[1]: Reached target Block Device Preparation 
for /dev/mapper/sdb2_crypt.
  Aug 17 07:12:32 hostname zpool[1887]: cannot import 'sdb': no such pool or 
dataset
  Aug 17 07:12:32 hostname zpool[1887]: Destroy and re-create the pool 
from
  Aug 17 07:12:32 hostname zpool[1887]: a backup source.
  Aug 17 07:12:32 hostname systemd[1]: zfs-import-cache.service: Main process 
exited, code=exited, status=1/FAILURE
  Aug 17 07:12:32 hostname systemd[1]: zfs-import-cache.service: Failed with 
result 'exit-code'.
  Aug 17 07:12:34 hostname systemd[1]: Finished Cryptography Setup for 
sdb1_crypt.
  Aug 17 07:12:34 hostname systemd[1]: Reached target Block Device Preparation 
for /dev/mapper/sdb1_crypt.

To manage notifications about this bug go to: