[Desktop-packages] [Bug 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

[John Hartley]

Hi, did the following installs to try to get Wayland installed:

sudo apt install gnome-session-wayland
sudo apt install gnome-remote-desktop

Still just getting purple splash with no login;

Did "ps -ax | land"

ps -ax | grep land
 2127 tty1 Ssl+   0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session 
--autostart /usr/share/gdm/greeter/autostart
 2338 ?Sl 0:00 /usr/bin/Xwayland :1024 -rootless -noreset -accessx 
-core -auth /run/user/126/.mutter-Xwaylandauth.77M8A0 -listen 4 -listen 5 
-displayfd 6
 4651 pts/0S+ 0:00 grep --color=auto land

So Xwayland appears to be started, so not sure why I am just getting
splash and no login prompt.

Thank,

John.

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1300004] Re: gedit does not elevate privileges while it's being launched

[Floyd Taylor]

Old version of gedit that installed by default in Ubuntu 18.04.3 clean
install just done today allows saving a file or "save as" to any
directory. Snap version of "Text Editor" which purports to be gedit
version 3.32.0 can't save a file anywhere I've tried. The error is that
I don't have permission even though I do have permission to Read AND
Write files in the directories I've tried.

Thinking that there may have been conflict, I uninstalled "old gedit"
via sudo apt remove gedit, then uninstalled and reinstalled "New gedit"
aka "Text Editor" from the Ubuntu Software app. No improvement.

FWIW if it's supposed to be gedit call it gedit. Look at VLC for an
example of old version and new snap version both listed and installable
in the Ubuntu Software store. Choose the version you want. It's a new
VERSION with a new install source not a new App.

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

Title:
  gedit does not elevate privileges while it's being launched

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  When I run gedit as normal user and try to change some file inside a
  system (for example, /etc/fstab) it doesn't allow me to write changes
  directly to that file. Instead, I can save file in my home directory,
  then move it on the right place with sudo mv. Other option is to copy
  it's content inside clipboard, relaunch gedit as root, then paste and
  save in appropriate place.

  These paths are not convenient, because I have to do a lot of
  unnecessary work, searching for the file twice or typing it's location
  into terminal. Imagine a situation when file cannot be saved and gedit
  asks for root password and escalates privileges automatically so we
  can now write directly to that file. Kedit can do this. Can we embed
  such functionality inside gedit?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gedit 3.8.3-0ubuntu3 [modified: usr/bin/gedit 
usr/lib/x86_64-linux-gnu/gedit/libgedit-private.so]
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Mar 31 10:28:06 2014
  InstallationDate: Installed on 2013-09-10 (201 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852399] [NEW] ?

[Zoran Stojilovic]

Public bug reported:

There is problem with video play on facebook

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 13 09:09:59 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Integrated Graphics Controller [1043:1de0]
InstallationDate: Installed on 2019-11-10 (2 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X540NA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=0d23bb72-2da5-41a9-b4cc-6c7a100ca090 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X540NA.311
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X540NA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540NA.311:bd08/22/2018:svnASUSTeKCOMPUTERINC.:pnX540NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X540NA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  ?

Status in xorg package in Ubuntu:
  New

Bug description:
  There is problem with video play on facebook

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 09:09:59 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Integrated Graphics Controller [1043:1de0]
  InstallationDate: Installed on 2019-11-10 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540NA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=0d23bb72-2da5-41a9-b4cc-6c7a100ca090 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540NA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540NA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modal

[Desktop-packages] [Bug 1835541] Re: ibus only provides non-standard UK keyboard layouts

[Gunnar Hjalmarsson]

** Bug watch added: github.com/ibus/ibus/issues #2153
   https://github.com/ibus/ibus/issues/2153

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2153
   Importance: Unknown
   Status: Unknown

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

Title:
  ibus only provides non-standard UK keyboard layouts

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Confirmed
Status in ibus package in Debian:
  Confirmed

Bug description:
  When I attempt to add my standard UK keyboard to the layouts ibus
  knows about, I cannot do so.

  (See the attached image for the list of available layouts.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Jul  5 10:07:41 2019
  InstallationDate: Installed on 2019-05-07 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago)

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

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

[Desktop-packages] [Bug 1851964] Re: Volume indicator lags behind scroll action to change volume

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1851964

Title:
  Volume indicator lags behind scroll action to change volume

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

Bug description:
  Changing the volume with the help of the mouse/touchpad, scrolling on
  top of the sound icon used to work fine in the older versions of gnome
  shell. In Ubuntu 19.10, it does not. I scroll, but the graphic
  indicator that shows on the screen lags behind, even jumps. If needed,
  I could try to record it as video. There is definitely some
  performance issue over there.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc6-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  9 23:50:04 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-10-19 (21 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  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/1851964/+subscriptions

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

[Desktop-packages] [Bug 1850893] Re: chromium-browser does not resolve any names

[Sachin Garg]

Agree with comment #22 - however why does does the SNAP version not
work?

Just updated to the EDGE channel [Version 80.0.3962.2 (Official Build)
snap (64-bit)] - but to no avail.

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

Title:
  chromium-browser does not resolve any names

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  OS:
  ===
  Description:  Ubuntu 19.10
  Release:  19.10

  Chromium Browser:
  =
  Version 78.0.3904.70 (Official Build) snap (64-bit)

  
  DNS resolution does not work in Chromium Browser since Ubuntu updated from 
18.04 -> 19.10 and chromium moved from package to SNAP.

  DNS works in Mozilla Firefox (being used to submit this bug report) as
  well as in Google Chrome (Version 78.0.3904.87 (Official Build)
  (64-bit))

  See attached screenshots.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLSwNV1BaQhYdAQOANB14KlKVpVZUnSUOUFS7jACzAIHAgQCBgJUAqcABAQEBAjqAGHE4LUBYLEUACSUhAAAe/QAySB5REQAKICAgICAg/ABDMjRGMzkwCiAgICAg/wBINFpNNTAwMTE1CiAgAVMCAxrxRpAEHxMSAyMJBweDAQAAZgMMABAAgAEdALxS0B4guChVQAklIQAAHowK0JAgQDEgDEBVAAklIQAAGIwK0Iog4C0QED6WAAklIQAAGAAAyQ==
   modes: 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 
1440x900 1280x800 1280x720 1280x720 1280x720 1280x720 1280x720 1024x768 
1024x768 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 
720x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5fgGAAEaAQSlHRB4AviQnllVnCYaUFQBAQEBAQEBAQEBAQEBAQEBPhxWoFAAFjAwIDYAJaUQAAAanhZWoFAAFjAwIDYAJaUQAAAaAgARQ/8PPOZBRjrmAAM=
   modes: 1366x768 1366x768
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/mapper/shoor-home xfs194G  171G   24G  88% /home
   tmpfs  tmpfs  7.8G  186M  7.6G   3% /dev/shm
   /dev/mapper/shoor-home xfs194G  171G   24G  88% /home
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-05-02 (558 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: HP HP ProBook 430 G5
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=2dbdc9ef-f608-4d62-83ff-348f47118c15 ro 
resume=UUID=ff6eebb5-8c92-4fad-af15-00ccb0e08484
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.97 
(021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859})
  Snap.ChromiumVersion: Chromium 78.0.3904.97 snap
  Tags:  eoan snap
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
tty vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: Q85 Ver. 01.01.07
  dmi.board.name: 8377
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.21.00
  dmi.chassis.asset.tag: 5CD750DHFQ
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ85Ver.01.01.07:bd10/17/2017:svnHP:pnHPProBook430G5:pvr:rvnHP:rn8377:rvrKBCVersion02.21.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 430 G5
  dmi.product.sku: 3EB74PA#ACJ
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works

[Andreas Pokorny]

I recently had to switch my company card and it now uses a newer version
so it get mis-identified by pcsc-lite from debian - but works fine in
the latest release of pcsc-lite. As companies like Atos seem to
frequently roll out new versions of their cards it would be nice if we
could have opensc (I assume this is also in use - not sure whether it is
client or server side) and pcsc-lite in a separate snap built from a
more recent source

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

Title:
  [snap] smart card reader no longer works

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium uses the Netscape Cryptographic Module to access smartcards
  for authentication purposes. This stopped working when switching to
  the snap version. Chromium would normally access the setup in
  ~/.pki/nssdb/pkcs11.txt That file  would refer to a library used to
  access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc-
  pkcs11.so

  The problem can be bypassed by manually launching chromium via:
  /snap/chromium/current/usr/lib/chromium-browser/chrome

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

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

[Desktop-packages] [Bug 602809] Re: add Mouse Click Debounce Feature?

[Herman Grobler]

Is there any update on this, I use a MSI mouse and MSI keyboard. The issue is 
most notable on my mouse, but I have duplicate key press events on my keyboard 
as well.
I'm sure allowing the debounce delay to be configurable will be a quick win 
here as JohnWashington suggested.

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

Title:
  add Mouse Click Debounce Feature?

Status in xserver-xorg-input-evdev:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Confirmed

Bug description:
  Model:  bonp3
  OS:  Ubuntu 10.04 LTS

  When I single click the mouse (external USB Mouse - Mouse Pad
  disabled) half the time the system responds as though I have double
  clicked the mouse.  I try 2 different USB mouse units and it still
  does this.  I am running Ubuntu 10.04 on a separate PC that does not
  have this mouse problem.  So I am thinking this problem is a System76
  driver issue???

  It's annoying.  :(

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Marcin P]

** Attachment added: "alsa-info.txt.success-internal-headphones"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305010/+files/alsa-info.txt.success-internal-headphones

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Marcin P]

** Attachment added: "alsa-info.txt.failed-built-in-speaker.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305009/+files/alsa-info.txt.failed-built-in-speaker.txt

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Marcin P]

I installed modified kernal:
5.0.0-34.36+conexant-codec-generic #codec SMP Tue Nov 12 22:40:14 CST 2019 
x86_64 x86_64 x86_64 GNU/Linux

After system startup there is no sound from built-in speakers.
After connecting headphones sound works correctly in headphones.
After disconnecting headphones again there is no sound from built-in speakers.

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Marcin P]

I have some additional observations (on regular kernel: 5.0.0-35-generic
#38~18.04.1-Ubuntu SMP Mon Nov 11 09:16:10 UTC 2019 x86_64 x86_64 x86_64
GNU/Linux):

I also have a HP docking station which has its own separated built-in
DAC. When laptop is connected to this docking station I can choose from
following sound devices:

- Digital Output (S/PDIF) - USB Audio
- Analog Output - USB Audio
- Speakers - Built-in Audio

When I don't connect headphones I can switch between these devices and
when coming back to built-in speakers the speakers usually work (however
sometimes they don't). But after connecting headphones the speakers will
never work again.

To clarify: all previous tests I did were done on laptop disconnected
from docking station.

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Marcin P]

** Attachment added: "alsa-info.txt.still-failed-built-in-speakers"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305011/+files/alsa-info.txt.still-failed-built-in-speakers

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1852265] Re: Nautilus hangs when right-click->properties is selected on file

[Kalle Tuulos]

I noticed that RabbitVCS / checkerservice.py was the reason for hanging.
After I removed the RabbitVCS installation, Nautilus doesn't hang any
more.

Could this bug be moved to rabbitvcs-nautilus?

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

Title:
  Nautilus hangs when right-click->properties is selected on file

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Ubuntu 18.04.3 LTS

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  nautilus:
Installed: 1:3.26.4-0~ubuntu18.04.4
Candidate: 1:3.26.4-0~ubuntu18.04.4
Version table:
   *** 1:3.26.4-0~ubuntu18.04.4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  3) What you expected to happen
  4) What happened instead

  A directory containing any amount of files (may be just few, may be
  hundreds of files) is opened. Some file is right-clicked and
  Properties is selected, after which Nautilus hangs immediately.

  It can be killed with "killall -9 nautilus" command, after which one
  must wait for short time before Nautilus can be started again.

  If it is started too soon, it will not start, it just prints text:
  "Failed to register: Timeout was reached"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Nov 12 15:58:19 2019
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'958x757+2151+138'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'RabbitVCS::age_column', 
'RabbitVCS::author_column', 'RabbitVCS::revision_column', 
'RabbitVCS::status_column']"
  InstallationDate: Installed on 2018-10-25 (383 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

[Morten Kjeldgaard]

Re: "unsigned" I figured it out, however, my boot partition is UEFI, so
I probably can't use an unsigned image.

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
 

[Desktop-packages] [Bug 1848847] Re: Suspend and resume stopped working with nouveau driver after upgrade to 19.10

[b8e5n]

For me, the problem persists with 5.3.0-19.

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

Title:
  Suspend and resume stopped working with nouveau driver after upgrade
  to 19.10

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Under Nouveau driver, suspend and resume of my laptop stopped working
  after i upgraded from 19.04 to 19.10.

  When desktop lid is closed, the fans will kick in and turn until
  battery is empty or hard shutdown using the power button.

  Worked before under xorg and wayland. Now doesn't work with either.
  Works with Nvidia driver 340.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 19 13:30:53 2019
  DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-17-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9]
  InstallationDate: Installed on 2019-01-12 (279 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBookPro5,5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to eoan on 2019-10-06 (12 days ago)
  dmi.bios.date: 06/15/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP55.88Z.00AC.B03.0906151708
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F2268AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBookPro5,5
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1848847] Re: Suspend and resume stopped working with nouveau driver after upgrade to 19.10

[b8e5n]

Sorry for the spam, but there happens to be a new kernel available just now.
The problem persists with 5.3.0-22.

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

Title:
  Suspend and resume stopped working with nouveau driver after upgrade
  to 19.10

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Under Nouveau driver, suspend and resume of my laptop stopped working
  after i upgraded from 19.04 to 19.10.

  When desktop lid is closed, the fans will kick in and turn until
  battery is empty or hard shutdown using the power button.

  Worked before under xorg and wayland. Now doesn't work with either.
  Works with Nvidia driver 340.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 19 13:30:53 2019
  DistUpgraded: 2019-10-06 16:30:12,792 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-17-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00b9]
  InstallationDate: Installed on 2019-01-12 (279 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Apple Inc. MacBookPro5,5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=595c74ec-799d-4c25-bc8d-f06155d59f97 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to eoan on 2019-10-06 (12 days ago)
  dmi.bios.date: 06/15/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP55.88Z.00AC.B03.0906151708
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F2268AC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268AC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8:
  dmi.product.family: MacBook
  dmi.product.name: MacBookPro5,5
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1780678] Re: [snap] Chromium cannot use WebUSB

[Erik van Konijnenburg]

Tested with the Numworks calculator v0100, Ubuntu 19.10.

$ dpkg -l chromium-browser
...
ii  chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 amd64Transitional 
package - chromium-browser -> chromium snap
$ snap changes
ID   Status  Spawn   Ready   Summary
36   Donetoday at 10:20 CET  today at 10:20 CET  Refresh "chromium" snap 
from "candidate/raw-usb-test" channel
$ snap interface raw-usb
name:raw-usb
summary: allows raw access to all USB devices
slots:
  - core
$ sudo snap connect chromium:raw-usb
error: snap "chromium" has no plug named "raw-usb"

And without this connect, chrome://device-log/ says 'operation not permitted',
as designed.

At this point, the workaround of using chromium without a snap wrapper
seems no longer available.  The snap system knows something about raw-
usb, but the chromium snap from the raw-usb-test channel does not want
to connect to it.

Let me know when you want further testing.

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

Title:
  [snap] Chromium cannot use WebUSB

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  We're running into a weird bug on Ubuntu : WebUSB works on Chrome but
  doesn't on Chromium!

  Here's our udev rule:

  https://workshop.numworks.com/files/drivers/linux/50-numworks-
  calculator.rules

  It uses the uaccess tag which adds an ACL to the created file in /dev/
  so that the current logged-in user has RW access to the corresponding
  /dev/bus/usb/** device. Apparently that's the way to go, since relying
  on groups is fragile (not all distros use the "plugdev" group for
  example).

  That udev rules works just fine. When using a command-line utility
  such as "dfu-tool", the USB device is seen and can be read from and
  written to. It also works just fine on Chrome. But Chromium gives us
  an "access denied" error. It lists the device, we do get the pop-up,
  but we cannot communicate. On Chromium, chrome://device-log says :

  Failed to open /dev/bus/usb/001/011: Operation not permitted (1)

  Here are the infos on said file:

  user@virtualbox:~$ ls -l /dev/bus/usb/001/011
  crw-rw-r--+ 1 root root 189, 10 Jul  3 11:35 /dev/bus/usb/001/011

  As you can see, the file is owned root/root, but has an ACL (as shown
  by the "+" symbol)

  user@virtualbox:~$ getfacl /dev/bus/usb/001/011
  getfacl: Removing leading '/' from absolute path names
  # file: dev/bus/usb/001/011
  # owner: root
  # group: root
  user::rw-
  user:user:rw-
  group::rw-
  mask::rw-
  other::r--

  Here the ACL supposedely gives RW access to "user" who is indeed the
  current logged-in user, and the user running Chromium and Chrome.

  For reference :
   - Latest stable Ubuntu (18.04)
   - Using the Chromium that ships with Ubuntu (from the Ubuntu Software app. 
attached chrome://version page)
   - And using latest stable Chrome from google.com (attached chrome://version 
page)

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

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

[Desktop-packages] [Bug 1835541] Re: ibus only provides non-standard UK keyboard layouts

[Bug Watch Updater]

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

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

Title:
  ibus only provides non-standard UK keyboard layouts

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed
Status in ibus package in Debian:
  Confirmed

Bug description:
  When I attempt to add my standard UK keyboard to the layouts ibus
  knows about, I cannot do so.

  (See the attached image for the list of available layouts.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Jul  5 10:07:41 2019
  InstallationDate: Installed on 2019-05-07 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago)

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

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

[Desktop-packages] [Bug 1850127] Re: Unable to print with Brother printer since upgrade to Ubuntu 19.10

[Till Kamppeter]

As your printer is working again now and we are not able to investigate
the original problem I am closing this bug now.

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

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

Title:
  Unable to print with Brother printer since upgrade to Ubuntu 19.10

Status in cups package in Ubuntu:
  Invalid

Bug description:
  I have recently bought a new color laser printer (Brother HL-
  L8260CDW), which is connected through wLAN. It works like a charm
  under Ubuntu 19.04, but refuses to print since the upgrade to stock
  Ubuntu 19.10. I can reach it via ping and through its HTTP config page
  from the same computer.

  During my collection of relevant bug information I discovered the
  following error messages:

  1. Some print filter was unable to grep 
/etc/cups/ppd/Brother_HL_L8260CDW_series.ppd
  This file was rw for user "root" and r for group "lp", but not accessible 
to others.
  I have made it world readable for testing purposes, but I still can't 
print.

  2. I checked /var/log/syslog for app-armour errors but found none which would 
be related
  to cups and/or printing

  3. After fixing the permission issue, the new error message is "File \'\' not 
found" and
  "Unable to add document to print job.", both of which are too cryptic for 
me to dig
  further into this by myself.

  
  Attached to this bug report I send the following pieces of information:
  - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt)
  - output from "lpinfo -v" (lpinfo.txt)
  - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" 
(avahi.txt)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   E [28/Oct/2019:10:40:04 +0100] [Job 112] File \'\' not found
   E [28/Oct/2019:10:40:12 +0100] [Job 112] Unable to add document to print job.
   E [28/Oct/2019:10:45:59 +0100] [Job 113] File \'\' not found
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 10:50:05 2019
  InstallationDate: Installed on 2015-11-11 (1446 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Brother_HL_L8260CDW_series: 
implicitclass://Brother_HL_L8260CDW_series/
  MachineType: MSI MS-7982
  Papersize: a4
  PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=64458150-bde5-4ffc-8eb1-038fae855347 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO-DH (MS-7982)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd07/08/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-DH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7982
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

[Peter D.]

@Morten

I think that all Ryzen motherboards are going to have UEFI firmware
rather than the old BIOS firmware - even though everyone keeps using the
old name.

If it is your computer and you know what you are doing you could turn
off secure boot.  If you don't know, then don't do it.

I grabbed all of these files;

CHECKSUMS
CHECKSUMS.gpg
linux-headers-5.4.0-050400rc7_5.4.0-050400rc7.201911102031_all.deb
linux-headers-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb
linux-image-unsigned-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb
linux-modules-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb

@Kai-Heng

Rc7 is better than rc6, but not a lot.

I might have imagined the part about the VGA port being reported as a
VGA port.  Sorry.  That was probably when I had the graphics card
plugged in.  The VGA port is being reported as a second Display Port
again.

With a fresh install of Eoan Ermine Xubuntu, updates, and rc7;

Standard boot gives a badly pixelated display for menus, moving windows,
changing text; xrandr reports reasonable things, then after 10 or 20
minutes the machine locks up.

Booting with safe graphics from the grub menu gives a stable display,
but xrandr seems confused and only reports one mode with a 77 Hz
vertical refresh rate, and no mention of any ports.

Do you want log files, or anything in particular?

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dm

[Desktop-packages] [Bug 1849859] Re: error when connecting to smb server

[Launchpad Bug Tracker]

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

** Changed in: system-config-printer (Ubuntu)
   Status: New => Confirmed

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

[Peter D.]

Correction:

Rc7 sometimes boots in the standard way.  Sometimes it goes to a black
screen.

Rc7 boots reliably from the *recovery* mode in the grub menu.

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

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfil

[Desktop-packages] [Bug 1851385] Re: ubuntu 19.10 / print bug : requires authentication

[Till Kamppeter]

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

** This bug has been marked a duplicate of bug 1849859
   error when connecting to smb server

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1849859] Re: error when connecting to smb server

[Launchpad Bug Tracker]

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

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

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1849859] Re: error when connecting to smb server

[Launchpad Bug Tracker]

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

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

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Hui Wang]

Please remove any modle= from alsa-base.conf

Install the testing kernel and reboot, then test headphone and speaker with the 
testing kernel.
https://people.canonical.com/~hwang4/samsung-test/
(to install the testing kernel, sudo dpkg -i linux-modules-xxx.deb; sudo dpkg 
-i linux-image-xxx.deb; sudo dpkg -i linux-modules-extra-.deb)

If headphone and speaker still don't work, please run this script and
retest the headphone and speaker again.

then upload the dmesg and alsa-info.txt-with-coeff

** Attachment added: "set-coeff.sh"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305138/+files/set-coeff.sh

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture

[Desktop-packages] [Bug 1851824] Re: gnome shell freezes when too many notifications appear

[fcole90]

Thanks. I created a log with `journalctl --since "2019-11-08 13:00:00"
--until "2019-11-08 13:26:49" > ~/gnome_hung_logs.txt` which I then
cleaned up of unnecessary events, like nm reconnecting or similar
unuseful logs.

** Attachment added: "gnome_hung_logs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851824/+attachment/5305140/+files/gnome_hung_logs.txt

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

Title:
  gnome shell freezes when too many notifications appear

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using 20.04. When I receive some notifications immediately one
  after the other, the shell sometimes freezes.

  I usually make it start again moving to a vt and doing `killall -3
  gnome-shell`.

  This makes it work again (except it makes some apps like PyCharm and
  Chrome to crash).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 13:26:49 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-03 (277 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago)

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Hui Wang]

Please do a test.

Boot with the regular kernel (5.0.0-35-generic), make sure the speakers
can work after booting, then run:

amixer sset 'Auto-Mute Mode' 'Disabled'

After that plug a headphone and unplug the headphone, does the speaker
still work?

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Martin S]

Install the testing kernel and reboot, 


Couldn't boot after installing all 3 .deb's:

error: /boot/vmlinuz-5.3.0.23.25+samsung-test-generic has invalid signature
error: you need to load the kernel first

Press any key to continue...

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviro

[Desktop-packages] [Bug 1852315] Re: CVE‑2019‑5696 5697 5698

[Alberto Milone]

Changed to public. Thanks

** No longer affects: nvidia-graphics-drivers-390 (Ubuntu Bionic)

** No longer affects: nvidia-graphics-drivers-390 (Ubuntu Disco)

** No longer affects: nvidia-graphics-drivers-390 (Ubuntu Eoan)

** Information type changed from Private Security to Public Security

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

Title:
  CVE‑2019‑5696 5697 5698

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-418 source package in Bionic:
  New
Status in nvidia-graphics-drivers-430 source package in Bionic:
  New
Status in nvidia-graphics-drivers-435 source package in Bionic:
  New
Status in nvidia-graphics-drivers-418 source package in Disco:
  New
Status in nvidia-graphics-drivers-418 source package in Eoan:
  New
Status in nvidia-graphics-drivers-430 source package in Eoan:
  New
Status in nvidia-graphics-drivers-435 source package in Eoan:
  New

Bug description:
  According to NVIDIA's security bulletin, the driver series ranging from 418 
to 430 seem to be affected:
  https://nvidia.custhelp.com/app/answers/detail/a_id/4907

  Here are the relevant CVEs:

  CVE‑2019‑5696
  CVE‑2019‑5697
  CVE‑2019‑5698

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

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

[Desktop-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Lilian Tao]

in reply to #23, @hui.wang please find the dump from window10 in
attachment.

** Attachment added: "RtHDDump-20191113.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5305169/+files/RtHDDump-20191113.txt

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

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

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

[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Martin S]

Hi,

1) Steps:
- Removed the option model=
- Rebooted
- turned off Secure Boot and booted with your test kernel.


Result:
No sound from speakers.
Very very quiet headphones.


2) Steps:
sudo set-coeff.sh
sudo su
echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef

Result:
No sound from speakers.
Very very quiet headphones.

alsa-info is attached.

Thanks,
Martin


** Attachment added: "alsa-info-with-coefficients-after-set-coeff.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305170/+files/alsa-info-with-coefficients-after-set-coeff.txt

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   

[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

[Martin S]

dmesg output attached from #21, step 2)


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305171/+files/dmesg.txt

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Sour

[Desktop-packages] [Bug 1852440] [NEW] Please give us back our chromium package on ppa, no one want snaps

[medin2014]

Public bug reported:

Please, we as ubuntu community the first thing we do after installing
Ubuntu is removing that crappy snap from our system, it's slow to
install and takes huge size on disk, and most of apps installed by snap
doesn't work, please make new version via ppa, please.

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

Title:
  Please give us back our chromium package on ppa, no one want snaps

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Please, we as ubuntu community the first thing we do after installing
  Ubuntu is removing that crappy snap from our system, it's slow to
  install and takes huge size on disk, and most of apps installed by
  snap doesn't work, please make new version via ppa, please.

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

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

[Desktop-packages] [Bug 1849859] Re: error when connecting to smb server

[Till Kamppeter]

For me it looks like that something changed in Samba. Printing on such a
server is done via the /usr/lib/cups/backend/smb CUPS backend which is
part of the smbclient package.

Is there no way to access the printer on the NAS via IPP?

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1851931] [NEW] On-screen keyboard does not appear automatically when selecting some text fields on Eoan

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop
and a desktop.

The OSK pops up fine on terminal, login field and text editor. It also
doesn't work on Chrome.

Curiously, when swiping up with mouse on the laptop the OSK doesn't come
up when Chromium is on the view, but it comes up when on desktop.

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


** Tags: eoan
-- 
On-screen keyboard does not appear automatically when selecting some text 
fields on Eoan
https://bugs.launchpad.net/bugs/1851931
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to chromium-browser 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 1851931] Re: On-screen keyboard does not appear automatically when selecting some text fields on Eoan

[Paul White]

** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu)

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

Title:
  On-screen keyboard does not appear automatically when selecting some
  text fields on Eoan

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I get this on Eoan, no OSK pop up for Chromium text fields, on a
  laptop and a desktop.

  The OSK pops up fine on terminal, login field and text editor. It also
  doesn't work on Chrome.

  Curiously, when swiping up with mouse on the laptop the OSK doesn't
  come up when Chromium is on the view, but it comes up when on desktop.

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

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

[Desktop-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

[Dariusz Gadomski]

Joe, I still can't reproduce your issue.
Can you please verify against what I'm trying:
1. Setup a VPN that provides DNS via DHCP
2. Connect to that VPN and verify DNS by:
$ systemd-resolve --status
(...)
Link 4 (tun0)
(...)
DNS Servers: X.X.X.X
(...)
3. Disconnect VPN and edit connection:
$ nmcli connection edit myvpn
nmcli> set ipv4.dns-priority -30
nmcli> save
$ nmcli connection show myvpn | grep dns-priority
ipv4.dns-priority:  -30
ipv6.dns-priority:  0

4. Re-connect to VPN and try to reach a name within the VPN:
$ dig some.host.in.my.vpn

I have used:
$ apt-cache policy network-manager
network-manager:
  Installed: 1.10.6-2ubuntu1.2

Please tell me in which of the steps in your case network-manager
behaves differently.

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

[Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google

[Timo Jyrinki]

Reflecting current status per series, adjust as needed.

The upstream bug says fixed in 68.2.1, which is currently in proposed
for eoan and bionic.

** Also affects: thunderbird (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: thunderbird (Ubuntu Focal)
   Importance: High
 Assignee: Olivier Tilloy (osomon)
   Status: Triaged

** Also affects: thunderbird (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: thunderbird (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: thunderbird (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: thunderbird (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: thunderbird (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: thunderbird (Ubuntu Disco)
   Status: New => Triaged

** Changed in: thunderbird (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: thunderbird (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: thunderbird (Ubuntu Eoan)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: thunderbird (Ubuntu Disco)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Bug watch added: Mozilla Bugzilla #1592407
   https://bugzilla.mozilla.org/show_bug.cgi?id=1592407

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1592407
   Importance: Unknown
   Status: Unknown

** Changed in: thunderbird (Ubuntu Focal)
   Status: Triaged => Fix Released

** Changed in: thunderbird (Ubuntu Eoan)
   Status: Triaged => Fix Committed

** Changed in: thunderbird (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Changed in: thunderbird (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: thunderbird (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: thunderbird (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: thunderbird (Ubuntu Bionic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: thunderbird (Ubuntu Xenial)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Authentication constantly re-requested for Google

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Triaged
Status in thunderbird source package in Bionic:
  Fix Committed
Status in thunderbird source package in Disco:
  Triaged
Status in thunderbird source package in Eoan:
  Fix Committed
Status in thunderbird source package in Focal:
  Fix Released

Bug description:
  When I use Thunderbird, it keeps failing to connect with my Google
  (Gmail) accounts. It keeps asking for authentication via the web
  portal, I seem to successfully give Thunderbird authentication, but no
  messages come in and, soon afterwards, the web portal comes up asking
  for login again.

  I am using OAuth2 (so this ( https://support.mozilla.org/en-
  US/questions/1201406 ) doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   3444 F pulseaudio
   /dev/snd/pcmC0D0p:   adam   3444 F...m pulseaudio
  BuildID: 20191007090404
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 14:56:50 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-03 (817 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown
   172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so 
(browser-plugin-freshplayer-pepperflash)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404
  RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or m

[Desktop-packages] [Bug 1852363] Re: Non working button to open the printers configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  Non working button to open the printers configuration

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Using 19.10 with the current snap
  - click print
  - in the print dialog, select the 'destination' 'see more' option
  - click the manage button at the bottom

  The printers line has an icon to open the printer configuration dialog
  which doesn't work, it probably tries to call a command which isn't
  available from the snap environment?

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

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

[Desktop-packages] [Bug 1824282] Re: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU

[Doug McMahon]

New bug 
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1851416

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

Title:
  Add a mode that load nvidia.ko only so that we display on intel and do
  cuda deep learning in NV GPU

Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  Per current NV and intel GPU driver, if we load nvidia.ko only, we can
  do display on intel GPU and leave the NV to deep learning for a
  graphic workstation.

  I proposed to add a mode might call "intel+nv_cuda" for this mode.

  Test procedure:

  1. install the new package on a platform with both intel and NV graphic card.
  2. $ sudo prime-select intel+nv_cuda; sudo reboot
  3. $ nvidia-smi # it will show the nvidia GPU status and we will found that 
no GUI process use any NV GPU memory.

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

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

[Desktop-packages] [Bug 1113420] Re: Alt+ window menu shortcuts cannot be disabled

[Samuel Tissot]

A little workaround that I found

the alt-r key does not trigger for me the HUD. So I reprogrammed my
keyboard alt-l to be alt-r as well.

works for me. I hope it helps until this is fixed/changed.

NOTE. I do have a programmable keyboard. I do not know if it works with
software keymapping solution

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

Title:
  Alt+ window menu shortcuts cannot be disabled

Status in Unity:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I find the  key ergonomically very useful (it can be pressed with
  a thumb without moving any of the "letter" fingers) and I would like
  to use it for many custom keyboard shortcuts (there is a reason why it
  plays such a big role in Emacs and the whole OS X for that matter).

  Currently, though,  is hardcoded to activate window menu entries
  (such as +F for the file menu, +E for the edit menu) and
  there is no way to surpass this functionality in all the applications.
  Personally, I find these shortcuts quite useless - they take you to
  "copy", "paste", and "open file" which have standard shortcuts anyway
  (with the exception of preferences, which for some reason don't have a
  standardized shortcut even though that's often the only thing a person
  looks for up there).

  Expected behaviour
  -

  What I would like to see is a global option to disable these alt+
  menu shortcuts to free up the  key for other uses (similar to the
  option already available in gnome-terminal, only global). Preferably,
  activating this option would also remove the first-letter underlining
  in the menu to indicate to users that they can't acess it through
  shortcuts.

  To reproduce:
  -

  - in Unity settings -> keyboard -> Shortcuts -> Launchers change the "Launch 
terminal" shortcut to ALT+T
  - hit -t, new terminial pops up
  - start Thunderbird or Okular, both of which have a "Tools" menu
  - note -t now opens the Tools menu
  - kill the application
  - hit -t, nothing happens

  (I marked nautilus for apport to collect my version numbers, but this
  affects most applications - didn't know what the right target is)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Sat Feb  2 13:22:32 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'931x626+1+80'"
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2012-10-19 (106 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google

[Bug Watch Updater]

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

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


On 2019-10-29T20:37:21+00:00 Ka-adm0n-v1 wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101
Firefox/70.0

Steps to reproduce:

Clean install Thunderbird 68.2
- Add Gmail account
- Fill in Google Authentication popup window and allow app
- Fails at next window


Actual results:

Email is not synced at all

Warning saying:
Unable to log in at server. Probably wrong configuration, username or password

Password & username is correct


Expected results:

Login should Continue and account should start syncing email

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


On 2019-10-29T20:43:56+00:00 Ka-adm0n-v1 wrote:

Tried older versions and latest Thunderbird beta 71 with the same results
Maybe Google has changed something with their OAuth2 requirements ?

Also should note the email is not auto-filled in the Google login popup
(this used to be auto-filled)

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


On 2019-10-29T21:18:31+00:00 Ka-adm0n-v1 wrote:

Created attachment 9105051
Log from login process

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


On 2019-10-29T22:08:16+00:00 Wls220spring wrote:

I test creating my Google IMAP account and Comcast POP3 account with
every release candidate. I had no problem creating the accounts when
testing the 68.2 candidate on Ubuntu 18.04.2 LTS. I still have that test
profile and I can get mail on the account.

After seeing this bug report in my Gmail Bugzilla folder,  I tested my
68.2 with a test profile on both Windows 10 and Ubuntu, and can
reproduce the problem.

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


On 2019-10-29T22:36:05+00:00 Wls220spring wrote:

I just tested creating the account with a new test profile using 71.0b1
on Ubuntu 18.04.3 LTS and can reproduce.

I don't recall seeing the dialogs from Google that appear now when
testing release candidates.

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


On 2019-10-29T22:45:24+00:00 Jorg K wrote:

No changes in that area between TB 70 beta 4 and TB 71 beta 1. Does it
still work with TB 68?

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


On 2019-10-29T23:00:38+00:00 Jorg K wrote:

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

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


On 2019-10-29T23:01:58+00:00 Jorg K wrote:

Sorry, you said 68.2.0. Hmm, looks like Google finally tightened the
screw. Magnus and Andrei, do you know anything about this?

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


On 2019-10-29T23:05:04+00:00 Wls220spring wrote:

Created attachment 9105072
gmailerrorlog.txt

Creating an account in 68.2 with a test profile. No.

The user would normally get a dialog window with the email address already 
filled in and all they had to do was click "Next" to get to the dialog window 
to enter the password. Now I have to fill in my email or phone number.
Entering the email address and clicking next brings up the window to fill in 
the password, showing my email address and avatar associated with the account.
Typing in the password and clicking next brings up the "Mozilla Thunderbird 
Email wants to access your Google Account" dialog window.
Clicking the "Allow" button is where it fails.

No problem using my account in 68.2 or 70.0b1 or 72.0a1 with the
production profiles on Windows 10 or Linux.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1850651/comments/8


On 2019-10-29T23:09:59+00:00 Jorg K wrote:

I've just confirmed it. After answering all the Google prompts incl.
tying in a code received via SMS, the authentication fails :-( - An
existing account still seems to work.

Repl

[Desktop-packages] [Bug 1851918] Re: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'"

[Till Kamppeter]

** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no
  attribute 'VERSION'"

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New
Status in pillow package in Ubuntu:
  New
Status in python-imaging package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install HPLIP on Ubuntu 19.10 with `sudo apt-get install hplip*`
  2. Run `hp-check -r`

  Expected results:
  * `hp-check -r` runs without errors

  Actual results:
  * `hp-check -r` shows many errors and crashes:

  $ hp-check -r
  Saving output in log file: /home/mate/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.19.6)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
  dependencies are installed to successfully compile HPLIP. 
   
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied   
  tarball has the proper dependencies installed to successfully run.
   
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time  
  dependencies).
   

  Check types:  
   
  a. EXTERNALDEP - External Dependencies
   
  b. GENERALDEP - General Dependencies (required both at compile and run time)  
   
  c. COMPILEDEP - Compile time Dependencies 
   
  d. [All are run-time checks]  
   
  PYEXT SCANCONF QUEUES PERMISSION  
   

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  warning: ubuntu-19.10 version is not supported. Using ubuntu-19.04
  versions dependencies to verify and install...

  ---
  | SYSTEM INFO |
  ---

   Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux
   Host: eoan
   Proc: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux
   Distribution: ubuntu 19.10
   Bitness: 64 bit

  
  ---
  | HPLIP CONFIGURATION |
  ---

  HPLIP-Version: HPLIP 3.19.6
  HPLIP-Home: /usr/share/hplip
  warning: HPLIP-Installation: Auto installation is not supported for ubuntu 
distro  19.10 version 

  Current contents of '/etc/hp/hplip.conf' file:
  # hplip.conf.  Generated from hplip.conf.in by configure.

  [hplip]
  version=3.19.6

  [dirs]
  home=/usr/share/hplip
  run=/var/run
  ppd=/usr/share/ppd/hplip/HP
  ppdbase=/usr/share/ppd/hplip
  doc=/usr/share/doc/hplip
  html=/usr/share/doc/hplip-doc
  icon=no
  cupsbackend=/usr/lib/cups/backend
  cupsfilter=/usr/lib/cups/filter
  drv=/usr/share/cups/drv
  bin=/usr/bin
  apparmor=/etc/apparmor.d
  # Following values are determined at configure time and cannot be changed.
  [configure]
  network-build=yes
  libusb01-build=no
  pp-build=no
  gui-build=yes
  scanner-build=yes
  fax-build=yes
  dbus-build=yes
  cups11-build=no
  doc-build=yes
  shadow-build=no
  hpijs-install=yes
  foomatic-drv-install=yes
  foomatic-ppd-install=no
  foomatic-rip-hplip-install=no
  hpcups-install=yes
  cups-drv-install=yes
  cups-ppd-install=no
  internal-tag=3.19.6
  restricted-build=no
  ui-toolkit=qt5
  qt3=no
  qt4=no
  qt5=yes
  policy-kit=yes
  lite-build=no
  udev_sysfs_rules=no
  hpcups-only-build=no
  hpijs-only-build=no
  apparmor_build=no
  class-driver=no

  
  Current contents of '/var/lib/hp/hp

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

[Pål Bergström]

Didn't know what to include. It's long even if I do -d. But I found an
error with dmar. Not sure what it stands for but it led me to turn of
virtualization in BIOS. Crossing my fingers but it seems better. Though
some apps start very slow compared to 19.04 like FileZilla and FreeCAD.
Could be another thing or. Will see. The problem has been kind of
irrational.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor
  now and then. Problem with multitasking.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 10:29:50 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-10-18 (17 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1850088] Re: permission denied when opening a mounted folder in save file dialog

[david feeney]

@osomon regarding your question "... ~/server works around the
problem?", I have a tmpfs mount in my $HOME (19.10) and it is
inaccessible to chromium.

/etc/fstab
tmpfs /home/david/ramdisk tmpfs rw,size=2048M 0 0

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

Title:
  permission denied when opening a mounted folder in save file dialog

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 19.10, when I tried to open a file into a
  sshfs-mounted folder inside my home folder, it says permission denied.
  This didn't happen at Ubuntu 19.04.

  Steps to reproduce:
  1. Use sshfs to mount a sftp folder on an empty folder inside my home drive 
(e.g. ~/.server)
  2. Create a soft link in the home folder to a folder inside the mounted sftp 
file system (e.g. ~/server > .server/home/michael )
  3. Open chromium
  4. Download a file
  5. Enter that folder in the file dialog

  Expected result:
  I can enter the folder

  Actual result:
  It says permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  DRM.card1-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card1-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBBDGbAJEYAAA8WAQNuMx14LspFpFZLnCUSUFS9SwDRwLMAlQCBgJUPAQEBAQEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxMjE1MDE3OTU2/ABQaGlsaXBzIDIzNENM/QA4TB5TEQAKICAgICAgAHs=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768 
1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400
  Date: Mon Oct 28 10:14:27 2019
  DiskUsage:
   Filesystem   Type   Size  Used Avail Use% Mounted on
   /dev/mapper/vg0-root ext4   230G  190G   29G  87% /
   tmpfstmpfs  7.8G  165M  7.6G   3% /dev/shm
   /dev/mapper/vg0-root ext4   230G  190G   29G  87% /
  InstallationDate: Installed on 2016-10-03 (1119 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vg0-root ro quiet splash resume=/dev/vg0/swap vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70 
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
  Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago)
  dmi.bios.date: 08/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd08/13/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Desktop-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

[Ilario Sanseverino]

I too confirm the bug in Ubuntu 19.10

network-manager 1.1.20.4-2ubuntu2 amd6420.4-2ubuntu2 amd64
network-manager-openconnect 1.2.4-2ubuntu1 amd64
openconnect 8.02-1build1 amd64

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

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  
  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  
  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1852265] Re: Nautilus hangs when right-click->properties is selected on file

[Sebastien Bacher]

> Could this bug be moved to rabbitvcs-nautilus?

reassigned

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

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

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

Title:
  Nautilus hangs when right-click->properties is selected on file

Status in rabbitvcs package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Ubuntu 18.04.3 LTS

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  nautilus:
Installed: 1:3.26.4-0~ubuntu18.04.4
Candidate: 1:3.26.4-0~ubuntu18.04.4
Version table:
   *** 1:3.26.4-0~ubuntu18.04.4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.26.3-0ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  3) What you expected to happen
  4) What happened instead

  A directory containing any amount of files (may be just few, may be
  hundreds of files) is opened. Some file is right-clicked and
  Properties is selected, after which Nautilus hangs immediately.

  It can be killed with "killall -9 nautilus" command, after which one
  must wait for short time before Nautilus can be started again.

  If it is started too soon, it will not start, it just prints text:
  "Failed to register: Timeout was reached"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Nov 12 15:58:19 2019
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'958x757+2151+138'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'RabbitVCS::age_column', 
'RabbitVCS::author_column', 'RabbitVCS::revision_column', 
'RabbitVCS::status_column']"
  InstallationDate: Installed on 2018-10-25 (383 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Marcin P]

Yes, the speakers behaves perfectly now. Thank you.

When auto-mute is enabled and I disconnect the headphones shouldn't the
global system volume be muted?

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

[Marcus Tomlinson]

@adam-yorba, when you said you reproduced this copying from Geany into
Geary what did you mean? That an image was pasted instead of text? Or
that nothing was pasted?

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

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

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

  There is some discussion of the problem here:

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

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

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

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

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1288786] Re: pkexec does not launch graphical authentication

[apt-ghetto]

No, pkexec per default does not start a graphical application for security 
reasons.
If you want to start a graphical application with pkexec, you need a policy in 
/usr/share/polkit-1/actions.

But, nowadays, it mostly isn't necessary to start a graphical
application with elevated privileges, because there are better
alternatives.

On *buntu 18.04, synaptic does have a policy => 
https://packages.ubuntu.com/bionic/amd64/synaptic/filelist
You can start it with synaptic-pkexec. The same command is used in 
/usr/share/applications/synaptic.desktop

If it does not work and you have a policy, please check, that the
PolicyKit Authentication Agent is running (lxsession-default-apps in
section autostart) and logout/login.

I don't understand, how "su -l $other_user" is related to this bug
report?

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

Title:
  pkexec does not launch graphical authentication

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Installed Trusty Tahr Lubuntu Beta1 version and added xubuntu desktop.  In 
buth desktops, I tried to launch synaptic to install some packages.  If I try 
to launch from menu, nothing seems to happen.  From a terminal, I ran
pkexec "/usr/sbin/synaptic"
   and saw that it asks for password in the terminal window, instead of popping 
up an authentication window like previous Ubuntu version did.  That was why I 
saw no authentication request when launching from menu..  I have a 
workaround)launching from Terminal window), but this should be fixed before 
release.

  ralph@minnie:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"
  ralph@minnie:~$ pkexec --version
  pkexec version 0.105

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1288786/+subscriptions

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

[Adam Dingle]

@marcustomlinson, when copying/pasting from Geany into Geary, I didn't
get an image.  I believe I got the wrong text.  But unfortunately I
don't remember precisely.

I have seen this bug zillions of times in LibreOffice Writer, typically
when copying in one window and pasting in another, and only a few times
in other apps.

Thanks for your research determining that this is related to X11.  That
gives us a possible workaround: log into a Wayland session instead.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

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

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

  There is some discussion of the problem here:

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

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

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

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

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions

[Jonathan Kamens]

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

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

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

Title:
  can't install gnome shell extensions

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

Bug description:
  Here's what I'm trying to do:

  1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/
  2. Click the toggle switch to install it.
  3. Use the extension after it is installed.

  Here's what should happen:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch goes from Off to On and the extension is added to my top 
bar.

  Here's what happens instead:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch stays in the Off permission, and the extension is not 
added to my top bar.

  Here's what I see in journalctl:

  Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user
  /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from
  available to installed is not OK

  I've also tried unzipping by hand into a subdirectory of
  ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and
  enabling the extension at extensions.gnome.org/local, but that doesn't
  work either. The toggle switch goes to On when I toggle it, but the
  extension isn't actually enabled and when I reload the page the switch
  is Off again.

  I've tried with https://extensions.gnome.org/extension/779/clipboard-
  indicator/ and https://extensions.gnome.org/extension/7/removable-
  drive-menu/ too. They won't install and activate either.

  *** I do not have this problem on a second Ubuntu 19.10 computer I
  use. *** I have no idea what is different between the two computers or
  how to troubleshoot further.

  I am using Xorg, not Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 14:16:34 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (55 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

[Sebastien Bacher]

** Tags added: regression-update

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions

[Sebastien Bacher]

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

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

Title:
  can't install gnome shell extensions

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

Bug description:
  Here's what I'm trying to do:

  1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/
  2. Click the toggle switch to install it.
  3. Use the extension after it is installed.

  Here's what should happen:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch goes from Off to On and the extension is added to my top 
bar.

  Here's what happens instead:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch stays in the Off permission, and the extension is not 
added to my top bar.

  Here's what I see in journalctl:

  Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user
  /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from
  available to installed is not OK

  I've also tried unzipping by hand into a subdirectory of
  ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and
  enabling the extension at extensions.gnome.org/local, but that doesn't
  work either. The toggle switch goes to On when I toggle it, but the
  extension isn't actually enabled and when I reload the page the switch
  is Off again.

  I've tried with https://extensions.gnome.org/extension/779/clipboard-
  indicator/ and https://extensions.gnome.org/extension/7/removable-
  drive-menu/ too. They won't install and activate either.

  *** I do not have this problem on a second Ubuntu 19.10 computer I
  use. *** I have no idea what is different between the two computers or
  how to troubleshoot further.

  I am using Xorg, not Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 14:16:34 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (55 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1843262] Re: tracker-miner-fs crashed with SIGABRT in raise()

[Sebastien Bacher]

** Changed in: tracker-miners (Ubuntu)
   Importance: Low => High

** Changed in: tracker-miners (Ubuntu)
   Status: Incomplete => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/tracker-miners/issues #86
   https://gitlab.gnome.org/GNOME/tracker-miners/issues/86

** Also affects: tracker via
   https://gitlab.gnome.org/GNOME/tracker-miners/issues/86
   Importance: Unknown
   Status: Unknown

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

Title:
  tracker-miner-fs crashed with SIGABRT in raise()

Status in Tracker:
  Unknown
Status in tracker-miners package in Ubuntu:
  Triaged

Bug description:
  after turn on pc

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: tracker-miner-fs 2.1.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 17:17:05 2019
  ExecutablePath: /usr/lib/tracker/tracker-miner-fs
  InstallationDate: Installed on 2019-07-14 (57 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701)
  ProcCmdline: /usr/lib/tracker/tracker-miner-fs
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: tracker-miners
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
  Title: tracker-miner-fs crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1852383] Re: system hangs on shutdown

[Sebastien Bacher]

** Package changed: gdm3 (Ubuntu) => systemd (Ubuntu)

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

Title:
  system hangs on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  On a Lenovo Yoga S940, the system always hangs on shutdown.
  The screen turns black and nothing happens anymore. 
  I have to keep pressed for several seconds the shutdown hardware button in 
order to actually turn it off.

  I attach the journalctl output from the shutdown which present very
  similar 'errors' from session to session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
  Uname: Linux 5.3.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 07:03:38 2019
  InstallationDate: Installed on 2019-10-09 (34 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1852474] [NEW] cups not printing if authentication required by server

[Thomas Schweikle]

Public bug reported:

cups does not print if servers require authenticated users to print. No
login-dialog is shown. Print jobs are on hold, waiting for
legitimization. But no legitimization dialog will be shown.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
Uname: Linux 5.3.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 13 19:23:18 2019
InstallationDate: Installed on 2019-09-09 (65 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat:
 device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: 
smb://srvmfg02-muc.bfs.de/drucker-muc
 device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/
Lsusb:
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', 
'/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied
 grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2019
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug eoan

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

Title:
  cups not printing if authentication required by server

Status in cups package in Ubuntu:
  New

Bug description:
  cups does not print if servers require authenticated users to print.
  No login-dialog is shown. Print jobs are on hold, waiting for
  legitimization. But no legitimization dialog will be shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
  Uname: Linux 5.3.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 13 19:23:18 2019
  InstallationDate: Installed on 2019-09-09 (65 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat:
   device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: 
smb://srvmfg02-muc.bfs.de/drucker-muc
   device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', 
'/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied
   grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: V

[Desktop-packages] [Bug 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue

[Thomas Schweikle]

Same for Ubuntu 19.10 with cups 2.2.12

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

Title:
  CUPS cannot print to Kerberos-authenticated SMB print queue

Status in cups package in Ubuntu:
  Confirmed
Status in Debian:
  Fix Released

Bug description:
  Binary package hint: cups

  That was investigated on maverick (cups 1.4.4) and natty (cups 1.4.6).

  CUPS in Ubuntu cannot authenticate using Kerberos to an SMB print
  queue, such as one in an Active Directory.  This is because the smb
  backend is being invoked as user lp, and this user cannot access the
  Kerberos credential cache of the user who submitted the job.  When
  trying to print, the job is held for authentication, and a dialog
  prompting for username/password is being shown.  On Windows (and
  possibly other OS), the user would not be prompted if he has a ticket
  in the Kerberos realm (ie, "logged on to the domain") he is trying to
  print to.

  The CUPS smb backend on Ubuntu is the smbspool binary provided by
  Samba.  When run as a user, it will pick the Kerberos credential cache
  by itself and authenticate seamlessly.  Otherwise, it will read the
  KRB5CCNAME environment variable and try to use that when possible.

  There is two possible solutions to that:

  - Invoke the smb backend as root and pass it the KRB5CCNAME
  environment variable pointing to the user's Kerberos credential cache.
  CUPS execute the backend as user lp if it is world-executable, which
  is currently the case on Ubuntu.  User lp do not have the permission
  to read  the user's credential cache, hence why the smb backend would
  need to be executed as root (by removing the world-executable bit).
  Also, CUPS does not currently set KRB5CCNAME before invoking the smb
  backend (see http://www.cups.org/str.php?L3847).

  - Execute smbspool as the user submitting the job.

  
  I presume we would have the same problem with other backend that would do 
Kerberos authentication, although I do not know of a specific one.  I have only 
tested and investigated with the smb backend.

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

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

[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

[baptiste]

Simpler than j127's solution is to download the last beta on
https://download.mozilla.org/?product=firefox-beta-latest-
ssl&os=linux64&lang=en-US, copy your profile into a new folder, then
launch the executable with `MOZ_ALLOW_DOWNGRADE=1
/home/baptiste/firefox/firefox -P`, create a profile and choose the
copied folder. All works smoothly and it takes 5mn.

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

Title:
  Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1

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

Bug description:
  After update from: 70.0+build2-0ubuntu0.16.04.1 to
  71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
  message that I can Refresh Firefox (crash) or Start in safe mode (also
  crash).

  Tech details:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04
  package name:   71.0~b5+build1-0ubuntu0.16.04.1

  Crash log details:
  AdapterDeviceID: 0x1616
  AdapterDriverVendor: mesa/i965
  AdapterDriverVersion: 18.0.5.0
  AdapterVendorID: 0x8086
  BuildID: 20191028161640
  ContentSandboxCapabilities: 119
  ContentSandboxCapable: 1
  ContentSandboxLevel: 4
  CrashTime: 1572373123
  DOMIPCEnabled: 1
  FramePoisonBase: 9223372036600930304
  FramePoisonSize: 4096
  InstallTime: 1572364967
  IsWayland: 0
  IsWaylandDRM: 0
  MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is 
invalid)
  Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP- 
  ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  ProductName: Firefox
  ReleaseChannel: beta
  SafeMode: 1
  SecondsSinceLastCrash: 816
  StartupCrash: 0
  StartupTime: 1572373025
  TelemetryEnvironment: 
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
 DRI Intel(R) HD Graphics 5500 (Broadwell GT2) 
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
  ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS 
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS 
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2 
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker 
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder 
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM 
Worker",7584:"QuotaManager 
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM 
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver 
#2",7633:"StreamTrans

[Desktop-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

[Joe Hohertz]

Did you ensure that the connection was set for "use only for resources
on the connection"? (I believe this may be ipv4.never-default=yes
setting in nmcli... and only bring it up because you do not mention it.)

I also think the negative DNS priority might be historical, no longer
needed. (I just noticed mine was set to 50, which I believe is default
for VPN connections now)

I should also note that if the never-default is set to "no"... I *will*
see the DNS server, however the routing is then incorrect as the VPN
concerned doesn't provide public routes.

So to be clear... never-default needs to be set to yes... DNS we expect
is from DHCP options sent from the VPN server, and the problem is that
you will see NO DNS servers for tun0 when you run the 'systemd-resolve
--status' command

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

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

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

[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Taylor Braun-Jones]

My guess is that rls-bb-notfixing means this is not getting fixed in
Bionic Beaver 18.04. Really hoping a fix can make it into the 20.04 LTS
release though.

I agree with Paul - systemd-resolve is not doing what it promises to do.
>From systemd.network(5):

Both "search" and "routing-only" domains are used for routing of DNS 
queries:
look-ups for host names ending in those domains (hence also single label 
names, if
any "search domains" are listed), are routed to the DNS servers configured 
for
this interface. The domain routing logic is particularly useful on 
multi-homed
hosts with DNS servers serving particular private DNS zones on each 
interface.

The "routing-only" domain "~."  (the tilde indicating definition of a 
routing
domain, the dot referring to the DNS root domain which is the implied 
suffix of
all valid DNS names) has special effect. It causes all DNS traffic which 
does not
match another configured domain routing entry to be routed to DNS servers
specified for this interface. This setting is useful to prefer a certain 
set of
DNS servers if a link on which they are connected is available.

This setting is read by systemd-resolved.service(8). "Search domains" 
correspond
to the domain and search entries in resolv.conf(5). Domain name routing has 
no
equivalent in the traditional glibc API, which has no concept of domain name
servers limited to a specific link.

One partial workaround is to remove `[!UNAVAIL=return]` after `resolve`
in /etc/nsswitch.conf:

hosts: files mdns4_minimal [NOTFOUND=return] resolve dns myhostname

That way a traditional DNS resolution is done after systemd-resolve
fails. This works for everything I've tested so far _except_ Google
Chrome.

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.

[Desktop-packages] [Bug 1849285] Re: [SRU] 3.34.2

[Iain Lane]

I did some testing in line with the bug's description with
3.34.2-1ubuntu1 and it seemed good to me.

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

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

Title:
  [SRU] 3.34.2

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  We missed the release with this one, but we ought to catch up with
  upstream.

  [ QA ]

  Uploaded under the GNOME SRU policy exception.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Please test the terminal keeps working, including changing themes,
  multiple tabs and whatever else you can think of.

  [ Regression potential ]

  The substantive change is around full screen terminals not remaining
  full screen sometimes. So check that this keeps working and nothing
  else breaks regarding full screening.

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

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

[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1851554

Title:
  can't install gnome shell extensions

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

Bug description:
  Here's what I'm trying to do:

  1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/
  2. Click the toggle switch to install it.
  3. Use the extension after it is installed.

  Here's what should happen:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch goes from Off to On and the extension is added to my top 
bar.

  Here's what happens instead:

  1. I am prompted for confirmation to install the extension.
  2. I click Install.
  3. The toggle switch stays in the Off permission, and the extension is not 
added to my top bar.

  Here's what I see in journalctl:

  Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user
  /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from
  available to installed is not OK

  I've also tried unzipping by hand into a subdirectory of
  ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and
  enabling the extension at extensions.gnome.org/local, but that doesn't
  work either. The toggle switch goes to On when I toggle it, but the
  extension isn't actually enabled and when I reload the page the switch
  is Off again.

  I've tried with https://extensions.gnome.org/extension/779/clipboard-
  indicator/ and https://extensions.gnome.org/extension/7/removable-
  drive-menu/ too. They won't install and activate either.

  *** I do not have this problem on a second Ubuntu 19.10 computer I
  use. *** I have no idea what is different between the two computers or
  how to troubleshoot further.

  I am using Xorg, not Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 14:16:34 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (55 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

[Michal Turecki]

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

I have a similar problem after upgrading Ubuntu to have Gnome 3.34 installed.
The only difference is that Alt+Tab works until certain point when windows 
freeze and only Ctrl + Alt + F3 -> init 3 -> login -> init 5 cycle restores the 
desktop.

CS:GO clearly loads with a lag, takes longer to load waiting on a loading image 
with shutter fade-in.
Main CS:GO screen sometimes loads but mouse cursor after moving is resetted to 
previous position after around 0.1 sec. Mouse press/keyboard is unresponsive. 
Suggestion about mutter being stuck in the message loop seems plausible.

I tried ppa above, mutter won't update so I forced it to install yet it
did not fix the problem. Steps taken:

sudo add-apt-repository ppa:kisak/lp-1848852
sudo apt install mutter=3.34.1-1ubuntu1~lp1848852

Do you have any suggestions what to do next?

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

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

Bug description:
  After upgrade to ubuntu 19.10, when I launch counter strike global offensive 
from steam the game is frozen. I can alt-tab and close the game. Tried in 
fluxbox window manager where the game works, changed fullscreen to windowed 
fullscreen in the options and tried on gnome again, now the desktop isn't 
responding after launching the game and I had to ctrl-alt-f3 to reboot my 
machine.
  Using a Radeon RX 580 video card.

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

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

[Desktop-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

[Kashif Khan]

sound card/driver :
Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
DeviceName: Onboard - Sound
Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS
Flags: bus master, fast devsel, latency 32, IRQ 143
Memory at a351 (64-bit, non-prefetchable) [size=16K]
Memory at a310 (64-bit, non-prefetchable) [size=1M]
Kernel driver in use: snd_hda_intel

I wasnt able to get any of the MP3 files to play via paplay

** Attachment added: "output of journalacl"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1852018/+attachment/5305258/+files/log.txt

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

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

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

[Desktop-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

[Sebastien Bacher]

You should be able to try to e.g
$ paplay /usr/share/sounds/freedesktop/stereo/dialog-information.oga

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

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

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

[Desktop-packages] [Bug 1847900] [NEW] Daily Deja Dup failure with "Failed with an unknown error."

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Daily backup fails with:
```
Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
  File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
  File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
return self.__run_synchronously(fn, params)
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
ret = fn(*params)
  File "/usr/bin/duplicity", line 453, in 
vol_num: put(tdp, dest_filename, vol_num),
  File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)
```

Ubuntu 18.04.3 LTS
deja-dup37.1-2fakesync1ubuntu0.1
duplicity   0.7.17-0ubuntu1.1

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: Fix Released

-- 
Daily Deja Dup failure with "Failed with an unknown error."
https://bugs.launchpad.net/bugs/1847900
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to deja-dup 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 1847900] Re: Daily Deja Dup failure with "Failed with an unknown error."

[Michael Terry]

This is fixed in 19.10 by using the python3 version of duplicity.

You can get the fix on 18.04  by using the snap version of Deja Dup:
snap install deja-dup --classic

** Project changed: deja-dup => deja-dup (Ubuntu)

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

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

Title:
  Daily Deja Dup failure with "Failed with an unknown error."

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Daily backup fails with:
  ```
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1511, in do_backup
  full_backup(col_stats)
File "/usr/bin/duplicity", line 572, in full_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)
  ```

  Ubuntu 18.04.3 LTS
  deja-dup  37.1-2fakesync1ubuntu0.1
  duplicity 0.7.17-0ubuntu1.1

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

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

[Desktop-packages] [Bug 1847196] Re: BackendException: PyDrive backend requires PyDrive installation

[Michael Terry]

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

** This bug has been marked a duplicate of bug 1852069
   Failed to backup to google drive on ubuntu 19.10

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

Title:
  BackendException: PyDrive backend requires PyDrive installation

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  I have deja-dup configured to do a back up to Google Drive. This
  worked until like a month or two ago, at which point it started to
  print

  BackendException: PyDrive backend requires PyDrive installation.  Please read 
the manpage for setup details.
  Exception: No module named 'pydrive'

  There does not seem to be a pydrive module in the archive; and I
  thought it is using GOA anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct  8 09:02:38 2019
  InstallationDate: Installed on 2018-03-14 (572 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to eoan on 2018-11-20 (321 days ago)

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

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

[Desktop-packages] [Bug 1810665] Re: Ubuntu 19.04 / DejaDup / can not Data return

[Michael Terry]

The missing dependency issue should be fixed in 19.10

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

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

Title:
  Ubuntu 19.04 / DejaDup / can not Data return

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Hello

  Can not Data return of my system.

  package missing

  duplicity
  python-gi

  Install this

  Start DejaDup, found not Files.

  Action from ubuntuusers DejaDup to 18.10
  Fond files, start return data,  Error!

  DejaDup is not in function.

  I can not more tests in 19.04, i muss have Data.

  Best Regards
  Marko

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

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

[Desktop-packages] [Bug 1831368] Re: Deja-dup asks to install software from un-trusted sources

[Michael Terry]

Should be fixed in 19.10 by hard depending on the packages.

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

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

Title:
  Deja-dup asks to install software from un-trusted sources

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  When setting up deja-dup to backup to Google drive, it says that
  dulicity & python-gi are not installed (this is expected). It gives
  the option to install these packages, but the system warns that they
  are from an untrusted source.

  Installing the same packages from terminal raises no such warnings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  2 12:28:52 2019
  InstallationDate: Installed on 2019-05-28 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive

[Michael Terry]

Alright, the switch to our own keys seems to have fixed this. I’ll close
the remaining tasks on this bug.

Ubuntu 19.10 uses the new key but has a separate issue with Google
Drive: bug 1852069

** Changed in: deja-dup (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: duplicity
   Status: Confirmed => Invalid

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

Title:
  Authentication error with google drive

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

Bug description:
  Hi,

  I'm having an issue using deja-dup to back up my laptop to my google
  drive.

  When backing only a small folder (eg: ~/Documents) every thing works fine.
  However when trying to backup my whole home folder (/home/myusername) I get 
an "Invalid credentials" error after 5-10 min.

  The back up seems to start normally and my destination folder starts
  filling with "duplicity-full...difftar.gz" files, but eventually I get
  the Invalid Credentials error.

  
  lsb_release -d
  Fedora release 27 (Twenty Seven)

  rpm -q deja-dup duplicity
  deja-dup-37.1-1.fc27.x86_64
  duplicity-0.7.16-1.fc27.x86_64

  deja-dup.log attached.
  I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if 
needed.

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

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

[Desktop-packages] [Bug 1766258] Re: Duplicity fails to install

[Michael Terry]

Should be fixed in 19.10

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

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

Title:
  Duplicity fails to install

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Ran into this error on 17.10 which is allegedly fixed on 18.04:
  https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1734499 (I
  think I did the original backup on either 17.04 or 17.10)

  I upgraded to 18.04 and now the problem is that when I put the USB
  stick in, Backups asks to install duplicity, and I click Install, but
  it doesn't install (the progress bar hangs and if I take the USB stick
  out and put it back in again it pops up the installation request
  again).

  After leaving it for many minutes, I get the error:

  Backup Failed
  client did not authorize action

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 23 14:24:17 2018
  InstallationDate: Installed on 2017-08-03 (262 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (1 days ago)

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

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

[Desktop-packages] [Bug 1787150] Re: After upgrading from 16.04 to 18.04 automatic backups aren't taken, because package "duplicity" is missing

[Michael Terry]

Should be fixed in 19.10 by having Deja Dup depend on duplicity again.

Or you could use the snap version.

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

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

Title:
  After upgrading from 16.04 to 18.04 automatic backups aren't taken,
  because package "duplicity" is missing

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  I upgraded a system from 16.04 to 18.04 and sure enough, backup
  software is broken again. For some reason duplicity is missing and
  automatic backups haven't been taken.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 15 12:53:08 2018
  InstallationDate: Installed on 2017-02-05 (555 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1233799] Re: "Skip Backup" didn't skip the backup.

[Michael Terry]

That UI option is gone now.

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

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

Title:
  "Skip Backup" didn't skip the backup.

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Turned on computer for first time in about a week.
  Backup started going, but I was using my internet connection and didn't want 
the backup to go.
  Right click icon in classic gnome shell and selected "Skip Backup".

  Within 10 minutes, it was trying to prepare another backup... selected
  skip again and reported this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50
  Uname: Linux 3.2.0-53-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  CheckboxSubmission: 880f1cef728a67d1a58407cc143447d4
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Tue Oct  1 14:36:46 2013
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-06-15 (473 days ago)

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

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

[Desktop-packages] [Bug 1335605] Re: Click location displaced upwards by about 1cm

[Michael Terry]

I’m going to assume this is fixed on recent releases? At the least,
compiz isn’t used by default anymore.

If you still see this, please reopen.

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

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

Title:
  Click location displaced upwards by about 1cm

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  When backups start, and Place Windows in compiz is set to "Maximise",
  clicking controls on the backup window doesn't work. However, if you
  click about 1cm above them (e.g. the details arrow, or buttons, or
  option buttons if running first time) then they work. It gives the
  appearance that the window is not responding until you notice
  accidentally click one control and the one below flinches.

  Restoring to normal then maximising the window solves the problem.
  Also, after running ubuntu-bug and returning to the window the problem
  goes away. However, this has happened reliably many times and I have
  not had this particular problem in any other application.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 29 12:17:30 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2013-05-07 (417 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (61 days ago)

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

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

[Desktop-packages] [Bug 1712757] Re: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_m

[Michael Terry]

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

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

Title:
  /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-
  
monitor:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_value:g_settings_get_boolean:deja_dup_migrate_settings

Status in deja-dup package in Ubuntu:
  Fix Released

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

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

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

[Desktop-packages] [Bug 1749950] Re: deja-dup-monitor (11) in WTF::HashTable, WTF::KeyValuePairKeyExtractor

[Michael Terry]

Closing this, as Deja Dup no longer links with WebKit

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

** Changed in: webkit2gtk (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  deja-dup-monitor (11) in WTF::HashTable,
  WTF::KeyValuePairKeyExtractor >, WTF::PtrHash,
  WTF::HashMap, WTF::HashTraits,
  WTF::HashTraits
  >::KeyValuePairTraits, WTF::HashTraits >::remove

Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Fix Released

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

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

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

[Desktop-packages] [Bug 1450429] Re: Backups configuration duplicated folders

[Michael Terry]

This was fixed in 39.1 (and Ubuntu 19.10)

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

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

Title:
  Backups configuration duplicated folders

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 15.04
  unity-control-center 15.04.0+15.04.20150410-0ubuntu1

  Just a small UI bug.
  I'm using the Backups UI from Settings/System to backup files to a network 
share.
  I've removed the ~/Downloads folder from the 'Folders to ignore' section.
  When I open the Backups UI now for the first time, the folders in 'Folders to 
save' and 'Folders to ignore' are correct.
  But when I go back to All Settings and then open Backups again, each folder 
in these sections will be shown twice.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 13:03:05 2015
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-02-11 (77 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (0 days ago)
  usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5

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

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

[Desktop-packages] [Bug 940782] Re: deja-dup crashed with SIGSEGV in g_file_make_directory_with_parents()

[Michael Terry]

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

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

Title:
  deja-dup crashed with SIGSEGV in g_file_make_directory_with_parents()

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  deja-dup:
Installed: 21.90-0ubuntu1
Candidate: 21.90-0ubuntu1
Version table:
   *** 21.90-0ubuntu1 0
  500 http://in.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  Expected Outcome: I had logged into one user account X and then switched to 
another user account Y. Then I plugged in my external backup harddisk.
  Deja Dup should not start the encrypted backup in user account X as it was 
not the currently active account. User account Y is the currently active 
account, so Deja-Dup should finish the encrypted backup successfully in user 
account Y.

  Actual Outcome: Deja-Dup finished the encrypted backup successfully in
  user account Y. But when I switched back to user account X, this crash
  report was generated and Deja-Dup showed an error message. I think the
  error message said "Permission Denied".

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 21.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  CheckboxSubmission: da29d507ee0e5fa36c9fd9e32f64b95a
  CheckboxSystem: 174dd9663cefed283ef72538c1136ee0
  CrashCounter: 1
  Date: Sat Feb 25 10:19:01 2012
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111215)
  ProcCmdline: deja-dup --backup --auto
  SegvAnalysis:
   Segfault happened at: 0xaa3b9e : 
cmpl   $0x1,0x4(%eax)
   PC (0x00aa3b9e) ok
   source "$0x1" ok
   destination "0x4(%eax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   g_file_make_directory_with_parents () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: deja-dup crashed with SIGSEGV in g_file_make_directory_with_parents()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1737535] Re: Falha ao executar processo filho "duplicity" (Arquivo ou diretório não encontrado)

[Michael Terry]

Should be fixed in 19.10 or by using the snap.

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

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

Title:
  Falha ao executar processo filho "duplicity" (Arquivo ou diretório não
  encontrado)

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Não Consigo executar o programa! Aparece a seguinte mensagem: Falha ao
  executar processo filho "duplicity" (Arquivo ou diretório não
  encontrado)

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

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

[Desktop-packages] [Bug 1844799] Re: Use new snap banner format

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Eoan)
   Status: Triaged => Fix Committed

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

Title:
  Use new snap banner format

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  Snaps now have a native banner format. The old screenshot method is no longer 
supported and will result in banners no longer displaying.

  [Test Case]
  1. Open GNOME Software
  2. Check banner shown in in the new format

  [Regression Potential]
  Some small risk of breaking banner code.

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

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

[Desktop-packages] [Bug 1816396] Re: Starting snap from the after-install notification fails

[Robert Ancell]

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Eoan)
   Status: Triaged => Fix Committed

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

Title:
  Starting snap from the after-install notification fails

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  The launch button on the notification shown after snaps are installed doesn't 
 work.

  [Test Case]
  1. Open GNOME Software
  2. Select a snap that is not installed
  3. Install that snap
  4. Switch focus to another application (i.e. so GNOME Software doesn't have 
focus)

  Expected result:
  A notification is shown saying the app is installed with a button that 
launches it.

  Observed result:
  A notification is shown but the launch button give an error like "no such 
desktop file: io.snapcraft.vlc-"

  [Regression Potential]
  TBD

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

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

[Desktop-packages] [Bug 1844799] Re: Use new snap banner format

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  Use new snap banner format

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Disco:
  Won't Fix
Status in gnome-software source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  Snaps now have a native banner format. The old screenshot method is no longer 
supported and will result in banners no longer displaying.

  [Test Case]
  1. Open GNOME Software
  2. Check banner shown in in the new format

  [Regression Potential]
  Some small risk of breaking banner code.

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

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

[Desktop-packages] [Bug 1740238] Re: 'operation already pending' error when drive gets available, manual start required

[Michael Terry]

Has this been seen on 18.04+?

** Changed in: deja-dup (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  'operation already pending' error when drive gets available, manual
  start required

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I have scheduled daily backups for a laptop to be kept forever on a
  drive that is often disconnected from the laptop. I connect it when I
  can; when I connect it, it gives a 'Backups failed' error stating that
  an operation is already pending. I must then open Backups from the
  launcher for this pending backup to begin. Please fix these two bugs
  (or single bug causing two problems?) so that the backup starts
  without telling me an operation (presumably the backup that starts) is
  already pending, and without me having to open Backups for it to
  start.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 27 17:51:10 2017
  InstallationDate: Installed on 2017-11-20 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1724638] Re: deja-dup-monitor crashes with an out-of-memory issue

[Michael Terry]

Closing this because we took out the memory cap.

** Changed in: deja-dup
   Status: Confirmed => Fix Released

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

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

Title:
  deja-dup-monitor crashes with an out-of-memory issue

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

Bug description:
  In the 36.x series, I added some code that will prevent deja-dup-
  monitor's memory usage from growing out of bounds (see original bug
  1302416 that I have still been unable to reproduce).

  This causes crashes occasionally when the process is prevented from
  allocating more memory.  This will be the master bug for such crashes
  and the dups will have the specific crash details.

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

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

[Desktop-packages] [Bug 942743] Re: add an update-manager like notification

[Michael Terry]

We use a notification for that these days

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

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

Title:
  add an update-manager like notification

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Every time I turn my ubuntu box on and there are new updates
  available, update-manager opens itself as a unity launcher waiting for
  an action. I wish deja-dup had the same behavior for a pending
  scheduled backup, especially when the backup drive is not available at
  the moment.

  xand@notebook:~$ lsb_release -d
  Description:  Ubuntu 11.10
  xand@notebook:~$ dpkg-query -W deja-dup duplicity
  deja-dup  20.1-0ubuntu0.2
  duplicity 0.6.15-0ubuntu2

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

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

[Desktop-packages] [Bug 1027503] Re: Deja-Dup failed to restore full backup

[Michael Terry]

I don’t think there’s enough information here for me to guess what our
2012 code was trying to do. I’m going to close this, but please reopen
if you still see it.

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

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

Title:
  Deja-Dup failed to restore full backup

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  GIven how Deja-Dup failed to backup data to a Samba share
  (https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1026828), I
  had it backup into a local folder, then copied the folder onto Samba
  and verified that the same amount of files were there. Then I had to
  wipe my home folder (was undoing ecryptfs slowness), and I copied the
  files off Samba onto the computer again. I asked Deja-Dup to restore
  the files... and it failed with: "Could not restore
  ‘/home/svorai/’: File not found in backup".

  Now I don't know how to get my data back.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic i686
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  Date: Sun Jul 22 07:03:09 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-04-27 (85 days ago)

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

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

[Desktop-packages] [Bug 1042143] Re: auto shutdown after sucessful backup does not work

[Michael Terry]

The brainstorm link is dead now and we don’t have any code left for
inhibiting a shutdown (Deja Dup will just resume next time). I’m going
to close, but please open a new bug if you’re still experiencing a bug
around this.

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

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

Title:
  auto shutdown after sucessful backup does not work

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  I had submitted a idea in brainstorm
  http://brainstorm.ubuntu.com/idea/30032/ and it turned out to be a
  bug.

  I tried out what was written in the comment but it did not work out.

  The backup progress bar stopped and shutdown dialog window turned
  transparent for about 10-15 seconds and my PC began to shutdown. No
  pop ups, alert message box came up.

  I started the PC again, opened deja dub backup. The Backup Overview
  window read 'Most recent backup Yesterday'.

  lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

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

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

[Desktop-packages] [Bug 1019293] Re: "gpg: can't handle text lines longer than 19995 characters" error when backing up

[Michael Terry]

Has anyone seen this in recent years?

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

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

Title:
  "gpg: can't handle text lines longer than 19995 characters" error when
  backing up

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  When I run deja-dup, and it encounters some data* it asks for the
  password to be reentered, and when you do that, it tries again, and
  gets in the same loop, over and over until you cancel. Nothing ends up
  being backed up.

  * e.g. my gpg public keyring, but when I exclude .gnupg, it has what
  may be the same problem on something else too, so I think that's
  coincidence.

  The last part of the log is at the bottom of this, and I'll attach the
  final 1000 lines. I don't think this is a duplicate of bug #883742, as
  the source of the error is quite different.

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf') 
/home/robin/.gnupg/gpg.conf reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf'
  DUPLICITY: . A home/robin/.gnupg/gpg.conf

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf~

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf~') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf~') 
/home/robin/.gnupg/gpg.conf~ reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf~'
  DUPLICITY: . A home/robin/.gnupg/gpg.conf~

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/pubring.gpg

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'pubring.gpg') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'pubring.gpg') 
/home/robin/.gnupg/pubring.gpg reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/pubring.gpg'
  DUPLICITY: . A home/robin/.gnupg/pubring.gpg

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-_XHa0A-tempdir/mkstemp-DS0LuL-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-_XHa0A-tempdir/mktemp-w2gx_c-2

  DUPLICITY: INFO 1
  DUPLICITY: . GPG error detail: Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1403, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1396, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1366, in main
  DUPLICITY: . full_backup(col_stats)
  DUPLICITY: .   File "/usr/bin/duplicity", line 500, in full_backup
  DUPLICITY: . globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity", line 378, in write_multivol
  DUPLICITY: . globals.gpg_profile, globals.volsize)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
332, in GPGWriteFile
  DUPLICITY: . file.close()
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
221, in close
  DUPLICITY: . self.gpg_failed()
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
206, in gpg_failed
  DUPLICITY: . raise GPGError, msg
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: . 
  DUPLICITY: . 

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jun 29 14:04:01 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-05-08 (52 days ago)

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

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

[Desktop-packages] [Bug 1702015] Re: package deja-dup 34.2-0ubuntu1.1 failed to install/upgrade: package deja-dup is not ready for configuration cannot configure (current status 'half-installed')

[Michael Terry]

This looks like some issue with the old deja-dup-backend-gvfs package.
That’s no longer a separate package.

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

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

Title:
  package deja-dup 34.2-0ubuntu1.1 failed to install/upgrade: package
  deja-dup is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Zamrza notebook

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70
  Uname: Linux 4.4.0-82-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.7
  Architecture: amd64
  Date: Wed Jun 28 01:03:40 2017
  DuplicateSignature:
   package:deja-dup:34.2-0ubuntu1.1
   Setting up libc6-dev:amd64 (2.23-0ubuntu9) ...
   dpkg: error processing package deja-dup (--configure):
package deja-dup is not ready for configuration
  ErrorMessage: package deja-dup is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-02-04 (515 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: deja-dup
  Title: package deja-dup 34.2-0ubuntu1.1 failed to install/upgrade: package 
deja-dup is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-05-14 (414 days ago)

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

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

[Desktop-packages] [Bug 1650723] Re: package deja-dup 34.2-0ubuntu1 failed to install/upgrade: unable to move aside './usr/lib/x86_64-linux-gnu/deja-dup/libwidgets.so' to install new version: Structur

[Michael Terry]

The error “ install new version: Structure needs cleaning” seems like
some ext4 error, from a quick internet search. Maybe from copying data
from inside Windows? I’m going to close as not a Deja Dup bug.

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

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

Title:
  package deja-dup 34.2-0ubuntu1 failed to install/upgrade: unable to
  move aside './usr/lib/x86_64-linux-gnu/deja-dup/libwidgets.so' to
  install new version: Structure needs cleaning

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  Fail the packager installation.

  This was a upgrade installation.

  Ubuntu 16.04.1 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Dec 17 09:41:28 2016
  DuplicateSignature:
   package:deja-dup:34.2-0ubuntu1
   Unpacking deja-dup (34.2-0ubuntu1.1) over (34.2-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/deja-dup_34.2-0ubuntu1.1_amd64.deb (--unpack):
unable to move aside './usr/lib/x86_64-linux-gnu/deja-dup/libwidgets.so' to 
install new version: Structure needs cleaning
  ErrorMessage: unable to move aside 
'./usr/lib/x86_64-linux-gnu/deja-dup/libwidgets.so' to install new version: 
Structure needs cleaning
  InstallationDate: Installed on 2016-07-10 (159 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: deja-dup
  Title: package deja-dup 34.2-0ubuntu1 failed to install/upgrade: unable to 
move aside './usr/lib/x86_64-linux-gnu/deja-dup/libwidgets.so' to install new 
version: Structure needs cleaning
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (133 days ago)

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

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

[Desktop-packages] [Bug 1370363] Re: deja-dup fails to backup using SFTP/SSH if Gnome Keyring is not available

[Michael Terry]

For our own passphrases, etc, we just use libsecrets, which is not tied
to a specific desktop.

But for network server access, we do rely on gvfs, which is not likely
to change. And that might have some wonkiness in other desktop envs
(though hopefully that’s better in 2019 than in past, assuming that it
also uses libsecret now).

I’ll close this, but please reopen if you think there’s something more
Deja Dup should be doing itself here.

** Changed in: deja-dup
   Status: Confirmed => Fix Released

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

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

Title:
  deja-dup fails to backup using SFTP/SSH if Gnome Keyring is not
  available

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

Bug description:
  I have had a working deja-dup setup under Ubuntu 12.04LTS. I upgraded
  to Ubuntu 14.04LTS. Now deja-dup no-longer works, the window states
  "Permission denied" (the German translation), also if I run
  "DEJA_DUP_DEBUG=1 deja-dup --backup" there is no output at all. (I am
  currently trying running it from a KDE desktop.)

  I can still successfully run "duplicity collection-status" + the URL I
  find in org.gnome.deja-dup's file backend configuration and get a
  reasonable output, so it does not appear to be an ssh-related issue.

  I moved .cache/deja-dup out of the way, for no improvement.

  How do we go about debugging this?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Sep 17 08:51:40 2014
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (18 days ago)

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

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

[Desktop-packages] [Bug 1847247] Re: External dictionaries are not loaded

[Mathew Hodson]

** Bug watch removed: Mozilla Bugzilla #1457321
   https://bugzilla.mozilla.org/show_bug.cgi?id=1457321

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

Title:
  External dictionaries are not loaded

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Committed
Status in thunderbird source package in Eoan:
  Fix Committed

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

  NOTE TO SRU TEAM: Please do not release this package without
  consulting first. This is a security update pushed via -proposed to
  get a bit more testing. Will be released via it's own processes.

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

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

[Desktop-packages] [Bug 1841709] Re: [regression] gobject.h:767: syntax error

[Mathew Hodson]

** Tags removed: fixed-in-3.34.2 fixed-upstream regression
** Tags added: patch-accepted-upstream regression-release

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

Title:
  [regression] gobject.h:767: syntax error

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

Bug description:
  [ Impact ]

  Building mutter triggers various non-fatal syntax errors:

  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected '/' in 
'  do { if g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at '/'
  /usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected ')', 
expecting identifier or '(' in '  do { if 
g_type_check_instance_is_fundamentally_a ((GTypeInstance*) 
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message 
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*) 
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while 
(0);' at ')'
  /usr/include/glib-2.0/gobject/gobject.h:770: syntax error, unexpected ')', 
expecting identifier or '(' in '# 770 
"/usr/include/glib-2.0/gobject/gobject.h"' at ')'

  Looks like the offending release glib2.0 (2.61.2-2) is from last
  night's updates.

  [ Test case ]

  - Just build mutter and ensure that no such errors are triggered

  [ Regression potential ]

  None, once it builds we're all happy :)

  ---

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: libglib2.0-dev 2.61.2-2
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Aug 28 11:30:06 2019
  InstallationDate: Installed on 2019-05-02 (117 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 
(20190501)SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]

[Mathew Hodson]

** Bug watch removed: gitlab.gnome.org/GNOME/mutter/issues #826
   https://gitlab.gnome.org/GNOME/mutter/issues/826

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in mutter source package in Eoan:
  Fix Committed
Status in gnome-shell source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  [ Impact ]

  Gnome shell fills the journal with errors as soon as a view is closed
  from the overview

  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1

  [ Test case ]

  1) Open terminal and watch journalct -f /usr/bin/gnome-shell
  2) Open a window (i.e Files)
  3) Close Files in the activities overview
  4) gnome-shell spanws errors in the journal.

  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

  [ Regression potential ]

  Key focus might not work properly in some shell elements, in
  particular the focus be owned by multiple actors or by none of them.

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

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

[Desktop-packages] [Bug 1852540] Re: changed gmail password now cannot connect imap with thunderbird 60.9.0

[Jeremy Winick]

This problem is really unexpected and has caused me a lot of grief. When
I got a message from a identity protection service that my gmail account
MAY have been compromised, I changed my gmail password. Then as soon as
I tried to get mail via thunderbird, I got imap authentication errors.

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

Title:
  changed gmail password now cannot connect imap with thunderbird 60.9.0

Status in thunderbird package in Ubuntu:
  New

Bug description:
  this is a KNOWN problem as I have seen similar question on the
  Internet and it appears that something screwed up with Thunderbird in
  recent updates with their OAuth2  authentication method code. I am
  running Thunderbird 60.9.0 which appears to be the latest available
  for Ubuntu (Kubuntu) 16.04 LTS

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

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

[Desktop-packages] [Bug 1852540] [NEW] changed gmail password now cannot connect imap with thunderbird 60.9.0

[Jeremy Winick]

Public bug reported:

this is a KNOWN problem as I have seen similar question on the Internet
and it appears that something screwed up with Thunderbird in recent
updates with their OAuth2  authentication method code. I am running
Thunderbird 60.9.0 which appears to be the latest available for Ubuntu
(Kubuntu) 16.04 LTS

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

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

Title:
  changed gmail password now cannot connect imap with thunderbird 60.9.0

Status in thunderbird package in Ubuntu:
  New

Bug description:
  this is a KNOWN problem as I have seen similar question on the
  Internet and it appears that something screwed up with Thunderbird in
  recent updates with their OAuth2  authentication method code. I am
  running Thunderbird 60.9.0 which appears to be the latest available
  for Ubuntu (Kubuntu) 16.04 LTS

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

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