date:20200831

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

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

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

Title:
  Some fonts are corrupted

Status in evince package in Ubuntu:
  Expired

Bug description:
  Hello
  Some of cyrillic fonts is corrupted, some isn't. The same issue is in xpdf. 
It's ok in mupdf
  2435491_10-11-2016.pdf - example file

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  9 20:19:32 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-06 (34 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  KernLog:
   
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

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

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

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in gnome-session package in Ubuntu:
  Expired

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1884380] Re: screen lock is not working

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

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

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

Title:
  screen lock is not working

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  the lock screen is not working (when I press the button it try to lock
  the screen bot nothgin happens)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.19
  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
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 20 21:24:46 2020
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2020-06-15  21:29:13
   Requested-By: talgat (1000)
   Upgrade: netplan.io:amd64 (0.99-0ubuntu3~20.04.1, 0.99-0ubuntu3~20.04.2), 
skypeforlinux:amd64 (8.61.0.77, 8.61.0.95), libfwupdplugin1:amd64 (1.3.9-4, 
1.3.9-4ubuntu0.1), libfwupd2:amd64 (1.3.9-4, 1.3.9-4ubuntu0.1), 
libnetplan0:amd64 (0.99-0ubuntu3~20.04.1, 0.99-0ubuntu3~20.04.2), fwupd:amd64 
(1.3.9-4, 1.3.9-4ubuntu0.1)
   Remove: fwupd-signed:amd64 (1.27+1.3.9-4)
   End-Date: 2020-06-15  21:30:16
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1885998] Re: Unable to use fingerprint login

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

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

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

Title:
  Unable to use fingerprint login

Status in libfprint package in Ubuntu:
  Expired

Bug description:
  I'm using ubuntu 20.04 LTS on ThinkPad X390.
  When I'm trying to enable fingerprint login, there's an error:
  GDBus.Error:net.reactivated.Fprint.Error.Internal:Open failed with error: The 
driver encountered a protocol error with the divice.

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

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

[Desktop-packages] [Bug 1886046] Re: ubuntu on wayland logs out user when screen locks

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

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

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

Title:
  ubuntu on wayland logs out user when screen locks

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

Bug description:
  WHen using 
   - Ubuntu on Wayland
   - dash to panel
   - arc menu
   - firefox (with Gnome extension, Grammarly) 

  when I leave the computer idle and the screen locks, mostly when
  returning to the computer the user is logged out and a new session is
  created through a selection of user and password entry, rather than
  continuing the session.

  This is most unproductive
  I allowed the system to report this with the automatic reporting tool, and 
this has been occurring for over a month.

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

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

[Desktop-packages] [Bug 1893719] [NEW] Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF

2020-08-31 Thread Chih-Hsyuan Ho

Public bug reported:

[Impact]

 * We were advised by Synaptics to upgrade the existing libfprint in the
archive to include sensor support for 0xE9 and 0xDF as highlighted in
the following commits:

https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a

[Test Case]

 * We have several OEM platforms with these Synaptics sensors enabled
with Focal and they can be used to validate these changes.

[Regression Potential]

 * Regression potential for an updated libfprint with these new PIDs is
low

[Other Info]

 None

** Affects: oem-priority
 Importance: Low
 Status: New

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


** Tags: oem-priority

** Changed in: oem-priority
   Importance: Undecided => Low

** Also affects: oem-priority/focal
   Importance: Undecided
   Status: New

** No longer affects: oem-priority/focal

** Tags added: oem-priority

** Information type changed from Proprietary to Public

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

** Description changed:

  [Impact]
  
-  * We were advised by Synaptics to upgrade the existing libfprint in the
- archive to include sensor support for 0xE9 and 0xDF:
+  * We were advised by Synaptics to upgrade the existing libfprint in the
+ archive to include sensor support for 0xE9 and 0xDF as highlighted in
+ the following commits:
+ 
  
https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a
  
  [Test Case]
  
-  * We have several OEM platforms with these Synaptics sensors enabled
+  * We have several OEM platforms with these Synaptics sensors enabled
  with Focal and they can be used to validate these changes.
  
  [Regression Potential]
  
-  * Regression potential for an updated libfprint with these new PIDs is
+  * Regression potential for an updated libfprint with these new PIDs is
  low
  
  [Other Info]
-  
-  None
+ 
+  None

** Summary changed:

- Add support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF
+ Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 
0xDF

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

Title:
  Request for adding support for Synaptics fingerprint reader sensors:
  0xE9 and 0xDF

Status in OEM Priority Project:
  New
Status in libfprint package in Ubuntu:
  New

Bug description:
  [Impact]

   * We were advised by Synaptics to upgrade the existing libfprint in
  the archive to include sensor support for 0xE9 and 0xDF as highlighted
  in the following commits:

  
https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a

  [Test Case]

   * We have several OEM platforms with these Synaptics sensors enabled
  with Focal and they can be used to validate these changes.

  [Regression Potential]

   * Regression potential for an updated libfprint with these new PIDs
  is low

  [Other Info]

   None

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

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

2020-08-31 Thread Anthony Wong

** Also affects: hwe-next
   Importance: Undecided
   Status: New

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

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/hwe-next/+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 1893704] Re: Very slow execution of boot and other tasks on an Atom N270

There's a large number of possible reasons for the slowness here. Indeed
maybe try a lighter version like:

http://cdimage.ubuntu.com/xubuntu/releases/18.04.5/release/xubuntu-18.04.5-desktop-i386.iso

** Summary changed:

- very slow execution of boot and other tasks
+ Very slow execution of boot and other tasks on an Atom N270

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

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  Very slow execution of boot and other tasks on an Atom N270

Status in Ubuntu:
  Won't Fix

Bug description:
  problems with time taken to execute tasks, perhaps as a result of
  cumulative updates over several lts editions.i am a complete novice,
  sorry I cannot provide more specific information.With more recent
  updates,a lot of time seemed to be spent loading? generic files one
  after another,for no apparent reason,{just watching update details in
  progress window}what I think is needed is a clean install, but I do
  not know how to do that and maintain data etc.The computer is a small
  netbook,Medion E1210.,probably needs a lighter version.

  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 i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 31 22:47:07 2020
  DistUpgraded: 2020-08-27 12:21:54,637 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GSE Express 
Integrated Graphics Controller [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [1462:0110]
  MachineType: MEDION E1210
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=38a83982-ae1b-4b05-bf17-ca55d6630e0a ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-08-27 (4 days ago)
  dmi.bios.date: 07/16/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E1210
  dmi.board.vendor: MEDION
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd07/16/2008:svnMEDION:pnE1210:pvrVer.001:rvnMEDION:rnE1210:rvrVer.001:cvnMEDION:ct3:cvrVer.001:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: E1210
  dmi.product.version: Ver.001
  dmi.sys.vendor: MEDION
  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: Wed Aug 26 22:14:29 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1220 
   vendor CPT
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1893693] Re: Unable to scroll gnome app list

Please open the 'Extensions' app and try disabling 'Ubuntu Dock'. Now
you will get the regular GNOME dock. Does this bug still happen after
that?

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

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

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

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

Title:
  Unable to scroll gnome app list

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

Bug description:
  I'm unable to scroll from page 1 to 2 in all apps under the gnome app
  list. Changing the dock from left side to bottom or right side solves
  the issue. Ubuntu 20.04 fresh install. See here for same issue:
  https://askubuntu.com/questions/1241165/should-i-report-show-
  applications-not-scrolling-as-a-bug

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia 
wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 22:37:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (39 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working

2020-08-31 Thread Gabriel Ramirez

** Attachment added: "sosreport-gabes-desky-1893579-2020-08-31-swehovc.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+attachment/5406318/+files/sosreport-gabes-desky-1893579-2020-08-31-swehovc.tar.xz

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

Title:
  Ctrl + Alt + T and Fn keys not working

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  The refered key combinations are no longer working on my desktop. The first 
one refers to opening the terminal. And the second one should work in 
combination with F2 or F3 or some other similars for incresing the volumen, or 
modifying brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-05 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-terminal 3.36.2-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1893686] Re: [nvidia] Some apps show semi-random corruption

Thanks for the bug report.

Are you able to provide a screenshot of the full desktop showing corrupt
and non-corrupt apps side by side?


** Summary changed:

- Some apps show semi-random corruption
+ [nvidia] Some apps show semi-random corruption

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

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

** Tags added: nvidia

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [nvidia] Some apps show semi-random corruption

Status in gtk+3.0 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  NVidia drivers in Ubuntu 20.04 show corruption in certain
  applications. Most egregious bug appears to be "Ubuntu Software
  Center" which is almost completely transparent and unusable.

  Also see occasional corruption in window decorations in other apps,
  namely Gnome Tweaks as a prime example.

  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: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 13:33:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7]
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729]
  InstallationDate: Installed on 2020-06-25 (67 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Alienware Alienware Aurora R8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.12
  dmi.board.name: 02XRCM
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R8
  dmi.product.sku: 08F7
  dmi.product.version: 1.0.12
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/gtk+3.0/+bug/1893686/+subscriptions

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

[Desktop-packages] [Bug 1893658] Re: I installed Ubuntu 20.04.1 Yesterday and Copied my backup from my mac so I did't shut down the night before and It is up from theinstallation i.e. about 35 hours f

While the memory usage is high please run:

  ps auxw > ps.txt
  free -m > free.txt

and then attach the resulting text files here.

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

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

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

Title:
  I installed Ubuntu 20.04.1 Yesterday and Copied my backup from my mac
  so I did't shut down the night before and It is up from
  theinstallation i.e. about 35 hours from installation, and I have
  installed multiple browsers, MS Teams, Skype, VSCode Insides (Two
  instances running), with two terminal window, It is eating memory(RAM)
  like hell along with SWAP. Both are full

Status in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 20.04.1 Yesterday and Copied my backup from my mac
  so I did't shut down the night before and It is up from
  theinstallation i.e. about 35 hours from installation, and I have
  installed multiple browsers, MS Teams, Skype, VSCode Insides (Two
  instances running), with two terminal window, It is eating memory(RAM)
  like hell along with SWAP. Both are full

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  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.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 19:28:24 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-08-30 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working

2020-08-31 Thread Gabriel Ramirez

FWIW these updates seemed to have triggered this issue:

Upgrade: speech-dispatcher-espeak-ng:amd64 (0.10.1-1, 0.10.1-2),
gir1.2-lokdocview-0.1:amd64 (1:6.4.5-0ubuntu2, 1:7.0.1~rc1-0ubuntu1),
speech-dispatcher-audio-plugins:amd64 (0.10.1-1, 0.10.1-2),
libpam0g:amd64 (1.3.1-5ubuntu5, 1.3.1-5ubuntu6), alsa-topology-
conf:amd64 (1.2.2-1, 1.2.3-1), libreoffice-style-breeze:amd64
(1:6.4.5-0ubuntu2, 1:7.0.1~rc1-0ubuntu1), manpages:amd64 (5.07-1,
5.08-1), libqmi-proxy:amd64 (1.26.2-0.1, 1.26.4-0.1), libreoffice-
math:amd64 (1:6.4.5-0ubuntu2, 1:7.0.1~rc1-0ubuntu1), libfolks-
eds25:amd64 (0.14.0-1, 0.14.0-1build1), gnome-control-center-data:amd64
(1:3.37.3-1ubuntu1, 1:3.37.90-1ubuntu2), evolution-data-server-
common:amd64 (3.36.4-1build1, 3.37.90-1), fonts-noto-unhinted:amd64
(20200323-1, 20200323-1build1), libefivar1:amd64 (37-2ubuntu4, 37-5),
gnome-settings-daemon-common:amd64 (3.36.1-1ubuntu2, 3.37.0-1ubuntu1),
gnome-shell-extension-prefs:amd64 (3.36.4-1ubuntu1,
3.36.4-1ubuntu2~build1), gnome-calendar:amd64 (3.36.2-1,
3.36.2-1build1), libwin-hivex-perl:amd64 (1.3.19-1, 1.3.19-1build1),
qtbase5-dev-tools:amd64 (5.14.2+dfsg-5, 5.14.2+dfsg-6),
libavformat58:amd64 (7:4.3.1-1ubuntu1, 7:4.3.1-2ubuntu1),
python3-cupshelpers:amd64 (1.5.12-0ubuntu1, 1.5.12-0ubuntu2),
libpangoft2-1.0-0:amd64 (1.44.7-2ubuntu4, 1.46.0-2),
libpangoft2-1.0-0:i386 (1.44.7-2ubuntu4, 1.46.0-2), bind9-dnsutils:amd64
(1:9.16.4-1ubuntu2, 1:9.16.6-2ubuntu1), timgm6mb-soundfont:amd64 (1.3-3,
1.3-4), libavfilter7:amd64 (7:4.3.1-1ubuntu1, 7:4.3.1-2ubuntu1), ubuntu-
desktop-minimal:amd64 (1.454, 1.455), gnome-contacts:amd64 (3.36.1-1,
3.36.1-1build1), uno-libs-private:amd64 (1:6.4.5-0ubuntu2,
1:7.0.1~rc1-0ubuntu1), libedataserverui-1.2-2:amd64 (3.36.4-1build1,
3.37.90-1), libcups2:amd64 (2.3.3-2, 2.3.3-2ubuntu5), libcups2:i386
(2.3.3-2, 2.3.3-2ubuntu5), linux-headers-generic:amd64 (5.4.0.42.46,
5.8.0.16.18), libqt5test5:amd64 (5.14.2+dfsg-5, 5.14.2+dfsg-6), libdrm-
nouveau2:amd64 (2.4.102-1, 2.4.102-1ubuntu1), libdrm-nouveau2:i386
(2.4.102-1, 2.4.102-1ubuntu1), system-config-printer:amd64
(1.5.12-0ubuntu1, 1.5.12-0ubuntu2), libfolks-telepathy25:amd64
(0.14.0-1, 0.14.0-1build1), ffmpeg:amd64 (7:4.3.1-1ubuntu1,
7:4.3.1-2ubuntu1), libayatana-indicator3-7:amd64 (0.7.1-1, 0.8.1-1),
libridl-java:amd64 (1:6.4.5-0ubuntu2, 1:7.0.1~rc1-0ubuntu1), gnome-
control-center:amd64 (1:3.37.3-1ubuntu1, 1:3.37.90-1ubuntu2), linux-
libc-dev:amd64 (5.4.0-42.46, 5.8.0-16.17), libvirt-daemon-system-
systemd:amd64 (6.0.0-0ubuntu11, 6.6.0-1ubuntu2), libtype-tiny-perl:amd64
(1.010002-1, 1.010004-1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu2,
1.2.2-1ubuntu3), libuno-salhelpergcc3-3:amd64 (1:6.4.5-0ubuntu2,
1:7.0.1~rc1-0ubuntu1), libspeechd2:amd64 (0.10.1-1, 0.10.1-2),
libldap-2.4-2:amd64 (2.4.50+dfsg-1ubuntu3, 2.4.51+dfsg-1ubuntu1),
libldap-2.4-2:i386 (2.4.50+dfsg-1ubuntu3, 2.4.51+dfsg-1ubuntu1), speech-
dispatcher:amd64 (0.10.1-1, 0.10.1-2), libxapian30:amd64 (1.4.15-1,
1.4.17-1), libpam-modules:amd64 (1.3.1-5ubuntu5, 1.3.1-5ubuntu6),
libreofficekit-data:amd64 (1:6.4.5-0ubuntu2, 1:7.0.1~rc1-0ubuntu1), qt5
-gtk-platformtheme:amd64 (5.14.2+dfsg-5, 5.14.2+dfsg-6), slick-
greeter:amd64 (1.3.2+dfsg.1-2, 1.4.1+dfsg.1-1ubuntu1), plymouth-
themes:amd64 (0.9.4git20200323-0ubuntu6, 0.9.5-0ubuntu2),
libibverbs1:amd64 (29.0-1build1, 31.0-1), libreoffice-gtk3:amd64
(1:6.4.5-0ubuntu2, 1:7.0.1~rc1-0ubuntu1), foomatic-db-compressed-
ppds:amd64 (20200527-1, 20200820-1), libswresample3:amd64
(7:4.3.1-1ubuntu1, 7:4.3.1-2ubuntu1), libsystemd0:amd64 (246-2ubuntu1,
246.2-1ubuntu1), libsystemd0:i386 (246-2ubuntu1, 246.2-1ubuntu1),
libpulsedsp:amd64 (1:13.99.1-1ubuntu9, 1:13.99.1-1ubuntu10), xsane:amd64
(0.999-8ubuntu3, 0.999-9ubuntu1), linux-image-generic:amd64
(5.4.0.42.46, 5.8.0.16.18), libjuh-java:amd64 (1:6.4.5-0ubuntu2,
1:7.0.1~rc1-0ubuntu1), libpocketsphinx3:amd64
(0.8.0+real5prealpha+1-11ubuntu1

I've seen these messages in the syslog as well:
Aug 31 19:17:51 gabes-desky gnome-shell[9693]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Aug 31 19:17:51 gabes-desky gnome-shell[9693]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Aug 31 19:17:51 gabes-desky gnome-shell[9693]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

I'm attaching a sosreport from my machine affected by this

Thanks,
Gabe

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

Title:
  Ctrl + Alt + T and Fn keys not working

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  The refered key combinations are no longer working on my desktop. The first 
one refers to opening the terminal. And the second one should work in 
combination with F2 or F3 or some other similars for incresing the volumen, or 
modifying brightness.
  --- 
  ProblemType:

[Desktop-packages] [Bug 1893655] Re: Headphones connect but don't appear as audio output

Even if it's not that bug, please try the same workaround. Just delete
your personal audio config:

  cd ~/.config
  rm -rf pulse

and then log out and in again.

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

Title:
  Headphones connect but don't appear as audio output

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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

[Desktop-packages] [Bug 1893655] Re: Headphones connect but don't appear as audio output

Do you mean they don't appear in the audio device list at all, or they
just don't get used even when they're selected from the list? Either
way, bug 1866194 might be the answer and a fix for that should arrive in
20.04 in the coming weeks.

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

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

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

Title:
  Headphones connect but don't appear as audio output

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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

[Desktop-packages] [Bug 1893638] Re: X forgets middle mouse button exists

Also does the problem occur *without* the KVM?

** 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-server in Ubuntu.
https://bugs.launchpad.net/bugs/1893638

Title:
  X forgets middle mouse button exists

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Assuming this is the xorg package but could be wrong.

  Running a Logitech MX master 3 mouse, the middle mouse copy/paste
  isn't working out the box or is only working intermittently on boot.
  Using 'xinput --list-props 15' I'm seeing that the 'Middle Emulation
  Enabled (298)' is set to 0. If I set this to '1' by using 'xinput
  --set-prop 15 298 1' then turn the mouse off/on then I regain
  functionality. If I then switch to another computer attached to my KVM
  switch and back to this machine, the input is lost again. Attempting
  to set the default (299) value results in this error:

  X Error of failed request:  BadAccess (attempt to access private resource 
denied)
Major opcode of failed request:  131 (XInputExtension)
Minor opcode of failed request:  57 ()
Serial number of failed request:  20
Current serial number in output stream:  21

  I can script this to get around it, it's just messy and unnecessary

  
  Copy of output from xinput --list-props:

  Device 'Logitech MX Master 3':
Device Enabled (155):   1
Coordinate Transformation Matrix (157): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Natural Scrolling Enabled (291):   0
libinput Natural Scrolling Enabled Default (292):   0
libinput Scroll Methods Available (293):0, 0, 1
libinput Scroll Method Enabled (294):   0, 0, 0
libinput Scroll Method Enabled Default (295):   0, 0, 0
libinput Button Scrolling Button (296): 2
libinput Button Scrolling Button Default (297): 2
libinput Middle Emulation Enabled (298):0
libinput Middle Emulation Enabled Default (299):0
libinput Accel Speed (300): 0.00
libinput Accel Speed Default (301): 0.00
libinput Accel Profiles Available (302):1, 1
libinput Accel Profile Enabled (303):   1, 0
libinput Accel Profile Enabled Default (304):   1, 0
libinput Left Handed Enabled (305): 0
libinput Left Handed Enabled Default (306): 0
libinput Send Events Modes Available (276): 1, 0
libinput Send Events Mode Enabled (277):0, 0
libinput Send Events Mode Enabled Default (278):0, 0
Device Node (279):  "/dev/input/event8"
Device Product ID (280):1133, 16514
libinput Drag Lock Buttons (307):   
libinput Horizontal Scroll Enabled (308):   1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-30 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xfce4-settings 4.14.3-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1893638] Re: X forgets middle mouse button exists

You shouldn't need 'Middle Emulation' if you have a real middle button.
That emulation option just simulates a middle button when you press the
left and right buttons simultaneously.

Please run:

  xev

and then middle click in the little white window. Do you see in the text
produced that it mentions 'button 2' ?

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

Title:
  X forgets middle mouse button exists

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Assuming this is the xorg package but could be wrong.

  Running a Logitech MX master 3 mouse, the middle mouse copy/paste
  isn't working out the box or is only working intermittently on boot.
  Using 'xinput --list-props 15' I'm seeing that the 'Middle Emulation
  Enabled (298)' is set to 0. If I set this to '1' by using 'xinput
  --set-prop 15 298 1' then turn the mouse off/on then I regain
  functionality. If I then switch to another computer attached to my KVM
  switch and back to this machine, the input is lost again. Attempting
  to set the default (299) value results in this error:

  X Error of failed request:  BadAccess (attempt to access private resource 
denied)
Major opcode of failed request:  131 (XInputExtension)
Minor opcode of failed request:  57 ()
Serial number of failed request:  20
Current serial number in output stream:  21

  I can script this to get around it, it's just messy and unnecessary

  
  Copy of output from xinput --list-props:

  Device 'Logitech MX Master 3':
Device Enabled (155):   1
Coordinate Transformation Matrix (157): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Natural Scrolling Enabled (291):   0
libinput Natural Scrolling Enabled Default (292):   0
libinput Scroll Methods Available (293):0, 0, 1
libinput Scroll Method Enabled (294):   0, 0, 0
libinput Scroll Method Enabled Default (295):   0, 0, 0
libinput Button Scrolling Button (296): 2
libinput Button Scrolling Button Default (297): 2
libinput Middle Emulation Enabled (298):0
libinput Middle Emulation Enabled Default (299):0
libinput Accel Speed (300): 0.00
libinput Accel Speed Default (301): 0.00
libinput Accel Profiles Available (302):1, 1
libinput Accel Profile Enabled (303):   1, 0
libinput Accel Profile Enabled Default (304):   1, 0
libinput Left Handed Enabled (305): 0
libinput Left Handed Enabled Default (306): 0
libinput Send Events Modes Available (276): 1, 0
libinput Send Events Mode Enabled (277):0, 0
libinput Send Events Mode Enabled Default (278):0, 0
Device Node (279):  "/dev/input/event8"
Device Product ID (280):1133, 16514
libinput Drag Lock Buttons (307):   
libinput Horizontal Scroll Enabled (308):   1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-30 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xfce4-settings 4.14.3-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1893567] Re: Login name ellipsis/dot-dot-dot in GDM

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

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

Title:
  Login name ellipsis/dot-dot-dot in GDM

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently, my Ubuntu 20.04.1 login screen started showing my username
  as a dot-dot-dot, with a vertical scroll, despite being my user name
  only four letters (i.e.: kopa). It is the only user account in the
  system too.

  I've attached a screenshot of the login screen where the issue can be
  seen.

  GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No
  changes to its configuration were made.

  I can provide whatever extra information that could be useful in
  diagnosing this problem.

  Thank you.

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

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

[Desktop-packages] [Bug 1893709] Re: Very big text top bar and login screem whit zoom

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

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


** This bug has been marked a duplicate of bug 1892521
   Shell text is too big in mutter 3.36.4-0ubuntu0.20.04.2

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

Title:
  Very big text top bar and login screem whit zoom

Status in mutter package in Ubuntu:
  New

Bug description:
  After updating im-config to version 0.44-1ubuntu1.1 the top bar is
  shown with very large text and the login screen is zoomed. After doing
  several updating-restoring tests I have identified that the problem
  package is im-config. It only happens to me with the nvidia rtx 2060
  card and 440 driver. When I connect my monitor to the intel integrated
  graphics, the problem is solved.

  Will it be a conflict between the nvidia drivers and im-config?

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

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

[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

2020-08-31 Thread Eric Perret

I am seeing the same issue on 18.04.5 LTS

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

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

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

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

[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit

2020-08-31 Thread Eduardo

My apologies. I haven't been keeping up with my email and I just saw the
comments. Please close this bug report if there are existing solutions
for this one. I don't want to take up more of your time. As mentioned by
c-lobrano, I just changed the Gedit theme to another one. It's a
workaround, but it works well enough.

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

Title:
  Dark themes don't work well with highlighted current line in gedit

Status in GtkSourceView:
  New
Status in gtksourceview4 package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  In order to checkout out an old bug report I started gedit, enabled
  "Highlight current line" and changed the application theme to "Yaru-
  dark" The current line is highlighted correctly but the text is
  unreadable because it is too light. The text needs to be much darker.

  This is not a theme that I would normally use so I'm not too bothered
  about how the problem is fixed but this configuration makes gedit very
  difficult to use as you can't actually see the text that you're
  adding, changing or deleting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: yaru-theme-gtk 19.10.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 21 16:33:03 2019
  InstallationDate: Installed on 2019-05-17 (218 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago)

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

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

[Desktop-packages] [Bug 1893579] Re: Ctrl + Alt + T and Fn keys not working

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

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

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

Title:
  Ctrl + Alt + T and Fn keys not working

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  The refered key combinations are no longer working on my desktop. The first 
one refers to opening the terminal. And the second one should work in 
combination with F2 or F3 or some other similars for incresing the volumen, or 
modifying brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-05 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-terminal 3.36.2-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags: third-party-packages groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1893709] Re: Very big text top bar and login screem whit zoom

2020-08-31 Thread Javier

? Thank you very much.

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

Title:
  Very big text top bar and login screem whit zoom

Status in mutter package in Ubuntu:
  New

Bug description:
  After updating im-config to version 0.44-1ubuntu1.1 the top bar is
  shown with very large text and the login screen is zoomed. After doing
  several updating-restoring tests I have identified that the problem
  package is im-config. It only happens to me with the nvidia rtx 2060
  card and 440 driver. When I connect my monitor to the intel integrated
  graphics, the problem is solved.

  Will it be a conflict between the nvidia drivers and im-config?

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

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

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

And apologies for the multicomment spam but the output of apt-cache
policy libmutter-6-0

libmutter-6-0:
  Installed: 3.36.4-0ubuntu0.20.04.2
  Candidate: 3.36.4-0ubuntu0.20.04.2
  Version table:
 *** 3.36.4-0ubuntu0.20.04.2 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.1-3ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

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

Here's the output of `nvidia-smi`, FTR:

+-+
| NVIDIA-SMI 440.100  Driver Version: 440.100  CUDA Version: 10.2 |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  Quadro M2000M   Off  | :01:00.0  On |  N/A |
| N/A   43CP0N/A /  N/A |   1001MiB /  4043MiB |  0%  Default |
+---+--+--+

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

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

I should note that when I say "proprietary" above, I mean the nvidia-
driver-440 package.

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1893709] Re: Very big text top bar and login screem whit zoom

This kind of issue is way over my head, but given what you just wrote we
now know that it's not im-config related. Changing the affected package
to mutter, so the developers who work with that package can take a look.

** Package changed: im-config (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  Very big text top bar and login screem whit zoom

Status in mutter package in Ubuntu:
  New

Bug description:
  After updating im-config to version 0.44-1ubuntu1.1 the top bar is
  shown with very large text and the login screen is zoomed. After doing
  several updating-restoring tests I have identified that the problem
  package is im-config. It only happens to me with the nvidia rtx 2060
  card and 440 driver. When I connect my monitor to the intel integrated
  graphics, the problem is solved.

  Will it be a conflict between the nvidia drivers and im-config?

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

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

[Desktop-packages] [Bug 1893709] Re: Very big text top bar and login screem whit zoom

2020-08-31 Thread Javier

Thanks, I just tried disabling im-config and the problem actually seems
to persist. Investigating I have observed that the problem resides in
the dependencies "GObject data for mutter" and "Windows manager library
from mutter" that uses im-config (or at least it is visually inside im-
config in the graphical ubuntu updater. It is when updating these two
packages when the problem appears, if I restore those two packages it
solves.

** Attachment added: "Update promblem packages"
   
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893709/+attachment/5406304/+files/Captura%20de%20pantalla%20de%202020-09-01%2002-27-33.png

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

Title:
  Very big text top bar and login screem whit zoom

Status in mutter package in Ubuntu:
  New

Bug description:
  After updating im-config to version 0.44-1ubuntu1.1 the top bar is
  shown with very large text and the login screen is zoomed. After doing
  several updating-restoring tests I have identified that the problem
  package is im-config. It only happens to me with the nvidia rtx 2060
  card and 440 driver. When I connect my monitor to the intel integrated
  graphics, the problem is solved.

  Will it be a conflict between the nvidia drivers and im-config?

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

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

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

I'm updated fully as of today under 20.04 and have the same issue
described in OP with an NVIDIA M2000M in a Thinkpad P50 using the
proprietary drivers and 1 1080p monitor (the laptop panel) and 1 4k
monitor (Dell external).

#83 indicated that they changed things so that their PRIME settings were
"on demand" and that made things work for them, but my external monitor
just quits working when I change it to that.

Things work mostly as expected with the nouveau driver, but no scaling
really works under the proprietary driver. I would use the nouveau
driver but it seems very sluggish under any scaling factor.

That said, my issue isn't really about fractional scaling, FWIW. I want
to set the external display at 200% and set the internal one at 100%, a
configuration which doesn't require fractional. But doing this produces
200% on both panels reliably (and the percentage values in settings
reflect that both are set to 200%) under the proprietary drivers.

So right now I can effectively either choose from these three options:
a) use nouveau, make both displays work as I would like, but have a very
sluggish UI experience b) use proprietary and have text that's too small
to read for my old eyes on the 4K external monitor but have a usable
built-in display, or b) use proprietary to get reasonably sized text and
icons on the 4K external monitor but accept that the built-in monitor is
not very useful because its effective resolution is 960x540.

It seems that some people have gotten the combination of proprietary
NVIDIA drivers and scaling to work. I would try this on another system
to doublecheck but I don't have a machine handy with NVIDIA graphics
different than the one in my system (M2000M).

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

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

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

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

2.
Select the screen setup in gnome control center

3.
Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1893709] Re: Very big text top bar and login screem whit zoom

Btw, let's simply disable im-config to test:

* Open Language Support and select "none" as the Keyboard input method
system

* Reboot

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

Title:
  Very big text top bar and login screem whit zoom

Status in im-config package in Ubuntu:
  Incomplete

Bug description:
  After updating im-config to version 0.44-1ubuntu1.1 the top bar is
  shown with very large text and the login screen is zoomed. After doing
  several updating-restoring tests I have identified that the problem
  package is im-config. It only happens to me with the nvidia rtx 2060
  card and 440 driver. When I connect my monitor to the intel integrated
  graphics, the problem is solved.

  Will it be a conflict between the nvidia drivers and im-config?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893709/+subscriptions

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

[Desktop-packages] [Bug 1893709] Re: Very big text top bar and login screem whit zoom

Thanks for your report.

It sounds very odd to me that im-config would have anything to do with
the issue you are having. Especially the latest change, which only was a
tiny change to a .desktop file.

Does the problem disappear if you downgrade to version 0.44-1ubuntu1?

** Changed in: im-config (Ubuntu)
   Status: New => Incomplete

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

Title:
  Very big text top bar and login screem whit zoom

Status in im-config package in Ubuntu:
  Incomplete

Bug description:
  After updating im-config to version 0.44-1ubuntu1.1 the top bar is
  shown with very large text and the login screen is zoomed. After doing
  several updating-restoring tests I have identified that the problem
  package is im-config. It only happens to me with the nvidia rtx 2060
  card and 440 driver. When I connect my monitor to the intel integrated
  graphics, the problem is solved.

  Will it be a conflict between the nvidia drivers and im-config?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893709/+subscriptions

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

[Desktop-packages] [Bug 1893704] Re: very slow execution of boot and other tasks

2020-08-31 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  very slow execution of boot and other tasks

Status in xorg package in Ubuntu:
  New

Bug description:
  problems with time taken to execute tasks, perhaps as a result of
  cumulative updates over several lts editions.i am a complete novice,
  sorry I cannot provide more specific information.With more recent
  updates,a lot of time seemed to be spent loading? generic files one
  after another,for no apparent reason,{just watching update details in
  progress window}what I think is needed is a clean install, but I do
  not know how to do that and maintain data etc.The computer is a small
  netbook,Medion E1210.,probably needs a lighter version.

  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 i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 31 22:47:07 2020
  DistUpgraded: 2020-08-27 12:21:54,637 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GSE Express 
Integrated Graphics Controller [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [1462:0110]
  MachineType: MEDION E1210
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=38a83982-ae1b-4b05-bf17-ca55d6630e0a ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-08-27 (4 days ago)
  dmi.bios.date: 07/16/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E1210
  dmi.board.vendor: MEDION
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd07/16/2008:svnMEDION:pnE1210:pvrVer.001:rvnMEDION:rnE1210:rvrVer.001:cvnMEDION:ct3:cvrVer.001:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: E1210
  dmi.product.version: Ver.001
  dmi.sys.vendor: MEDION
  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: Wed Aug 26 22:14:29 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1220 
   vendor CPT
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1893709] [NEW] Very big text top bar and login screem whit zoom

2020-08-31 Thread Javier

Public bug reported:

After updating im-config to version 0.44-1ubuntu1.1 the top bar is shown
with very large text and the login screen is zoomed. After doing several
updating-restoring tests I have identified that the problem package is
im-config. It only happens to me with the nvidia rtx 2060 card and 440
driver. When I connect my monitor to the intel integrated graphics, the
problem is solved.

Will it be a conflict between the nvidia drivers and im-config?

** Affects: im-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gdm

** Tags added: gdm

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

Title:
  Very big text top bar and login screem whit zoom

Status in im-config package in Ubuntu:
  New

Bug description:
  After updating im-config to version 0.44-1ubuntu1.1 the top bar is
  shown with very large text and the login screen is zoomed. After doing
  several updating-restoring tests I have identified that the problem
  package is im-config. It only happens to me with the nvidia rtx 2060
  card and 440 driver. When I connect my monitor to the intel integrated
  graphics, the problem is solved.

  Will it be a conflict between the nvidia drivers and im-config?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893709/+subscriptions

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

[Desktop-packages] [Bug 1893704] [NEW] very slow execution of boot and other tasks

You have been subscribed to a public bug:

problems with time taken to execute tasks, perhaps as a result of
cumulative updates over several lts editions.i am a complete novice,
sorry I cannot provide more specific information.With more recent
updates,a lot of time seemed to be spent loading? generic files one
after another,for no apparent reason,{just watching update details in
progress window}what I think is needed is a clean install, but I do not
know how to do that and maintain data etc.The computer is a small
netbook,Medion E1210.,probably needs a lighter version.

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 i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Aug 31 22:47:07 2020
DistUpgraded: 2020-08-27 12:21:54,637 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GSE Express 
Integrated Graphics Controller [1462:0110]
   Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [1462:0110]
MachineType: MEDION E1210
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=38a83982-ae1b-4b05-bf17-ca55d6630e0a ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-08-27 (4 days ago)
dmi.bios.date: 07/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: E1210
dmi.board.vendor: MEDION
dmi.board.version: Ver.001
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MEDION
dmi.chassis.version: Ver.001
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd07/16/2008:svnMEDION:pnE1210:pvrVer.001:rvnMEDION:rnE1210:rvrVer.001:cvnMEDION:ct3:cvrVer.001:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: E1210
dmi.product.version: Ver.001
dmi.sys.vendor: MEDION
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: Wed Aug 26 22:14:29 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1220 
 vendor CPT
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: apport-bug bionic i386 ubuntu
-- 
very slow execution of boot and other tasks
https://bugs.launchpad.net/bugs/1893704
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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-08-31 Thread Lucas Chen Alba

I was having this issue, didn't gather much info on in, but I was on
Ubuntu 18.x LTS, my Dell Vostro was detecting 3 mics, when I actually
had only 1. I reinstalled Ubuntu, 20.04 now. At first glance it was
detecting the same mics and some buzz noise, same with the 18.x, but
then after the initial update, I restarted my pc and now it's all
working, and it only detects 1 mic

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Desktop-packages] [Bug 42571] Re: eog won't delete images on different volume

2020-08-31 Thread iBART

Still here... :o

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

Title:
  eog won't delete images on different volume

Status in Eye of GNOME:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released

Bug description:
  If you are viewing an image with eog and ask eog to delete the image
  (move to trash), then eog will fail to do so unless the image file
  resides on the same volume as /home/user. Instead, it just puts up a
  dialog box saying it failed to delete the image.

  What eog should do is what Nautilus does:

  (1) Move the file to ~/.Trash if the file lies on the same volume as
  ~/.

  (2) Move the file to  /mountpoint/.Trash-$USER if the volume is
  mounted at /mountpoint and .Trash-$USER exists.

  (3) If /mountpoint/.Trash-$USER does not exist and user has rwx
  permissions for /mounpoint/., then create /mountpoint/.Trash-$USER and
  do step (2).

  gthumb does (1) and (2) but not (3), while eog does only (1).

  The result is that the basic supplied applications in ubuntu/dapper
  for viewing and organizing images are both unable to delete images in
  a very common situation (e.g. when a user has a bunch of imags on a
  USB memory stick).

  I filed bug's in gnome's bugzilla a while ago, on both eog and gthumb.
  Because these have not yet been triaged, and because dapper's release
  is not far off, I am entering these bugs here. (I hope this is not bad
  procedure.) In my eog bug report on bugzilla, I also pointed out a
  one-line change in the source which would fix eog so that it at least
  does (2). The corresponding line of code in gthumb *looks* like it
  should do (3) also (according to the documentation of gnome-vfs), but
  fails to do (3).

  It may be that the failure to do (3) is not a bug in eog or gthumb.
  But the failure of eog to do (2) certainly is.

  The relevant bugzilla.gnome bugs are:

  http://bugzilla.gnome.org/show_bug.cgi?id=338653
  http://bugzilla.gnome.org/show_bug.cgi?id=339180

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

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2020-08-31 Thread Dominik Danieluk

The same issue here in Fedora32 gnome-shell 3.36.5. Alt+F2->(r) fixes
the issue for a while, but in some time it comes back. The mouse clicks
are inactive in the middle of the screen (horizontally), but seem to
work correctly on the left and right. For example in Chrome with 29 tabs
opened, first 11 tabs get correctly activated with the left click. The
tabs 12-20 are immune to the click and 21+ get again activated
correctly. of course the same thing happens in the other apps. For
example windows cannot be dragged when clicked within the 'dead' are,
however when clicked in first ~30% or last ~30% (horizontally) they are
dragged as expected. Let me know if you need any logs or other details.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893332] Re: LibreOffice dialogs are garbled

2020-08-31 Thread Heather Ellsworth

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

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

Title:
  LibreOffice dialogs are garbled

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Behaviour: The LibreOffice dialogs are completely unreadable, thus rendering 
the software useless.
  Expected: Normal display of the dialogs.

  See attached screenshot.

  Kubuntu 20.04 + Wayland
  Libreoffice:
  Version: 6.4.5.2
  Build ID: 1:6.4.5-0ubuntu0.20.04.1
  CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: kf5; 
  Locale: en-US (en_DE.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.5-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.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Aug 28 11:43:18 2020
  InstallationDate: Installed on 2019-09-20 (342 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919)
  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/1893332/+subscriptions

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

[Desktop-packages] [Bug 1893693] [NEW] Unable to scroll gnome app list

2020-08-31 Thread Anders Egeland

Public bug reported:

I'm unable to scroll from page 1 to 2 in all apps under the gnome app
list. Changing the dock from left side to bottom or right side solves
the issue. Ubuntu 20.04 fresh install. See here for same issue:
https://askubuntu.com/questions/1241165/should-i-report-show-
applications-not-scrolling-as-a-bug

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 31 22:37:56 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-07-22 (39 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Unable to scroll gnome app list

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm unable to scroll from page 1 to 2 in all apps under the gnome app
  list. Changing the dock from left side to bottom or right side solves
  the issue. Ubuntu 20.04 fresh install. See here for same issue:
  https://askubuntu.com/questions/1241165/should-i-report-show-
  applications-not-scrolling-as-a-bug

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia 
wl
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 22:37:56 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-22 (39 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/

@Ian, I meant that a snapped application, run as the current user, won't
be able to write to its $SNAP_DATA. I just verified that with:

snap run --shell chromium
cd $SNAP_DATA
touch foobar

and got "touch: cannot touch 'foobar': Permission denied"

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

Title:
  [snap] apparmor denials on /etc/chromium-browser/policies/

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  [1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/managed/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  [1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/recommended/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  Those denials don't appear to prevent the app from running. Still,
  they should be investigated and fixed if possible.

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

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

2020-08-31 Thread Thiago Marcello

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

Same issue here.
Ubuntu 20.04 LTS and Ubuntu 18.04 LTS

JBL Reflect Flow

Dell Latitude 3400

-- 
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 1891733] Re: Support better Arabic font

Verified the test case using language-selector-{common,gnome} 0.204.1
from focal-proposed.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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:
  Fix Committed
Status in language-selector source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  Arabic speaking users have requested better rendering of Arabic. This
  proposed upload addresses that wish. Related discussion is being held
  at .

  So how is this an SRUable bug fix and not just an enhancement which
  should go to -backports? Well, currently, if you install the Arabic
  language via Language Support, a couple of Arabic fonts packages are
  pulled. But even if you set an Arabic locale, those fonts won't make a
  difference. The explanation is that DejaVu fonts, which also are able
  to render Arabic, have higher fontconfig precedence. The user must
  mess with fontconfig themselves to change the effective font, which is
  a bug. (I can't tell if it ever worked as intended.)

  So to summarize: This is a combination of a bug fix and an
  enhancement.

  [Test Case]

  * Install the language-selector-{gnome,common} packages
    from focal-proposed.

  * Open the Language Support tool and install Arabic.

  * Open a terminal window and run this command:

    LC_CTYPE=ar_EG.UTF-8 fc-match -a | head -10

  * Find that Noto fonts are at the top of the list.

  [Regression risk]

  This will change the effective font for rendering Arabic for some
  users. But the user experience will be improved in those cases, not
  the opposite.

  The change in font will only happen for users with an Arabic locale.
  The risk that other users would be affected by the change is low.

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 1893686] Re: Some apps show semi-random corruption

2020-08-31 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Some apps show semi-random corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  NVidia drivers in Ubuntu 20.04 show corruption in certain
  applications. Most egregious bug appears to be "Ubuntu Software
  Center" which is almost completely transparent and unusable.

  Also see occasional corruption in window decorations in other apps,
  namely Gnome Tweaks as a prime example.

  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: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 13:33:16 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7]
   NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729]
  InstallationDate: Installed on 2020-06-25 (67 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Alienware Alienware Aurora R8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.12
  dmi.board.name: 02XRCM
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R8
  dmi.product.sku: 08F7
  dmi.product.version: 1.0.12
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1893686/+subscriptions

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

[Desktop-packages] [Bug 1893686] [NEW] Some apps show semi-random corruption

You have been subscribed to a public bug:

NVidia drivers in Ubuntu 20.04 show corruption in certain applications.
Most egregious bug appears to be "Ubuntu Software Center" which is
almost completely transparent and unusable.

Also see occasional corruption in window decorations in other apps,
namely Gnome Tweaks as a prime example.

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: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 31 13:33:16 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7]
 NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729]
InstallationDate: Installed on 2020-06-25 (67 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Alienware Alienware Aurora R8
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2020
dmi.bios.vendor: Alienware
dmi.bios.version: 1.0.12
dmi.board.name: 02XRCM
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
dmi.product.family: Alienware
dmi.product.name: Alienware Aurora R8
dmi.product.sku: 08F7
dmi.product.version: 1.0.12
dmi.sys.vendor: Alienware
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 corruption focal ubuntu
-- 
Some apps show semi-random corruption
https://bugs.launchpad.net/bugs/1893686
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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd

2020-08-31 Thread Dan Streetman

note there is only one xenial reverse-dep autopkgtest failure, for nfs-
utils on s390x, and that test has always failed and can be ignored.

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  Fix Committed
Status in rpcbind source package in Bionic:
  Fix Released
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.

  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved
  ports.

  [test case]

  start rpcbind and check which ports it is listening on, e.g.:

  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
  udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind

  each time rpcbind is restarted, it will be listening to a different
  'random' port.

  [regression potential]

  this adds a way to disable rpcbind from listening to the 'random'
  port. any regression would likely prevent rpcbind from starting, or
  may cause problems with the interaction between rpcinfo and rpcbind,
  as rpcinfo may use the random reserved port in some cases, as detailed
  in the Debian bug.

  [scope]

  This is needed only for Bionic and earlier.

  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved
  port.

  [other info]

  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time;
  there is no runtime parameter to allow the admin to choose the
  behavior.

  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why
  Debian introduced the -r parameter. So, when this -r parameter is
  backported to Bionic and earlier, we must retain the default behavior
  for those releases, which is for rpcbind to open the random reserved
  port.

  Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
  and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change 
the default to disabled.

  This allows 1) retaining the existing default behavior of rpcbind in x
  and b, while also 2) providing a mechanism to change that default for
  anyone who does *not* want remote calls to be enabled, and 3) allowing
  the mechanism to change the default to remain in place after an
  upgrade to Focal. Using the environment variable allows anyone to
  disable the remote calls in x and/or b, and then upgrade to Focal
  without breaking rpcbind or needing to remove the env var. After the
  upgrade to Focal, the environment variable (defined in
  /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored
  without any change needed to the rpcbind package in Focal or later.

  [original description]

  Binary package hint: cups

  cups 1.3.9-2ubuntu4
  From /var/log/cups/error_log:
  cups: unable to bind socket for address 127.0.0.1:631 - Address already in 
use.

  Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd
  when started.

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

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

[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd

2020-08-31 Thread Dan Streetman

ubuntu@lp304393-x:~$ dpkg -l|grep rpcbind
ii  rpcbind  0.2.3-0.2ubuntu0.1 
amd64converts RPC program numbers into universal addresses
ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
udp0  0 *:927   *:* 
13471/rpcbind   


same default behavior after upgrade:

ubuntu@lp304393-x:~$ dpkg -l|grep rpcbind
ii  rpcbind  0.2.3-0.2ubuntu0.16.04.1   
amd64converts RPC program numbers into universal addresses
ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind
ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
udp0  0 *:625   *:* 
14441/rpcbind   


with parameter added, random port disabled:

ubuntu@lp304393-x:~$ cat /etc/default/rpcbind 
RPCBIND_RMTCALL_DEFAULT_DISABLED=1

ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind
ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
ubuntu@lp304393-x:~$ 


with parameter commented, default behavior restored:

ubuntu@lp304393-x:~$ cat /etc/default/rpcbind 
#RPCBIND_RMTCALL_DEFAULT_DISABLED=1

ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind
ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
udp0  0 *:660   *:* 
14476/rpcbind   


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

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  Fix Committed
Status in rpcbind source package in Bionic:
  Fix Released
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.

  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved
  ports.

  [test case]

  start rpcbind and check which ports it is listening on, e.g.:

  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
  udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind

  each time rpcbind is restarted, it will be listening to a different
  'random' port.

  [regression potential]

  this adds a way to disable rpcbind from listening to the 'random'
  port. any regression would likely prevent rpcbind from starting, or
  may cause problems with the interaction between rpcinfo and rpcbind,
  as rpcinfo may use the random reserved port in some cases, as detailed
  in the Debian bug.

  [scope]

  This is needed only for Bionic and earlier.

  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved
  port.

  [other info]

  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time;
  there is no runtime parameter to allow the admin to choose the
  behavior.

  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why
  Debian introduced the -r parameter. So, when this -r parameter is
  backported to Bionic and earlier, we must retain the default behavior
  for those releases, which is for rpcbind to open the random reserved
  port.

  Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
  and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change 
the default to disabled.

  This allows 1) retaining the existing default behavior of rpcbind in x
  and b, while also 2) providing a mechanism to change that default for
  anyone who does *not* want remote calls to be enabled, and 3) allowing
  the mechanism to change the default to

[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier

2020-08-31 Thread Jack

Sorry - mixed my words - as you can see it's failing on an attempt to
retreive the remote *signatures* file, not the manifest file.   The
manifest is stored in standard class; the signatures file is stored in
DEEP_ARCHIVE class.

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

Title:
  Download of vol1 in validate_encryption_settings() fails when using S3
  glacier

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

Bug description:
  Duplicity version: 0.8.12.1612
  ubuntu 20.04 LTS
  python 3.8.2

  When i try to restart a backup which goes to S3 (via boto3) (use of:
  --s3-use-deep-archive or --s3-use-glacier) it fails:

  Last full backup date: Wed Apr 29 17:45:32 2020
  RESTART: Volumes 2 to 2 failed to upload before termination.
   Restarting backup at volume 2.
  Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when 
calling the GetObject operation: The operation is not valid for the object's 
storage class
  Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when 
calling the GetObject operation: The operation is not valid for the object's 
storage class

  This is because a file stored in glacier cannot be downloaded. I dont
  know if this known?

  To solve this: either skip validate_encryption_settings() when using
  any of this storage backends or introduce an option to skip the
  download manually (e.g. --skip-download-on-restart)

  I fixed it for me with manully skipping the
  validate_encryption_settings() function.

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

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

[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/

2020-08-31 Thread Ian Johnson

@osomon,

> $SNAP_DATA/policies is not writable by the snap, so the import of
existing policies won't work.

$SNAP_DATA is by definition writable, so I'm curious what led you to
think that it isn't? If it is showing up as read-only then that would be
a snapd bug. Perhaps you were running as non-root, as the directory is
root-owned and only writable by root ?

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

Title:
  [snap] apparmor denials on /etc/chromium-browser/policies/

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  [1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/managed/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  [1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/recommended/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  Those denials don't appear to prevent the app from running. Still,
  they should be investigated and fixed if possible.

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

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

[Desktop-packages] [Bug 1893569] Re: The mouse freezes

2020-08-31 Thread Leonidas S. Barbosa

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

Title:
  The mouse freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  The mouse freezes in the middle of work. I connected others and the
  same thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 30 20:44:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba Corporation HD Graphics 5500 [1179:f920]
 Subsystem: Toshiba Corporation Jet PRO [Radeon R5 M230 / R7 M260DX / 
Radeon 520 Mobile] [1179:f923]
  InstallationDate: Installed on 2020-06-15 (76 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA SATELLITE L50-B
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sr_RS
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8f2dae7e-98af-440c-adfc-c31f5c18bb4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 2.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTQE-00500DY4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: INVALID
  dmi.product.name: SATELLITE L50-B
  dmi.product.sku: INVALID
  dmi.product.version: PSKTQE-00500DY4
  dmi.sys.vendor: TOSHIBA
  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/1893569/+subscriptions

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

[Desktop-packages] [Bug 1891270] Re: Iranian calendar shows in Azerbaijani language

2020-08-31 Thread Danial Behzadi

I think ubiquity should generate the locale when Iran is selected.

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

Title:
  Iranian calendar shows in Azerbaijani language

Status in gnome-calendar package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  New

Bug description:
  I already installed Ubuntu 20.04.1 LTS  and set location on Iran during 
installation.
  After finishing installation successfully, I open the calendar by clicking at 
the top of the screen (where the clock is shown), I see the calendar with 
Azerbaijani names for month and weekdays.

  Such as "آقوست" for August and "جومعه آخشامی" for Thursday.

  But it should show in Iranian names such as "اوت" for August and
  "پنجشنبه" for Thursday.

  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

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

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

[Desktop-packages] [Bug 1891270] Re: Iranian calendar shows in Azerbaijani language

2020-08-31 Thread Danial Behzadi

`fa_IR.UTF-8` local is not installed by default. That's a bug!

** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Confirmed

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

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

Title:
  Iranian calendar shows in Azerbaijani language

Status in gnome-calendar package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  New

Bug description:
  I already installed Ubuntu 20.04.1 LTS  and set location on Iran during 
installation.
  After finishing installation successfully, I open the calendar by clicking at 
the top of the screen (where the clock is shown), I see the calendar with 
Azerbaijani names for month and weekdays.

  Such as "آقوست" for August and "جومعه آخشامی" for Thursday.

  But it should show in Iranian names such as "اوت" for August and
  "پنجشنبه" for Thursday.

  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

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

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

[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier

2020-08-31 Thread Jack

My incremental job uses the same parameters as the full, and it fails on
glacier/deep because duplicity tries to pull the remote manifest and
can't retrieve it - here's what I run:

duplicity /mnt/backup/src boto3+s3://BUCKETNAME/FOLDERNAME 
--file-prefix-archive archive-$(hostna
me -f)- --file-prefix-manifest manifest-$(hostname -f)- --file-prefix-signature 
signature-$(hostname -f)- --s3-use-deep-archive

...and here's the output:
Synchronizing remote metadata to local cache...
Copying 
signature-backup.HOSTNAME.com-duplicity-full-signatures.20200830T050003Z.sigtar.gpg
 to local cache.
Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when 
calling the GetObject operation: The operation is not valid for the object's 
storage class

It tries 4 more attempts and then fails completely.

I'm still not following the logic here anyways - wouldn't it be better
to store the signature files as as a standard class file, and allow the
metadata sync to proceed as usual...rather than just disabling metadata
sync for non-standard storage classes?  The implementation seems to be
inconsistent across AWS storage classes, and I can't get incrementals to
work at all with glacier deep.

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

Title:
  Download of vol1 in validate_encryption_settings() fails when using S3
  glacier

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

Bug description:
  Duplicity version: 0.8.12.1612
  ubuntu 20.04 LTS
  python 3.8.2

  When i try to restart a backup which goes to S3 (via boto3) (use of:
  --s3-use-deep-archive or --s3-use-glacier) it fails:

  Last full backup date: Wed Apr 29 17:45:32 2020
  RESTART: Volumes 2 to 2 failed to upload before termination.
   Restarting backup at volume 2.
  Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when 
calling the GetObject operation: The operation is not valid for the object's 
storage class
  Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when 
calling the GetObject operation: The operation is not valid for the object's 
storage class

  This is because a file stored in glacier cannot be downloaded. I dont
  know if this known?

  To solve this: either skip validate_encryption_settings() when using
  any of this storage backends or introduce an option to skip the
  download manually (e.g. --skip-download-on-restart)

  I fixed it for me with manully skipping the
  validate_encryption_settings() function.

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

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

[Desktop-packages] [Bug 1893674] [NEW] Firefox black screen blinking on kindle cloud reader

2020-08-31 Thread corrado venturini

Public bug reported:

Open kindle cloud reader, instead my book i see a blinking black screen as in 
attachment.
The problem does not happen on same PC, different partition running Ubuntu 
20.10 at same maintenance level but installed from an older ISO

corrado@corrado-n3-gg-0826:~$ inxi -Fx
System:Host: corrado-n3-gg-0826 Kernel: 5.4.0-42-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: N/A 
   Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 
 
   Mobo: Dell model: 0C1PF2 v: A00 serial:  
UEFI: Dell v: 1.5.0 date: 12/17/2019 
Battery:   ID-1: BAT0 charge: 34.3 Wh condition: 37.1/42.0 Wh (88%) model: 
SWD-ATL3.618 DELL WJPC403 
   status: Discharging 
CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 L2 cache: 6144 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046 
   Speed: 2545 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 2819 2: 
1115 3: 1142 4: 2527 5: 2577 6: 2706 
   7: 2036 8: 2047 
Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus ID: 00:02.0 
   Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus ID: 1-6:3 
   Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
   OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
20.1.5 direct render: Yes 
Audio: Device-1: Intel Smart Sound Audio vendor: Dell driver: snd_hda_intel 
v: kernel bus ID: 00:1f.3 
   Sound Server: ALSA v: k5.4.0-42-generic 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000 
   bus ID: 01:00.0 
   IF: enp1s0 state: down mac: 98:e7:43:59:19:19 
   Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter 
vendor: Dell driver: ath10k_pci 
   v: kernel port: 3000 bus ID: 02:00.0 
   IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 
   Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-10:4 
Drives:Local Storage: total: 476.94 GiB used: 8.54 GiB (1.8%) 
   ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB 
Partition: ID-1: / size: 31.25 GiB used: 8.49 GiB (27.2%) fs: ext4 dev: 
/dev/nvme0n1p3 
Swap:  ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: 
/dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 57.0 C mobo: N/A 
   Fan Speeds (RPM): cpu: 0 
Info:  Processes: 234 Uptime: 26m Memory: 7.55 GiB used: 1.49 GiB (19.7%) 
Init: systemd runlevel: 5 Compilers: 
   gcc: N/A Packages: 1810 Shell: Bash v: 5.0.17 inxi: 3.1.06 
corrado@corrado-n3-gg-0826:~$ apt policy firefox
firefox:
  Installed: 78.0.1+build1-0ubuntu1
  Candidate: 78.0.1+build1-0ubuntu1
  Version table:
 *** 78.0.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-n3-gg-0826:~$

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: firefox 78.0.1+build1-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-0ubuntu45
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  corrado1339 F pulseaudio
BuildID: 20200630195452
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 31 18:09:08 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:730
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-08-28 (3 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
IpRoute:
 default via 192.168.43.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.43.0/24 dev wlp2s0 proto kernel scope link src 192.168.43.222 metric 
600
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:730
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=78.0.1/20200630195452 (In use)
RunningIncompatibleAddons: False

[Desktop-packages] [Bug 1893674] Re: Firefox black screen blinking on kindle cloud reader

2020-08-31 Thread corrado venturini

retry attaching screencast

** Attachment added: "Screencast 2020-08-31 15:31:01.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893674/+attachment/5406177/+files/Screencast%202020-08-31%2015%3A31%3A01.mp4

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

Title:
  Firefox black screen blinking on kindle cloud reader

Status in firefox package in Ubuntu:
  New

Bug description:
  Open kindle cloud reader, instead my book i see a blinking black screen as in 
attachment.
  The problem does not happen on same PC, different partition running Ubuntu 
20.10 at same maintenance level but installed from an older ISO

  corrado@corrado-n3-gg-0826:~$ inxi -Fx
  System:Host: corrado-n3-gg-0826 Kernel: 5.4.0-42-generic x86_64 bits: 64 
compiler: gcc v: 9.3.0 Desktop: N/A 
 Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 
 
 Mobo: Dell model: 0C1PF2 v: A00 serial:  
UEFI: Dell v: 1.5.0 date: 12/17/2019 
  Battery:   ID-1: BAT0 charge: 34.3 Wh condition: 37.1/42.0 Wh (88%) model: 
SWD-ATL3.618 DELL WJPC403 
 status: Discharging 
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 L2 cache: 6144 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046 
 Speed: 2545 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 2819 
2: 1115 3: 1142 4: 2527 5: 2577 6: 2706 
 7: 2036 8: 2047 
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus ID: 00:02.0 
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus ID: 1-6:3 
 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
20.1.5 direct render: Yes 
  Audio: Device-1: Intel Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel bus ID: 00:1f.3 
 Sound Server: ALSA v: k5.4.0-42-generic 
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000 
 bus ID: 01:00.0 
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci 
 v: kernel port: 3000 bus ID: 02:00.0 
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 
 Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-10:4 
  Drives:Local Storage: total: 476.94 GiB used: 8.54 GiB (1.8%) 
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB 
  Partition: ID-1: / size: 31.25 GiB used: 8.49 GiB (27.2%) fs: ext4 dev: 
/dev/nvme0n1p3 
  Swap:  ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) 
dev: /dev/nvme0n1p2 
  Sensors:   System Temperatures: cpu: 57.0 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 234 Uptime: 26m Memory: 7.55 GiB used: 1.49 GiB (19.7%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: N/A Packages: 1810 Shell: Bash v: 5.0.17 inxi: 3.1.06 
  corrado@corrado-n3-gg-0826:~$ apt policy firefox
  firefox:
Installed: 78.0.1+build1-0ubuntu1
Candidate: 78.0.1+build1-0ubuntu1
Version table:
   *** 78.0.1+build1-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-gg-0826:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 78.0.1+build1-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-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1339 F pulseaudio
  BuildID: 20200630195452
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 18:09:08 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:730
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-08-28 (3 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  IpRoute:
   default via 192.168.43.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.43.0/24 dev wlp2s0

[Desktop-packages] [Bug 1842298] Re: Evince printing glitches on PDF documents from JHEP

2020-08-31 Thread Jonathan

I can confirm that this bug is no longer present in 20.04.

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

Title:
  Evince printing glitches on PDF documents from JHEP

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  Evince is unable to print PDF documents from the open-access journal
  JHEP. Example file:
  https://link.springer.com/content/pdf/10.1007%2FJHEP07%282016%29126.pdf
  (alternatively, go to
  https://link.springer.com/article/10.1007%2FJHEP07%282016%29126 and
  click Download).

  Expected behavior: When I open the file in evince, hit Ctrl+P and go
  to "Preview" or print the file, I expect to see the document properly
  rendered.

  Actual behavior: Both the print preview and the printed result are an
  unreadable mess.

  I have encountered this problem on every PDF file from JHEP that I
  tested, but didn't encounter this problem on any PDF file from any
  other source. Only printing and print preview are affected, reading
  and browsing the file works without issues. The problem persists when
  a different printer is selected (in particular, it also appears when I
  choose "print to file"). I printed the same file on Windows using
  PDFXchange editor, where no problems appeared, suggesting that the
  file itself is not  the root of the issue here.

  Affected package: evince

  Version information:
  Ubuntu 18.04.3 LTS, Evince version 3.28.4-0ubuntu1.2

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

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

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

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

-- 
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:
  Confirmed

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 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

2020-08-31 Thread Brian Murray

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

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

Title:
  gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR:
  Error: No valid stylesheet found for 'Yaru/gnome-shell.css'

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  An upgrade to gnome-shell on 18.10 was recently released which made it
  impossible for me to log in to my DE.  Upon typing my password, the
  gdm screen would disappear, only to re-appear a few seconds later.
  This was not a password typo as I didn't get the usual msg to that
  effect (I made at least 5 attempts, carefully typing my passwd).

  I solved the issue by switching to a terminal screen (using
  CTRL+ALT+F6 I believe), logging in, analyzing recent changes through
  /var/log/apt/history.log.  Beside the gnome-shell packages, a handful
  of Wayland packages were also upgraded as follows (I use X.org so left
  those alone):

  Start-Date: 2018-12-19  09:13:20
  Commandline: aptdaemon role='role-commit-packages' sender=':1.8821'
  Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), 
keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 
2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 
3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), 
libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), 
gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), 
gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), 
libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), 
libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1)
  End-Date: 2018-12-19  09:13:31

  I solved the issue by downgrading the just-updated gnome-shell
  packages as follows:

  sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome-
  shell=3.30.1-2ubuntu1

  Having done this, I switched back to the GDM screen and managed to log
  in as normal.  I couldn't find any smoking gun in system logs but
  please let me know if there's a way to collect any useful debug info.

  One thing I'm using which differs from stock 18.10 is the System76
  "Pop" theme (let me know if you need details).  Presumably a theme
  cannot cause such issues and/or if the new version of gnome-shell is
  meant to be incompatible with themes other than Yaru, this should be
  clearly documented.

  The problematic versions are the "Candidate" shown below:

  gnome-shell:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1.18.10.1
    Version table:
   3.30.1-2ubuntu1.18.10.1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.1-2ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-shell-common:
    Installed: 3.30.1-2ubuntu1
    Candidate: 3.30.1-2ubuntu1.18.10.1
    Version table:
   3.30.1-2ubuntu1.18.10.1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 
Packages
   *** 3.30.1-2ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages
  100 /var/lib/dpkg/status

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

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

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

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

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

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

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound cuts off and comes back on every 10 or so minutes. I have tried
  the usual stuff like purging and removing alsa and pulseaudio and
  restarting, forcing alsa reload, killing pulseaudio and starting
  again, etc.

  Here is the output from 
  cat /var/log/syslog* | grep -i pulse

  gnome-shell[7674]:
  [8240:8240:0516/223421.641830:ERROR:pulse_util.cc(300)] pa_operation
  is nullptr.

  I have attached alsa information also as an attachment

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

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

[Desktop-packages] [Bug 1892747] Re: [Dell Vostro 3446] Ubuntu hangs while changing display brightness from keyboard shortcut

2020-08-31 Thread Sujit Kumar

I found this question on askUbuntu:
https://askubuntu.com/questions/1242205/ubuntu-20-04-hangs-when-
changing-brightness-level-with-keyboard . Someone else is also facing
the same bug. Does this mean the bug can be Confirmed now?

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

Title:
  [Dell Vostro 3446] Ubuntu hangs while changing display brightness from
  keyboard shortcut

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Whenever I change my display's brightness using keyboard shortcuts (For me 
F11 & F12), Ubuntu hangs a little, the brightness is changed immediately, but 
everything (except the mouse) hangs while it is being changed and sometimes for 
quite some time after. There is no problem doing it through the system. 
Changing volume using keyboard shortcuts works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-22 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

assigning pcsc-lite back to sarnold for the decision if you really
need/want it for "pcscd" or not.

** Changed in: pcsc-lite (Ubuntu)
 Assignee: (unassigned) => Seth Arnold (seth-arnold)

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  Incomplete
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian policy.

  [Maintenance]
  The desktop team will subscribe to bugs, however it is

[Desktop-packages] [Bug 1891733] Re: Support better Arabic font

2020-08-31 Thread Timo Aaltonen

Hello Gunnar, or anyone else affected,

Accepted language-selector into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.204.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: language-selector (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

-- 
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:
  Fix Committed
Status in language-selector source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  Arabic speaking users have requested better rendering of Arabic. This
  proposed upload addresses that wish. Related discussion is being held
  at .

  So how is this an SRUable bug fix and not just an enhancement which
  should go to -backports? Well, currently, if you install the Arabic
  language via Language Support, a couple of Arabic fonts packages are
  pulled. But even if you set an Arabic locale, those fonts won't make a
  difference. The explanation is that DejaVu fonts, which also are able
  to render Arabic, have higher fontconfig precedence. The user must
  mess with fontconfig themselves to change the effective font, which is
  a bug. (I can't tell if it ever worked as intended.)

  So to summarize: This is a combination of a bug fix and an
  enhancement.

  [Test Case]

  * Install the language-selector-{gnome,common} packages
    from focal-proposed.

  * Open the Language Support tool and install Arabic.

  * Open a terminal window and run this command:

    LC_CTYPE=ar_EG.UTF-8 fc-match -a | head -10

  * Find that Noto fonts are at the top of the list.

  [Regression risk]

  This will change the effective font for rendering Arabic for some
  users. But the user experience will be improved in those cases, not
  the opposite.

  The change in font will only happen for users with an Arabic locale.
  The risk that other users would be affected by the change is low.

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 1893101] Re: Thunderbird 78.02.0 Crashes

FWIW, I'm not observing the crash when installing thunderbird from
groovy-proposed in a fully up-to-date groovy amd64 VM.

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

Title:
  Thunderbird 78.02.0 Crashes

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Thunderbird just segfaults and crashes on my system when i installed the .deb 
package
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bittin 4129 F pulseaudio
   /dev/snd/pcmC1D7p:   bittin 4129 F...m pulseaudio
   /dev/snd/controlC0:  bittin 4129 F pulseaudio
   /dev/snd/pcmC0D0p:   bittin 4129 F...m pulseaudio
  BuildID: 20200821101218
  CasperMD5CheckResult: skip
  Channel: release
  DistroRelease: Ubuntu 20.10
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-07-29 (28 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200729)
  IpRoute:
   default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 
   192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.158 metric 
100
  Locales: extensions.sqlite corrupt or missing
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: thunderbird 1:78.2.0+build1-0ubuntu2 [origin: unknown]
  PackageArchitecture: amd64
  Plugins: Shockwave Flash - 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources:
   /usr/lib/thunderbird/defaults/pref/vendor.js
   /usr/lib/thunderbird/defaults/pref/syspref.js
   /usr/lib/thunderbird/defaults/pref/channel-prefs.js
   prefs.js
  ProcEnviron:
   TERM=st-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/usr/bin/fish
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Profiles: Profile0 (Default) - LastVersion=68.10.0/20200629235513 (Out of 
date)
  RunningIncompatibleAddons: False
  Tags: third-party-packages groovy release-channel
  Themes: extensions.sqlite corrupt or missing
  Uname: Linux 5.4.0-42-generic x86_64
  UnreportableReason: Det här är inte ett officiellt Ubuntu-paket. Ta bort 
eventuella tredjepartspaket och försök igen.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/18/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-Gaming5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-Gaming 5
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.apport.blacklist.d.thunderbird: [deleted]
  modified.conffile..etc.apport.native-origins.d.thunderbird: [deleted]
  modified.conffile..etc.thunderbird.syspref.js: [deleted]

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

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

[Desktop-packages] [Bug 1893650] Re: Chromium snap causes network traffic. (Duh!)

2020-08-31 Thread rew

OK. Done. Downloaded, tested: Nope, google-chrome-stable does not show
this behaviour.

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

Title:
  Chromium snap causes network traffic. (Duh!)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When Chromium is running (but otherwise idle!), there is NFS traffic
  between my workstation and the NFS server here. On the order of 24000
  packets per second. Several tens of packets, OK. several hundreds:
  mwah. But this is outrageous.

  When strace-ing the chrome process I see:

  poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=31, events=POLLIN}, 
{fd=32, events=POLLIN}, {fd=137, events=POLLIN}], 5, 0) = 0 (Timeout)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)

  It uses poll to wait for events... and then gets informed: A timeout
  occurred, no filedescriptors are ready and then STILL Tries to read
  from fd 31 and 32. Furthermore, the process seems to specify a 0
  timeout as quite often I see the poll call return in about 20-50
  microseconds.

  The process that is doing this shows as:

   /snap/chromium/1284/usr/lib/chromium-browser/chrome --no-default-
  browser-check --no-first-run --password-store

  1) 
  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  2) 
  chromium-browser:
Installed: 84.0.4147.105-0ubuntu0.20.04.1
Candidate: 84.0.4147.105-0ubuntu0.20.04.1
Version table:
   *** 84.0.4147.105-0ubuntu0.20.04.1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

  
  3) I expect chromium to use little to no resources (CPU, network) when I'm 
not actively using it. (asking for small memory footprint is not currently 
realistic). 

  4)_ Chromium seems to do something that requires NFS traffic.

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

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

[Desktop-packages] [Bug 1893415] Re: Hardware GPU Compositing not working, missing libGLESV2.so in snap package

For future reference, here is the corresponding upstream commit:
https://chromium.googlesource.com/chromium/src/+/991f4aabb715c027664a007f814c08cb2175674e.

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

Title:
  Hardware GPU Compositing not working, missing libGLESV2.so in snap
  package

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  chrome://gpu/

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only. Hardware acceleration disabled
  Flash Stage3D: Software only. Hardware acceleration disabled
  Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  Out-of-process Rasterization: Disabled
  OpenGL: Disabled
  Hardware Protected Video Decode: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Skia Renderer: Enabled
  Video Decode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  Problems Detected
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Version Information
  Data exported 2020-08-28T12:43:36.316Z
  Chrome versionChrome/85.0.4183.83
  Operating system  Linux 5.4.0-42-generic
  Software rendering list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/software_rendering_list.json
  Driver bug list URL   
https://chromium.googlesource.com/chromium/src/+/94abc2237ae0c9a4cb5f035431c8adfb94324633/gpu/config/gpu_driver_bug_list.json
  ANGLE commit id   unknown hash
  2D graphics backend   Skia/85 8ae885386e910cff8c543ae0d952a2c43f46e4ad
  Command Line  /snap/chromium/1275/usr/lib/chromium-browser/chrome 
--no-default-browser-check --no-first-run --password-store 
--flag-switches-begin --flag-switches-end 
--origin-trial-disabled-features=MeasureMemory

  [truncated]

  Problems Detected for Hardware GPU
  Gpu compositing has been disabled, either via blacklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  Log Messages
  [31619:31619:0828/134331.474558:ERROR:gl_implementation.cc(286)] : Failed to 
load /snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: 
/snap/chromium/1275/usr/lib/chromium-browser/libGLESv2.so: cannot open shared 
object file: No such file or directory
  [31619:31619:0828/134331.475780:ERROR:viz_main_impl.cc(150)] : Exiting GPU 
process due to errors during initialization
  GpuProcessHost: The GPU process exited normally. Everything is okay.
  [31627:31627:0828/134336.157808:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.159639:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
  [31627:31627:0828/134336.160909:ERROR:gles2_cmd_decoder.cc(3614)] : 
ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader

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

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

[Desktop-packages] [Bug 1893650] Re: Chromium snap causes network traffic. (Duh!)

2020-08-31 Thread rew

(posting this from Chromium again, and immediately I see the network
traffic ballooning. It does look a bit as if the linux "select"
behaviour: modify the timeout to show time remaining is involved: It
takes like 15 seconds of medium traffic before stuff is back to the
original level again. My hypothesis is that "1ms" is still in the
timeout field for those first 15 seconds, so the repeat rate of the
triggering code is not so high. Then the timeout is reduced to zer and
it goes fullblast...

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

Title:
  Chromium snap causes network traffic. (Duh!)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When Chromium is running (but otherwise idle!), there is NFS traffic
  between my workstation and the NFS server here. On the order of 24000
  packets per second. Several tens of packets, OK. several hundreds:
  mwah. But this is outrageous.

  When strace-ing the chrome process I see:

  poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=31, events=POLLIN}, 
{fd=32, events=POLLIN}, {fd=137, events=POLLIN}], 5, 0) = 0 (Timeout)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)

  It uses poll to wait for events... and then gets informed: A timeout
  occurred, no filedescriptors are ready and then STILL Tries to read
  from fd 31 and 32. Furthermore, the process seems to specify a 0
  timeout as quite often I see the poll call return in about 20-50
  microseconds.

  The process that is doing this shows as:

   /snap/chromium/1284/usr/lib/chromium-browser/chrome --no-default-
  browser-check --no-first-run --password-store

  1) 
  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  2) 
  chromium-browser:
Installed: 84.0.4147.105-0ubuntu0.20.04.1
Candidate: 84.0.4147.105-0ubuntu0.20.04.1
Version table:
   *** 84.0.4147.105-0ubuntu0.20.04.1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

  
  3) I expect chromium to use little to no resources (CPU, network) when I'm 
not actively using it. (asking for small memory footprint is not currently 
realistic). 

  4)_ Chromium seems to do something that requires NFS traffic.

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

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

[Desktop-packages] [Bug 1893658] [NEW] I installed Ubuntu 20.04.1 Yesterday and Copied my backup from my mac so I did't shut down the night before and It is up from theinstallation i.e. about 35 hours

2020-08-31 Thread Suraj Dnyaneshwar Chandgude

Public bug reported:

I installed Ubuntu 20.04.1 Yesterday and Copied my backup from my mac so
I did't shut down the night before and It is up from theinstallation
i.e. about 35 hours from installation, and I have installed multiple
browsers, MS Teams, Skype, VSCode Insides (Two instances running), with
two terminal window, It is eating memory(RAM) like hell along with SWAP.
Both are full

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
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.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 31 19:28:24 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-08-30 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  I installed Ubuntu 20.04.1 Yesterday and Copied my backup from my mac
  so I did't shut down the night before and It is up from
  theinstallation i.e. about 35 hours from installation, and I have
  installed multiple browsers, MS Teams, Skype, VSCode Insides (Two
  instances running), with two terminal window, It is eating memory(RAM)
  like hell along with SWAP. Both are full

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 20.04.1 Yesterday and Copied my backup from my mac
  so I did't shut down the night before and It is up from
  theinstallation i.e. about 35 hours from installation, and I have
  installed multiple browsers, MS Teams, Skype, VSCode Insides (Two
  instances running), with two terminal window, It is eating memory(RAM)
  like hell along with SWAP. Both are full

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  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.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 31 19:28:24 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-08-30 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893655] [NEW] Headphones connect but don't appear as audio output

2020-08-31 Thread Alistair Cunningham

Public bug reported:

When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
laptop at Bluetooth level, but don't appear as an audio device. I have
to remove them in the Ubuntu Bluetooth settings, and then re-pair them,
every time. This is rather inconvenient. This started happening after
upgrading to Ubuntu 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
Uname: Linux 5.6.0-1021-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Aug 31 14:48:53 2020
InstallationDate: Installed on 2020-07-14 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20U9CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET19W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

Title:
  Headphones connect but don't appear as audio output

Status in bluez package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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

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

This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.2

---
alsa-ucm-conf (1.2.2-1ubuntu0.2) focal; urgency=medium

  * d/p/0003-ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  * d/p/0004-ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  * d/p/0005-sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  * d/p/0006-ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  * d/p/0007-sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  * d/p/0008-sof-soundwire-initial-UCM2-version.patch
  * d/p/0009-sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  * d/p/0010-sof-soundwire-rewrite-for-syntax-3.patch
  * d/p/0011-HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  * d/p/0012-hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  * d/p/0013-amd-renoir-acp-use-the-machine-driver-s-name-for-top.patch
  * d/p/0014-amd-renoir-acp-add-syntax-in-the-Linked.patch
  * d/p/0015-HDA-Intel-only-bind-the-acp-dmic-to-the-soundcard-wi.patch
  * d/p/0016-Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
enable sound on AMD Renoir machines (LP: #1889217)

  [ Kai-Heng Feng ]
  * d/p/0017-Add-support-for-Lenovo-ThinkStation-P620-Main-Audio.patch
Add proper stream and jack assignment to Lenovo ThinkStation P620
(LP: #1891461)

 -- Hui Wang   Mon, 10 Aug 2020 15:05:02 +0800

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

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

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

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

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

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

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

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

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch

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

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.6

---
pulseaudio (1:13.99.1-1ubuntu3.6) focal; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/0001-alsa-mixer-Recognize-USB-audio-jack-mixer.patch:
- recognize USB jack mixer to support jack detection (LP: #1891461)
  * d/p/0002-module-alsa-card-Set-a-minimum-profile-priority-if-i.patch:
- resolve an issue when headset gets unplugged, HDMI audio is choosen
  instead of internal speaker (LP: #1891461)

  [ Hui Wang ]
  * d/p/0034-alsa-adjust-ucm-sink-source-priority-according-to-po.patch
  * d/p/0035-ucm-add-possibility-to-skip-the-UCM-card-completely-.patch
  * d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch
- Make the AMD acp sound card skipped in the PA, then the ucm could
  link it to other sound cards, it is easy for gnome to support AMD
  Renoir sound driver after this change. (LP: #1889217)

 -- Kai-Heng Feng   Thu, 13 Aug 2020
18:53:08 +0800

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

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

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

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

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

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

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

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch

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

This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2

---
alsa-lib (1.2.2-2.1ubuntu2) focal; urgency=medium

  * d/p/0001-conf-add-snd_config_is_array-function.patch
  * d/p/0001-Enabled-extended-namehints-in-alsa.conf.patch
  * d/p/0002-topology-use-snd_config_is_array-function.patch
  * d/p/0003-ucm-merge-the-array-items-from-the-condition-blocks.patch
  * d/p/0004-ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  * d/p/0005-ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  * d/p/0006-ucm-handle-set-_once-command.patch
  * d/p/0007-ucm-handle-set-_defaults-command.patch
  * d/p/0008-ucm-initialize-mgr-once_list.patch
  * d/p/0009-ucm-fix-SectionOnce-comment.patch
  * d/p/0010-ucm-fix-compilation-error-in-set_defaults_user.patch
  * d/p/0011-ucm-rename-SectionOnce-to-BootSequence.patch
  * d/p/0012-ucm-rename-_once-command-to-_boot-command.patch
  * d/p/0013-ucm-configuration-implement-in-place-Include.patch
  * d/p/0014-ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  * d/p/0015-ucm-config-substitute-File-string-to-allow-variables.patch
  * d/p/0016-ucm-configuration-allow-to-define-the-configuration-.patch
  * d/p/0017-ucm-configuration-add-DefineRegex.patch
  * d/p/0018-ucm-substitute-arguments-in-sequences.patch
  * d/p/0019-ucm-allow-syntax-version-3.patch
  * d/p/0020-ucm-config-change-the-in-place-include-evaluation-or.patch
  * d/p/0021-ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  * d/p/0022-ucm-substitute-also-value-strings.patch
  * d/p/0023-ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  * d/p/0024-ucm-String-condition-implement-Empty.patch
  * d/p/0025-ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  * d/p/0026-ucm-substitute-OpenName.patch
  * d/p/0027-ucm-substitute-CardNumber.patch
  * d/p/0028-ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  * d/p/0029-ucm-substitute-device-modifier-names-too.patch
  * d/p/0030-ucm-substitute-device-strings-in-the-device-lists.patch
  * d/p/0031-ucm-substitute-component-sequence-string.patch
  * d/p/0032-ucm-substitute-verb-name-and-file-field.patch
  * d/p/0033-ucm-substitute-Comment-in-Transition-and-Device.patch
  * d/p/0034-ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  * d/p/0035-ucm-substitute-arguments-in-sequences-only-for-synta.patch
  * d/p/0036-ucm-shuffle-code-in-compound_merge.patch
  * d/p/0037-ucm-implement-CardIdByName-substitution.patch
  * d/p/0038-ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  * d/p/0039-ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  * d/p/0040-ucm-implement-CardNumberByName-substitution.patch
  * d/p/0041-ucm-fix-the-possible-buffer-overflow-substitution.patch
  * d/p/0042-ucm-simplify-get_by_card-in-parser.c.patch
  * d/p/0043-ucm-implement-AlwaysTrue-Condition.Type.patch
  * d/p/0044-ucm-Allow-empty-strings-in-var-.-substitutions.patch
  * d/p/0045-ucm-substitution-remove-duplicate-allow_empty-assign.patch
  * d/p/0046-ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch
  * d/p/0047-ucm-substitute-the-merged-tree-completely.patch
  * add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control
  * add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu2 in the 
d/libasound2.symbols
- enable sound on AMD Renoir machines (LP: #1889217)

  [ Kai-Heng Feng ]
  * d/p/0048-conf-USB-Audio-Disable-IEC958-on-Lenovo-ThinkStation.patch
- Disable IEC958 on Lenovo ThinkStation P620 (LP: #1891461)

 -- Hui Wang   Mon, 10 Aug 2020 15:09:30 +0800

** Changed in: alsa-lib (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

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

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

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

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and

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

This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.2

---
alsa-ucm-conf (1.2.2-1ubuntu0.2) focal; urgency=medium

  * d/p/0003-ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  * d/p/0004-ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  * d/p/0005-sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  * d/p/0006-ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  * d/p/0007-sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  * d/p/0008-sof-soundwire-initial-UCM2-version.patch
  * d/p/0009-sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  * d/p/0010-sof-soundwire-rewrite-for-syntax-3.patch
  * d/p/0011-HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  * d/p/0012-hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  * d/p/0013-amd-renoir-acp-use-the-machine-driver-s-name-for-top.patch
  * d/p/0014-amd-renoir-acp-add-syntax-in-the-Linked.patch
  * d/p/0015-HDA-Intel-only-bind-the-acp-dmic-to-the-soundcard-wi.patch
  * d/p/0016-Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
enable sound on AMD Renoir machines (LP: #1889217)

  [ Kai-Heng Feng ]
  * d/p/0017-Add-support-for-Lenovo-ThinkStation-P620-Main-Audio.patch
Add proper stream and jack assignment to Lenovo ThinkStation P620
(LP: #1891461)

 -- Hui Wang   Mon, 10 Aug 2020 15:05:02 +0800

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

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

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

[Desktop-packages] [Bug 1889217] Update Released

2020-08-31 Thread Łukasz Zemczak

The verification of the Stable Release Update for alsa-lib 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1889217

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

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

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

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

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

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

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

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

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.6

---
pulseaudio (1:13.99.1-1ubuntu3.6) focal; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/0001-alsa-mixer-Recognize-USB-audio-jack-mixer.patch:
- recognize USB jack mixer to support jack detection (LP: #1891461)
  * d/p/0002-module-alsa-card-Set-a-minimum-profile-priority-if-i.patch:
- resolve an issue when headset gets unplugged, HDMI audio is choosen
  instead of internal speaker (LP: #1891461)

  [ Hui Wang ]
  * d/p/0034-alsa-adjust-ucm-sink-source-priority-according-to-po.patch
  * d/p/0035-ucm-add-possibility-to-skip-the-UCM-card-completely-.patch
  * d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch
- Make the AMD acp sound card skipped in the PA, then the ucm could
  link it to other sound cards, it is easy for gnome to support AMD
  Renoir sound driver after this change. (LP: #1889217)

 -- Kai-Heng Feng   Thu, 13 Aug 2020
18:53:08 +0800

-- 
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:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

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

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

This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2

---
alsa-lib (1.2.2-2.1ubuntu2) focal; urgency=medium

  * d/p/0001-conf-add-snd_config_is_array-function.patch
  * d/p/0001-Enabled-extended-namehints-in-alsa.conf.patch
  * d/p/0002-topology-use-snd_config_is_array-function.patch
  * d/p/0003-ucm-merge-the-array-items-from-the-condition-blocks.patch
  * d/p/0004-ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  * d/p/0005-ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  * d/p/0006-ucm-handle-set-_once-command.patch
  * d/p/0007-ucm-handle-set-_defaults-command.patch
  * d/p/0008-ucm-initialize-mgr-once_list.patch
  * d/p/0009-ucm-fix-SectionOnce-comment.patch
  * d/p/0010-ucm-fix-compilation-error-in-set_defaults_user.patch
  * d/p/0011-ucm-rename-SectionOnce-to-BootSequence.patch
  * d/p/0012-ucm-rename-_once-command-to-_boot-command.patch
  * d/p/0013-ucm-configuration-implement-in-place-Include.patch
  * d/p/0014-ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  * d/p/0015-ucm-config-substitute-File-string-to-allow-variables.patch
  * d/p/0016-ucm-configuration-allow-to-define-the-configuration-.patch
  * d/p/0017-ucm-configuration-add-DefineRegex.patch
  * d/p/0018-ucm-substitute-arguments-in-sequences.patch
  * d/p/0019-ucm-allow-syntax-version-3.patch
  * d/p/0020-ucm-config-change-the-in-place-include-evaluation-or.patch
  * d/p/0021-ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  * d/p/0022-ucm-substitute-also-value-strings.patch
  * d/p/0023-ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  * d/p/0024-ucm-String-condition-implement-Empty.patch
  * d/p/0025-ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  * d/p/0026-ucm-substitute-OpenName.patch
  * d/p/0027-ucm-substitute-CardNumber.patch
  * d/p/0028-ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  * d/p/0029-ucm-substitute-device-modifier-names-too.patch
  * d/p/0030-ucm-substitute-device-strings-in-the-device-lists.patch
  * d/p/0031-ucm-substitute-component-sequence-string.patch
  * d/p/0032-ucm-substitute-verb-name-and-file-field.patch
  * d/p/0033-ucm-substitute-Comment-in-Transition-and-Device.patch
  * d/p/0034-ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  * d/p/0035-ucm-substitute-arguments-in-sequences-only-for-synta.patch
  * d/p/0036-ucm-shuffle-code-in-compound_merge.patch
  * d/p/0037-ucm-implement-CardIdByName-substitution.patch
  * d/p/0038-ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  * d/p/0039-ucm-allow-to-use-the-defined-variables-in-the-substi.patch
  * d/p/0040-ucm-implement-CardNumberByName-substitution.patch
  * d/p/0041-ucm-fix-the-possible-buffer-overflow-substitution.patch
  * d/p/0042-ucm-simplify-get_by_card-in-parser.c.patch
  * d/p/0043-ucm-implement-AlwaysTrue-Condition.Type.patch
  * d/p/0044-ucm-Allow-empty-strings-in-var-.-substitutions.patch
  * d/p/0045-ucm-substitution-remove-duplicate-allow_empty-assign.patch
  * d/p/0046-ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch
  * d/p/0047-ucm-substitute-the-merged-tree-completely.patch
  * add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control
  * add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu2 in the 
d/libasound2.symbols
- enable sound on AMD Renoir machines (LP: #1889217)

  [ Kai-Heng Feng ]
  * d/p/0048-conf-USB-Audio-Disable-IEC958-on-Lenovo-ThinkStation.patch
- Disable IEC958 on Lenovo ThinkStation P620 (LP: #1891461)

 -- Hui Wang   Mon, 10 Aug 2020 15:09:30 +0800

** Changed in: alsa-lib (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Add proper USB audio support for Lenovo ThinkStation P620

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

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

[Desktop-packages] [Bug 1893650] Re: Chromium snap causes network traffic. (Duh!)

Thanks for the report rew.
For testing purposes, could you download the google chrome installer from 
google.com/chrome, install it and test whether it is behaving similarly? That 
would be a useful data point. Thanks!

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

Title:
  Chromium snap causes network traffic. (Duh!)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When Chromium is running (but otherwise idle!), there is NFS traffic
  between my workstation and the NFS server here. On the order of 24000
  packets per second. Several tens of packets, OK. several hundreds:
  mwah. But this is outrageous.

  When strace-ing the chrome process I see:

  poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=31, events=POLLIN}, 
{fd=32, events=POLLIN}, {fd=137, events=POLLIN}], 5, 0) = 0 (Timeout)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)

  It uses poll to wait for events... and then gets informed: A timeout
  occurred, no filedescriptors are ready and then STILL Tries to read
  from fd 31 and 32. Furthermore, the process seems to specify a 0
  timeout as quite often I see the poll call return in about 20-50
  microseconds.

  The process that is doing this shows as:

   /snap/chromium/1284/usr/lib/chromium-browser/chrome --no-default-
  browser-check --no-first-run --password-store

  1) 
  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  2) 
  chromium-browser:
Installed: 84.0.4147.105-0ubuntu0.20.04.1
Candidate: 84.0.4147.105-0ubuntu0.20.04.1
Version table:
   *** 84.0.4147.105-0ubuntu0.20.04.1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

  
  3) I expect chromium to use little to no resources (CPU, network) when I'm 
not actively using it. (asking for small memory footprint is not currently 
realistic). 

  4)_ Chromium seems to do something that requires NFS traffic.

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

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

2020-08-31 Thread Łukasz Zemczak

The verification of the Stable Release Update for alsa-lib 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 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:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

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:

[Desktop-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl

Here is a diff working vs non-working:

https://www.diffchecker.com/WW0VL687

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

Title:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone not plugged in on bootl

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone is not plugged in on boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mea1935 F pulseaudio
   /dev/snd/pcmC1D0c:   mea1935 F...m pulseaudio
   /dev/snd/controlC0:  mea1935 F pulseaudio
   /dev/snd/controlC2:  mea1935 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 30 12:29:20 2020
  InstallationDate: Installed on 2020-07-17 (44 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450I GAMING PLUS AC (MS-7A40)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A40
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 465309] Re: [Upstream] Regular Expression Search for circumflex by itself does not find beginning of a paragraph

2020-08-31 Thread Bug Watch Updater

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  [Upstream] Regular Expression Search for circumflex by itself does not
  find beginning of a paragraph

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  New
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.5.3-0ubuntu1
Candidate: 1:3.5.3-0ubuntu1
Version table:
   *** 1:3.5.3-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  3) What is expected to happen in Writer, Calc, or the Macro Editor is when 
one opens the Find & Replace window, with Regular Expression checkbox checked, 
in the Search for drop down put a circumflex in, and the beginning of every 
paragraph is found. Consulting the LO Wiki and built-in LO help, it is implied 
that using a circumflex by itself in the find field should match the beginning 
of a paragraph:
  http://help.libreoffice.org/Common/List_of_Regular_Expressions

  4) What happens instead is nothing is found.

  WORKAROUND: Notepad++ 6.1.2:
  http://notepad-plus-plus.org/download/v6.1.2.html

  via WINE.

  apt-cache policy wine1.5
  wine1.5:
Installed: 1.5.4-0ubuntu1~ppa1~precise1+pulse17
Candidate: 1.5.4-0ubuntu1~ppa1~precise1+pulse17
Version table:
   *** 1.5.4-0ubuntu1~ppa1~precise1+pulse17 0
  500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ precise/main 
i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Oct 30 11:36:03 2009
  DistroRelease: Ubuntu 9.10
  Package: openoffice.org-core 1:3.1.1-4ubuntu2 [modified: 
var/lib/openoffice/basis3.1/program/services.rdb]
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-12-generic x86_64

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

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

[Desktop-packages] [Bug 465309]

2020-08-31 Thread Michael-warner-ut+libreoffice

*** This bug has been marked as a duplicate of bug 135538 ***

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

Title:
  [Upstream] Regular Expression Search for circumflex by itself does not
  find beginning of a paragraph

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  New
Status in libreoffice package in Ubuntu:
  Confirmed
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.5.3-0ubuntu1
Candidate: 1:3.5.3-0ubuntu1
Version table:
   *** 1:3.5.3-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  3) What is expected to happen in Writer, Calc, or the Macro Editor is when 
one opens the Find & Replace window, with Regular Expression checkbox checked, 
in the Search for drop down put a circumflex in, and the beginning of every 
paragraph is found. Consulting the LO Wiki and built-in LO help, it is implied 
that using a circumflex by itself in the find field should match the beginning 
of a paragraph:
  http://help.libreoffice.org/Common/List_of_Regular_Expressions

  4) What happens instead is nothing is found.

  WORKAROUND: Notepad++ 6.1.2:
  http://notepad-plus-plus.org/download/v6.1.2.html

  via WINE.

  apt-cache policy wine1.5
  wine1.5:
Installed: 1.5.4-0ubuntu1~ppa1~precise1+pulse17
Candidate: 1.5.4-0ubuntu1~ppa1~precise1+pulse17
Version table:
   *** 1.5.4-0ubuntu1~ppa1~precise1+pulse17 0
  500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ precise/main 
i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Oct 30 11:36:03 2009
  DistroRelease: Ubuntu 9.10
  Package: openoffice.org-core 1:3.1.1-4ubuntu2 [modified: 
var/lib/openoffice/basis3.1/program/services.rdb]
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-12-generic x86_64

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

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

[Desktop-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

While looking at pcsc-tools and pcscs-perl (only needed for the
dependency from pcscs-tools) I have found that these are not really
depended on by anything important.

This matches the statement in the request that says:
"This package provides general utilities for smartcards; it's possible that we 
do not strictly need this package for our use case."

Use case wise it contains:
- /usr/bin/ATR_analysis
  Tool to analyze the raw ATR answer from a smart card - debugging tool at best 
and
  no common use case
- /usr/bin/scriptor + /usr/bin/gscriptor
  Send scripts to a smartcard, that might be a developer or debugging feature 
but doesn't sound 
  an end user thing for the enterprise desktop you have in mind.
- /usr/bin/pcsc_scan
  This is the one end-user useful tool in this toolset showing the available 
cards that are 
  inserted. But honestly you want to integrate things in an enterprise desktop 
and there I'd
  expect a UI-thing for it and not this cmdline tool. At the same time nothing 
in gnome or 
  anywhere else related depends on it.

IMHO we should not promote packages to main we have no real use and
integration of.

If there is a good case how this plays a role in the envisioned
"Enterprise Desktop smartcard integration" then I'm more than happy to
review and process this (in that case also say why/why-not pcscd is
important - see above).

MIR Team Nack to pcsc-tools and pcscs-perl for the (currently) given
dependencies and reasoning.

** Changed in: pcsc-perl (Ubuntu)
   Status: New => Invalid

** Changed in: pcsc-tools (Ubuntu)
   Status: New => Invalid

** Changed in: pcsc-perl (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => (unassigned)

** Changed in: pcsc-tools (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => (unassigned)

** Changed in: pcsc-lite (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => (unassigned)

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  Incomplete
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The

[Desktop-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl

Logging in and out works. So I imagine the headphones just need to be
plugged in pre login.

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

Title:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone not plugged in on bootl

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone is not plugged in on boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mea1935 F pulseaudio
   /dev/snd/pcmC1D0c:   mea1935 F...m pulseaudio
   /dev/snd/controlC0:  mea1935 F pulseaudio
   /dev/snd/controlC2:  mea1935 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 30 12:29:20 2020
  InstallationDate: Installed on 2020-07-17 (44 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450I GAMING PLUS AC (MS-7A40)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A40
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl

Sorry for the poor description.

Basically, if my headphones are not plugged pre-boot I cannot get them
to register (I think I got them to work post boot by reinstalling
pulseaudio and trashing the config but not am not certain).

Here is the alsa-info.txt when they are plugged in pre-boot:

http://alsa-project.org/db/?f=86bf2f9c23ca1a730c413524ec17ea7b05f19766

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

Title:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone not plugged in on bootl

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone is not plugged in on boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mea1935 F pulseaudio
   /dev/snd/pcmC1D0c:   mea1935 F...m pulseaudio
   /dev/snd/controlC0:  mea1935 F pulseaudio
   /dev/snd/controlC2:  mea1935 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 30 12:29:20 2020
  InstallationDate: Installed on 2020-07-17 (44 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450I GAMING PLUS AC (MS-7A40)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A40
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl

Here is the alsa-info.txt when they are NOT plugged in pre-boot and do
not show up in the settings:


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

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

Title:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone not plugged in on bootl

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if
  headphone is not plugged in on boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mea1935 F pulseaudio
   /dev/snd/pcmC1D0c:   mea1935 F...m pulseaudio
   /dev/snd/controlC0:  mea1935 F pulseaudio
   /dev/snd/controlC2:  mea1935 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 30 12:29:20 2020
  InstallationDate: Installed on 2020-07-17 (44 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450I GAMING PLUS AC (MS-7A40)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A40
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Desktop-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

I asked about it in comment #2 already.
pcsc-lite was MIRed in bug 250245 but pcscd explcitly excluded.
One either needs to:
1. step up and say "yes we want to own it" (in that case please add a request 
to the description)
2. say this isn't needed for what you want to achieve (Essentially providing a 
Windows(R) SCard interfce - which chances are you won't need).

In the case of #2 please modify "opensc" in Ubuntu to reduce the "Recommends" 
dependency on pcscd to just a "Suggests".
Marking the task as incomplete and not doing a full review on pcscd until 
really requested.

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Incomplete

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  Incomplete
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]

[Desktop-packages] [Bug 1893650] [NEW] Chromium snap causes network traffic. (Duh!)

2020-08-31 Thread rew

Public bug reported:

When Chromium is running (but otherwise idle!), there is NFS traffic
between my workstation and the NFS server here. On the order of 24000
packets per second. Several tens of packets, OK. several hundreds: mwah.
But this is outrageous.

When strace-ing the chrome process I see:

poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=31, events=POLLIN}, 
{fd=32, events=POLLIN}, {fd=137, events=POLLIN}], 5, 0) = 0 (Timeout)
recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)

It uses poll to wait for events... and then gets informed: A timeout
occurred, no filedescriptors are ready and then STILL Tries to read from
fd 31 and 32. Furthermore, the process seems to specify a 0 timeout as
quite often I see the poll call return in about 20-50 microseconds.

The process that is doing this shows as:

 /snap/chromium/1284/usr/lib/chromium-browser/chrome --no-default-
browser-check --no-first-run --password-store

1) 
Description:Ubuntu 20.04.1 LTS
Release:20.04

2) 
chromium-browser:
  Installed: 84.0.4147.105-0ubuntu0.20.04.1
  Candidate: 84.0.4147.105-0ubuntu0.20.04.1
  Version table:
 *** 84.0.4147.105-0ubuntu0.20.04.1 500
500 http://nl.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 80.0.3987.163-0ubuntu1 500
500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages


3) I expect chromium to use little to no resources (CPU, network) when I'm not 
actively using it. (asking for small memory footprint is not currently 
realistic). 

4)_ Chromium seems to do something that requires NFS traffic.

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

Title:
  Chromium snap causes network traffic. (Duh!)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When Chromium is running (but otherwise idle!), there is NFS traffic
  between my workstation and the NFS server here. On the order of 24000
  packets per second. Several tens of packets, OK. several hundreds:
  mwah. But this is outrageous.

  When strace-ing the chrome process I see:

  poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=31, events=POLLIN}, 
{fd=32, events=POLLIN}, {fd=137, events=POLLIN}], 5, 0) = 0 (Timeout)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(31, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(32, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily 
unavailable)

  It uses poll to wait for events... and then gets informed: A timeout
  occurred, no filedescriptors are ready and then STILL Tries to read
  from fd 31 and 32. Furthermore, the process seems to specify a 0
  timeout as quite often I see the poll call return in about 20-50
  microseconds.

  The process that is doing this shows as:

   /snap/chromium/1284/usr/lib/chromium-browser/chrome --no-default-
  browser-check --no-first-run --password-store

  1) 
  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  2) 
  chromium-browser:
Installed: 84.0.4147.105-0ubuntu0.20.04.1
Candidate: 84.0.4147.105-0ubuntu0.20.04.1
Version table:
   *** 84.0.4147.105-0ubuntu0.20.04.1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

  
  3) I expect chromium to use little to no resources (CPU, network) when I'm 
not actively using it. (asking for small memory footprint is not currently 
realistic). 

  4)_ Chromium seems to do something that requires NFS traffic.

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

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

[Desktop-packages] [Bug 1893484] Re: Google Chrome 85.0.4183.83 crahses with SIGSEGV

Please note that an update of chromium-browser to version 85.0.4183.83
should be available very soon in the Ubuntu repositories. I would
appreciate if you could comment on this bug when you get the update to
let me know whether chromium-browser still works. Thanks in advance!

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

Title:
  Google Chrome 85.0.4183.83 crahses with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After an Update, the new version Google Chrome 85.0.4183.83  crashes
  with SIGSEGV.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  google-chrome-stable   85.0.4183.83-1 
  amd64The web browser from Google

  3) What you expected to happen
  Load the initial page or load my themes and configurations

  4) What happened instead
  It show the initial page, ask for Restore pages? when clicked it freezes for 
a moment and then a crash with:
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
  +++ killed by SIGSEGV (core dumped) +++

  
  Previous version was working fine.

  I de-installed, removed all configurations and themes and tried again.
  Same issue.

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

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

[Desktop-packages] [Bug 1892724] Re: Bump package epoch to 1 to ensure working upgrade path and transition to snap

Verified working.
For convenience I used a slightly different testing method than the test case 
in the bug description: I downloaded and installed (with `dpkg -i`) the 
chromium-browser, chromium-browser-l10n and chromium-codecs-ffmpeg-extra debs 
from 
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+sourcepub/11549449/+listing-archive-extra
 (version 85.0.4183.83-0ubuntu0.18.04.1, currently awaiting sponsoring to 
bionic-security) in a fully up-to-date focal VM. I then ran `sudo apt update` 
to verify that no update was available for chromium-browser. I then enabled 
focal-proposed for universe and verified that the update to chromium-browser 
1:85.0.4183.83-0ubuntu0.20.04.1 was available, installed it with `sudo apt 
install chromium-browser`, and checked that this installed the chromium snap as 
expected. I then verified that chromium-browser launches and works as expected.

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

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

Title:
  Bump package epoch to 1 to ensure working upgrade path and transition
  to snap

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Committed

Bug description:
  As a follow-up to bug #1889106, it was decided that the best solution to 
handle recurring version bumps for chromium-browser updates in stable series 
was to bump the package epoch to 1.
  See the discussion in 
https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041127.html.
  This needs to be done in groovy (done) and SRUed to focal.

  [Impact]

  Users upgrading from 18.04 to 20.04 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended as soon as a security 
update is published to bionic-security (which happens typically every 2-3 
weeks).
  This is because the version number in 18.04 often ends up being greater than 
the version in 20.04. Bumping the version number in 20.04 is enough to fix 
this, and was done a few times already (bug #1858500, bug #1889106), but it is 
tedious and impractical.

  [Test Case]

   * Ensure that a version of chromium-browser newer than 
84.0.4147.105-0ubuntu0.20.04.1 is available in bionic-{security,updates} (not 
currently the case, but will soon happen as version 85.0.4183.83 was just 
released upstream)
   * On a machine running 18.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 20.04
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions
  compared to the deb package, they are being tracked at
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
  snap is the desired behaviour though.

  [Original Description]

  For a complete rationale, see comments #4, #5, #7 and #8 in bug
  #1889106, and the discussion in https://lists.ubuntu.com/archives
  /ubuntu-devel/2020-August/041127.html.

  This needs to be done in groovy and SRUed to focal.

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

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

[Desktop-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

[Summary]
This looks mostly ok from a MIR POV, I've listed remaining that would
help to get this improved below. Those are rather minor, MIR Ack under the
condition to have them handled. Please update the bug once you have done so.

Specific binary packages to be promoted to main: libpam-pkcs11

Required TODOs:
- some testing for the overall context of smartcard usage as outlined in
  the ccid review
- please look into the odd file path of the pam .so file if that is ok
- please subscribe the team to the bug right away (too easy to be missed
  later and gives a preview about the bug influx)
Recommended TODOs:
- n/a

[Duplication]
In addition to opensc-pkcs11 this seems like "the same". But while opensc-pkcs11
is about providing pkcs#11 for pkcs#15 cards this lib here libpam-pkcs11 is a
subproject to opensc - there are pam_p11 (simpler) and pam-pkcs#11 (this one).
This lib here is about integrating pkcs#11 into pam with extended features
like name mapping and cert chain verification.
See
- https://github.com/OpenSC/OpenSC/wiki#sub-projects
- https://github.com/OpenSC/pam_pkcs11
=> Despite the name similarity duplication isn't an issue here

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- no -dev/-debug/-doc packages that need exclusion

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats
- does not open a port
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop

Problems:
- does deal with system authentication (eg, pam), etc)
=> This needs an security evaluation

[Common blockers]
OK:
- does not FTBFS currently
- no translation present, but none needed for this case (user visible)?
- not a python/go package, no extra constraints to consider int hat regard

Problems:
- does have a test suite that runs at build time
- does have a test suite that runs as autopkgtest
  (I have mentioned the overall testing before, applies here as well.
- The package has a team bug subscriber

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is not in place (but this is only a pam plugin)
- d/watch is present and looks ok
- Upstream update history is slow (but gladly seems only to be
  stable updates)
- Debian/Ubuntu update history is sporadic (e.g. 2 year gap)
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- Does not have Built-Using

Problems:
- the shared objects have odd pathing
  /lib/pam_pkcs11/ldap_mapper.so
  /lib/pam_pkcs11/opensc_mapper.so
  /lib/pam_pkcs11/openssh_mapper.so
  /lib/security/pam_pkcs11.so
  While everything else pam'y is in /lib/x86_64-linux-gnu/security/
  Does this have x86 only limitations (or a multiarch violation) we need
  to solve?

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as I can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks

** Changed in: pam-pkcs11 (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  New
Status in pcsc-tools package in Ubuntu:
  New

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.

[Desktop-packages] [Bug 1893484] Re: Google Chrome 85.0.4183.83 crahses with SIGSEGV

2020-08-31 Thread alex-mobigo

Chromium 84.0.4147.105 Built on Ubuntu , running on Ubuntu 18.04 not
affected!

As for the google-chrome i thought the update to the latest version came from 
Ubuntu, since i always run the update manually and disable any automatic 
update. Ok, wrong assumption.
I will try to report this crash to them or use chromium-browser.

Please, disregard.

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

Title:
  Google Chrome 85.0.4183.83 crahses with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After an Update, the new version Google Chrome 85.0.4183.83  crashes
  with SIGSEGV.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  google-chrome-stable   85.0.4183.83-1 
  amd64The web browser from Google

  3) What you expected to happen
  Load the initial page or load my themes and configurations

  4) What happened instead
  It show the initial page, ask for Restore pages? when clicked it freezes for 
a moment and then a crash with:
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
  +++ killed by SIGSEGV (core dumped) +++

  
  Previous version was working fine.

  I de-installed, removed all configurations and themes and tried again.
  Same issue.

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

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

[Desktop-packages] [Bug 1893638] Re: X forgets middle mouse button exists

2020-08-31 Thread gardron

Moving to xorg-server in that case

Yeah, I'm using XUbuntu but it doesn't feel like an xfsettingsd issue,
but happy to provide more info/test things to determine if that's the
case.

Thanks for the advice on submissions - will follow that in future.

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

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

Title:
  X forgets middle mouse button exists

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Assuming this is the xorg package but could be wrong.

  Running a Logitech MX master 3 mouse, the middle mouse copy/paste
  isn't working out the box or is only working intermittently on boot.
  Using 'xinput --list-props 15' I'm seeing that the 'Middle Emulation
  Enabled (298)' is set to 0. If I set this to '1' by using 'xinput
  --set-prop 15 298 1' then turn the mouse off/on then I regain
  functionality. If I then switch to another computer attached to my KVM
  switch and back to this machine, the input is lost again. Attempting
  to set the default (299) value results in this error:

  X Error of failed request:  BadAccess (attempt to access private resource 
denied)
Major opcode of failed request:  131 (XInputExtension)
Minor opcode of failed request:  57 ()
Serial number of failed request:  20
Current serial number in output stream:  21

  I can script this to get around it, it's just messy and unnecessary

  
  Copy of output from xinput --list-props:

  Device 'Logitech MX Master 3':
Device Enabled (155):   1
Coordinate Transformation Matrix (157): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Natural Scrolling Enabled (291):   0
libinput Natural Scrolling Enabled Default (292):   0
libinput Scroll Methods Available (293):0, 0, 1
libinput Scroll Method Enabled (294):   0, 0, 0
libinput Scroll Method Enabled Default (295):   0, 0, 0
libinput Button Scrolling Button (296): 2
libinput Button Scrolling Button Default (297): 2
libinput Middle Emulation Enabled (298):0
libinput Middle Emulation Enabled Default (299):0
libinput Accel Speed (300): 0.00
libinput Accel Speed Default (301): 0.00
libinput Accel Profiles Available (302):1, 1
libinput Accel Profile Enabled (303):   1, 0
libinput Accel Profile Enabled Default (304):   1, 0
libinput Left Handed Enabled (305): 0
libinput Left Handed Enabled Default (306): 0
libinput Send Events Modes Available (276): 1, 0
libinput Send Events Mode Enabled (277):0, 0
libinput Send Events Mode Enabled Default (278):0, 0
Device Node (279):  "/dev/input/event8"
Device Product ID (280):1133, 16514
libinput Drag Lock Buttons (307):   
libinput Horizontal Scroll Enabled (308):   1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-30 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: xfce4-settings 4.14.3-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1893638] [NEW] X forgets middle mouse button exists

You have been subscribed to a public bug:

Assuming this is the xorg package but could be wrong.

Running a Logitech MX master 3 mouse, the middle mouse copy/paste isn't
working out the box or is only working intermittently on boot. Using
'xinput --list-props 15' I'm seeing that the 'Middle Emulation Enabled
(298)' is set to 0. If I set this to '1' by using 'xinput --set-prop 15
298 1' then turn the mouse off/on then I regain functionality. If I then
switch to another computer attached to my KVM switch and back to this
machine, the input is lost again. Attempting to set the default (299)
value results in this error:

X Error of failed request:  BadAccess (attempt to access private resource 
denied)
  Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  57 ()
  Serial number of failed request:  20
  Current serial number in output stream:  21

I can script this to get around it, it's just messy and unnecessary


Copy of output from xinput --list-props:

Device 'Logitech MX Master 3':
Device Enabled (155):   1
Coordinate Transformation Matrix (157): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Natural Scrolling Enabled (291):   0
libinput Natural Scrolling Enabled Default (292):   0
libinput Scroll Methods Available (293):0, 0, 1
libinput Scroll Method Enabled (294):   0, 0, 0
libinput Scroll Method Enabled Default (295):   0, 0, 0
libinput Button Scrolling Button (296): 2
libinput Button Scrolling Button Default (297): 2
libinput Middle Emulation Enabled (298):0
libinput Middle Emulation Enabled Default (299):0
libinput Accel Speed (300): 0.00
libinput Accel Speed Default (301): 0.00
libinput Accel Profiles Available (302):1, 1
libinput Accel Profile Enabled (303):   1, 0
libinput Accel Profile Enabled Default (304):   1, 0
libinput Left Handed Enabled (305): 0
libinput Left Handed Enabled Default (306): 0
libinput Send Events Modes Available (276): 1, 0
libinput Send Events Mode Enabled (277):0, 0
libinput Send Events Mode Enabled Default (278):0, 0
Device Node (279):  "/dev/input/event8"
Device Product ID (280):1133, 16514
libinput Drag Lock Buttons (307):   
libinput Horizontal Scroll Enabled (308):   1
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-08-30 (0 days ago)
InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
NonfreeKernelModules: nvidia_modeset nvidia
Package: xfce4-settings 4.14.3-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Tags:  focal
Uname: Linux 5.4.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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


** Tags: apport-collected focal
-- 
X forgets middle mouse button exists
https://bugs.launchpad.net/bugs/1893638
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg-server 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 1893635] [NEW] three monitor setup hangs

2020-08-31 Thread Vee Tornado

Public bug reported:

I have a Ubuntu 20.04 setup with three almost identical monitors
(1920x1080) connected to a Radeon RX5500XT 8GB. All works fine as long
as I don't turn one of the monitors off and back on.

Whenever that happens, all other monitors briefly go blank and then turn
back on, as if they are being detected again, and all what I see then is
three black screens, with a mouse cursor that still can be moved across
all screens. From that moment on, nothing can be done anymore, and I
have to hit the reset button of the desktop PC.

The monitors have VGA, HDMI and DVI ports. I tried connected them to the
RX5500XT (which has 3xDP+1xHDMI ports), using all possible different
combinations of cables. (DVItoHDMI, DVItoDP, HDMItoHDMI, HDMItoDP). The
problem persists in any case.

Whenever I start the system with only two monitors connected, there is
no problem. If I switch off one of the monitors and back on, I see the
other go blank for a second or two, it turns back on, and the canvas is
properly filled with menu and background without any issue.

Obviously there is also no problem with only one monitor connected.

I experienced this problem with the standard Ubuntu 20.04 amdgpu driver.
So, I tried to install the most recent driver from AMD's website, and
that driver has the same issue.

I tried both gdm3 and lightdm. Same problem.

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

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

Title:
three monitor setup hangs

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

Bug description:
I have a Ubuntu 20.04 setup with three almost identical monitors
(1920x1080) connected to a Radeon RX5500XT 8GB. All works fine as long
as I don't turn one of the monitors off and back on.

Whenever that happens, all other monitors briefly go blank and then
turn back on, as if they are being detected again, and all what I see
then is three black screens, with a mouse cursor that still can be
moved across all screens. From that moment on, nothing can be done
anymore, and I have to hit the reset button of the desktop PC.

The monitors have VGA, HDMI and DVI ports. I tried connected them to
the RX5500XT (which has 3xDP+1xHDMI ports), using all possible
different combinations of cables. (DVItoHDMI, DVItoDP, HDMItoHDMI,
HDMItoDP). The problem persists in any case.

Whenever I start the system with only two monitors connected, there is
no problem. If I switch off one of the monitors and back on, I see the
other go blank for a second or two, it turns back on, and the canvas
is properly filled with menu and background without any issue.

Obviously there is also no problem with only one monitor connected.

I experienced this problem with the standard Ubuntu 20.04 amdgpu
driver. So, I tried to install the most recent driver from AMD's
website, and that driver has the same issue.

I tried both gdm3 and lightdm. Same problem.

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

[Desktop-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

[Summary]
>From the MIR POV the package is mostly ok. The overall topic of smartcard
usage will need some QA testing to be supportable. Only a bit can be done
in autopkgtest due to the special HW requirements but it would be worth to
try that as well as setting up a test lab with the most common respective HW.

This does need a security review, so I'll assign ubuntu-security

Binaries to promote: libccid

TODOs:

Recommended:
- Tests:
  - Special HW - In general and I guess this is true for all packages here.
Canonical should get a set of the common (=the want to be supported) devices
and document those somewhere to make it clear what is regularly tested /
supported vs what is on "hopefully it works" level.
  - Also please try at least if with vsmartcard-vpicc + vsmartcard-vpcd some
autopkgtest time testing could be added to some of these packages.
(I'm not going to repeat this request on all reviews, but overall it is
important for QA on such a new topic.)
- Add symbols tracking (this is a bit vice versa, it is a lib providing a driver
  to be used in ps/sc, but still auto-detect if things change is good)

Required:
- Please subscribe to the package (usually good to be done now already)


[Duplication]
libccid is used to communicate though PC/SC (also on this MIR) with smart cards.
https://wiki.debian.org/Smartcards holds a nice overview, there are a bunch
of special drivers in other packages (not part of this MIR), but ccid covers
the majority of devices listed.

[Dependencies]
OK:
- no other Dependencies to MIR due to this (libc6, libusb-1.0-0)
- no -dev/-debug/-doc packages that need exclusion

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not open a port
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop

Problems:
- does parse data formats
  The ccid protocol - if ever exploited - would be a very great angle of attack
- does deal with system authentication (eg, pam), etc)
  Smartcards can and commonly are used to do auth
- This will need a security review on top of the MIR review

[Common blockers]
OK:
- does not FTBFS currently
- no translation present, but none needed for this case (user visible)?
- not a python/go package, no extra constraints to consider int hat regard

Problems:
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- does have a test suite that runs as autopkgtest
=> Tests of special HW are hard at build time anyway, but a bit more than
nothing would be great. I suggested an overall test with a set of
meant to be supported cards exercising all the components of this MIR.

- The package has a team bug subscriber
This needs a Team subscriber still, Desktop was mentioned to be that, but it
isn't yet. From experience this is easy to be forgotten later. Also subscribing
now will help to see the influx of bugs on the topic and therefore help to be
sure if you want to own this.

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok
- Upstream update history is good (regular and only stable updates)
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- Does not have Built-Using

Problems:
- symbols tracking is not place

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as I can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- no embedded source copies
- not part of the UI for extra checks

** Changed in: ccid (Ubuntu)
 Assignee: Christian Ehrhardt  (paelzer) => Ubuntu Security Team 
(ubuntu-security)

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

Title:
  [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite

Status in ccid package in Ubuntu:
  New
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  New
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  New
Status in pcsc-tools package in Ubuntu:
  New

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop

[Desktop-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite