[Desktop-packages] [Bug 1880099] Re: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ub

2020-09-11 Thread Rocko
I think this affects me, at least I no longer get dash-to-dock or
ubuntu-dock now that groovy has updated to 3.37.

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

Title:
  ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR:
  Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-
  changed' on object 'Gjs_ubuntu-
  dock_ubuntu_com_dash_DashToDock_MyDashActor'

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

Bug description:
  ubuntu-dock no longer loads under gnome-shell 3.37:

  gnome-shell:3102): Gjs-WARNING **: 15:35:59.052: JS ERROR: Extension 
ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 
'Gjs_ubuntu-dock_ubuntu_com_dash_DashToDock_MyDashActor'
  
_init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:353:30

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

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


[Desktop-packages] [Bug 1880099] Re: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ub

2020-09-11 Thread Rocko
However, the gnome-3-38 branch in dash-to-dock does work.

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

Title:
  ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR:
  Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-
  changed' on object 'Gjs_ubuntu-
  dock_ubuntu_com_dash_DashToDock_MyDashActor'

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

Bug description:
  ubuntu-dock no longer loads under gnome-shell 3.37:

  gnome-shell:3102): Gjs-WARNING **: 15:35:59.052: JS ERROR: Extension 
ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 
'Gjs_ubuntu-dock_ubuntu_com_dash_DashToDock_MyDashActor'
  
_init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:353:30

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

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


[Desktop-packages] [Bug 1880099] Re: ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR: Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 'Gjs_ubuntu-dock_ub

2020-09-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ubuntu-dock no longer loads under gnome-shell 3.37: JS ERROR:
  Extension ubuntu-d...@ubuntu.com: Error: No signal 'allocation-
  changed' on object 'Gjs_ubuntu-
  dock_ubuntu_com_dash_DashToDock_MyDashActor'

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

Bug description:
  ubuntu-dock no longer loads under gnome-shell 3.37:

  gnome-shell:3102): Gjs-WARNING **: 15:35:59.052: JS ERROR: Extension 
ubuntu-d...@ubuntu.com: Error: No signal 'allocation-changed' on object 
'Gjs_ubuntu-dock_ubuntu_com_dash_DashToDock_MyDashActor'
  
_init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:353:30

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

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


[Desktop-packages] [Bug 1887150] Re: Fractional Scaling turns screen sideways

2020-09-11 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Fractional Scaling turns screen sideways

Status in mutter package in Ubuntu:
  Expired

Bug description:
  I right-click on desktop, click Display Settings, and find the Fractional 
Scaling option.
  When I enable the option my screen rotates 90 degrees. It's as if the display 
thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop).
  Can attach screenshots if possible.

  I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get
  update and sudo apt-get upgrade for the first time literally minutes
  ago. Nothing else was installed except for Grub Customizer and

  EDIT: Turns out I can't attach three screenshots. I can only attach
  one. I attached the final screenshot. I took screenshots of the
  original rotation, then before I selected the Fractional Scaling
  option, then what happened after. But I can only attach one of them.
  Please allow us to attach more than one screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 06:34:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) 
[1043:19d1]
  InstallationDate: Installed on 2020-07-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP412FA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=d20ac799-f93e-4aea-9632-495aa9132b04 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP412FA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP412FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412FA.302:bd05/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP412FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1887189] Re: package chromium-browser (not installed) failed to install/upgrade: subproces van het nieuwe pakket chromium-browser het script pre-installation gaf de foutwaarde

2020-09-11 Thread Launchpad Bug Tracker
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  subproces van het nieuwe pakket chromium-browser het script pre-
  installation gaf de foutwaarde 1 terug

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Ubtunu 20.04
  Opened Ubuntu Software while Apt was installing application in Terminal. 
Process seemed to crash but package seems to work.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 11 02:13:36 2020
  ErrorMessage: subproces van het nieuwe pakket chromium-browser het script 
pre-installation gaf de foutwaarde 1 terug
  InstallationDate: Installed on 2020-07-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
subproces van het nieuwe pakket chromium-browser het script pre-installation 
gaf de foutwaarde 1 terug
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1893484] Re: Google Chrome 85.0.4183.83 crahses with SIGSEGV

2020-09-11 Thread David Williams
After reading
https://support.google.com/chrome/thread/67845533?hl=en
I tried, on a whim, 
 chromium-browser --disable-gpu
and all works fine. 

I do not know what that means, but thought I'd post it here for 'data'. 
Perhaps it will help someone understand where to look for debugging, or, even, 
where the bug belongs. 

Thanks,

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

Title:
  Google Chrome 85.0.4183.83 crahses with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After an Update, the new version Google Chrome 85.0.4183.83  crashes
  with SIGSEGV.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  google-chrome-stable   85.0.4183.83-1 
  amd64The web browser from Google

  3) What you expected to happen
  Load the initial page or load my themes and configurations

  4) What happened instead
  It show the initial page, ask for Restore pages? when clicked it freezes for 
a moment and then a crash with:
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
  +++ killed by SIGSEGV (core dumped) +++

  
  Previous version was working fine.

  I de-installed, removed all configurations and themes and tried again.
  Same issue.

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

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


[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

2020-09-11 Thread Bug Watch Updater
** Changed in: wpa (Debian)
   Status: New => Fix Released

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

Title:
  Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Fix Released
Status in wpa package in Debian:
  Fix Released

Bug description:
  Some wifi adapters kept asking for a password when MAC address
  randomization was enabled.

  I reported this to Realtek, and they gave me a patch for
  wpa_supplicant, which fixes the issue.

  I asked Realtek to report this upstream to wpasupplicant, and they
  did, the commit is:
  http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563

  It would be very nice to cherrypick that for Focal.

  I uploaded it as a merge request below, and I tested that it fixes the issue 
with adapters based on the following chipsets:
  ath9k, rtl8812au, rtl88x2bu and rtl8821cu

  To reproduce this:

  Ubuntu's network-manager defaults to "MAC randomization disabled", I think as 
a workaround to this specific issue. This is defined in two places:
  - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf
  - Some specific drivers in 
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.

  With these, the problem happens in around 10% of the cases.
  To be able to reproduce it in 100% of the cases, it's best to remove these 
Ubuntu workarounds. So:
  - Set "wifi.scan-rand-mac-address=yes" in 
/etc/NetworkManager/NetworkManager.conf
  - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.
  - systemctl stop network-manager
  - killall wpa_supplicant
  - systemctl start network-manager

  Then insert a USB wifi adapter that results in a big name with 15
  characters like wlx74ee2ae2436a and try to connect to a wifi network.
  It will keep asking for a password.

  Then apply the patch, run the 3 commands above to restart network-
  manager, and verify that it can now connect properly.

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

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


[Desktop-packages] [Bug 1895349] [NEW] Sync libgweather 3.36.1-1 (main) from Debian unstable (main)

2020-09-11 Thread Amr Ibrahim
Public bug reported:

Please sync libgweather 3.36.1-1 (main) from Debian unstable (main)

It's a bug-fix release.

Changelog entries since current groovy version 3.36.0-1:

libgweather (3.36.1-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions. (Closes: #968909)

 -- Simon McVittie   Fri, 28 Aug 2020 23:36:23 +0100

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

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

Title:
  Sync libgweather 3.36.1-1 (main) from Debian unstable (main)

Status in libgweather package in Ubuntu:
  New

Bug description:
  Please sync libgweather 3.36.1-1 (main) from Debian unstable (main)

  It's a bug-fix release.

  Changelog entries since current groovy version 3.36.0-1:

  libgweather (3.36.1-1) unstable; urgency=medium

* Team upload
* New upstream release
  - This version works around the unavailability of the NOAA weather
services by using very short-term forecasts as current weather
conditions. (Closes: #968909)

   -- Simon McVittie   Fri, 28 Aug 2020 23:36:23 +0100

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

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


[Desktop-packages] [Bug 1895339] [NEW] display has stopped autorotating once logged-in

2020-09-11 Thread crysman
Public bug reported:

My modern Spin 5 (SP513-54N) is able to flip display into both "tent"
mode and/or "tablet" mode (almost 360°) and it used to flip OS screen
automatically, too.

Recently, the automatic rotation works only at login screen (before I
log in), once logged-in, flipping display keeps screen unrotated :(

What might be the cause?

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 11 20:18:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:8a5a] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:141f]
InstallationDate: Installed on 2020-06-19 (83 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=415eed75-e8aa-4b5a-a49d-51f5b103641e ro quiet splash i8042.nopnp=1 
pci=nocrs vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.05
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.05
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku: 
dmi.product.version: V1.05
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1895339

Title:
  display has stopped autorotating once logged-in

Status in xorg package in Ubuntu:
  New

Bug description:
  My modern Spin 5 (SP513-54N) is able to flip display into both "tent"
  mode and/or "tablet" mode (almost 360°) and it used to flip OS screen
  automatically, too.

  Recently, the automatic rotation works only at login screen (before I
  log in), once logged-in, flipping display keeps screen unrotated :(

  What might be the cause?

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 20:18:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:8a5a] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:141f]
  InstallationDate: Installed on 2020-06-19 (83 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=415eed75-e8aa-4b5a-a49d-51f5b103641e ro quiet splash i8042.nopnp=1 
pci=nocrs vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Desktop-packages] [Bug 1895339] Re: display has stopped autorotating once logged-in

2020-09-11 Thread crysman
Ah, my fault I am sorry, I've just found out there is a "Lock Screen
Rotation" button in notification area which has been enabled (although
accidentally). Please close this issue, thanks and sorry.

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

Title:
  display has stopped autorotating once logged-in

Status in xorg package in Ubuntu:
  New

Bug description:
  My modern Spin 5 (SP513-54N) is able to flip display into both "tent"
  mode and/or "tablet" mode (almost 360°) and it used to flip OS screen
  automatically, too.

  Recently, the automatic rotation works only at login screen (before I
  log in), once logged-in, flipping display keeps screen unrotated :(

  What might be the cause?

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 20:18:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:8a5a] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:141f]
  InstallationDate: Installed on 2020-06-19 (83 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=415eed75-e8aa-4b5a-a49d-51f5b103641e ro quiet splash i8042.nopnp=1 
pci=nocrs vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

2020-09-11 Thread Gilbertf
kern.log

** Attachment added: "kern.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894881/+attachment/5409903/+files/kern.log.gz

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

2020-09-11 Thread Gilbertf
syslog shows :

Sep 11 20:03:43 orion kernel: [  104.062316] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20570500
Sep 11 20:03:44 orion kernel: [  105.065317] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20670500
Sep 11 20:03:45 orion kernel: [  106.072545] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20770500
Sep 11 20:03:46 orion kernel: [  107.075711] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20870500
Sep 11 20:03:47 orion kernel: [  108.078909] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
Sep 11 20:03:48 orion kernel: [  109.091307] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
Sep 11 20:03:49 orion kernel: [  110.099662] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
Sep 11 20:03:50 orion kernel: [  111.107911] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
Sep 11 20:03:52 orion kernel: [  112.144229] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x202f8100
Sep 11 20:03:53 orion kernel: [  113.152440] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x202f8100
Sep 11 20:03:54 orion kernel: [  114.160509] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20170500
Sep 11 20:03:55 orion kernel: [  115.168750] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20370500
Sep 11 20:03:56 orion kernel: [  116.176862] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470500
Sep 11 20:03:57 orion kernel: [  117.188948] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20570500
Sep 11 20:03:58 orion kernel: [  118.192973] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20670500
Sep 11 20:03:59 orion kernel: [  119.205012] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20770500
Sep 11 20:04:00 orion kernel: [  120.216980] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20870500
Sep 11 20:04:01 orion kernel: [  121.228946] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
Sep 11 20:04:02 orion kernel: [  122.240854] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500


--

kern.log shows :

Sep 11 20:03:34 orion kernel: [   94.967128] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
Sep 11 20:03:35 orion kernel: [   95.977126] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
Sep 11 20:03:36 orion kernel: [   96.979389] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
Sep 11 20:03:37 orion kernel: [   97.985740] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
Sep 11 20:03:38 orion kernel: [   99.020209] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x202f8100
Sep 11 20:03:39 orion kernel: [  100.030810] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x202f8100
Sep 11 20:03:40 orion kernel: [  101.037589] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20170500
Sep 11 20:03:41 orion kernel: [  102.044399] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20370500
Sep 11 20:03:42 orion kernel: [  103.055305] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470500
Sep 11 20:03:43 orion kernel: [  104.062316] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20570500
Sep 11 20:03:44 orion kernel: [  105.065317] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20670500
Sep 11 20:03:45 orion kernel: [  106.072545] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20770500
Sep 11 20:03:46 orion kernel: [  107.075711] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20870500
Sep 11 20:03:47 orion kernel: [  108.078909] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
Sep 11 20:03:48 orion kernel: [  109.091307] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
Sep 11 20:03:49 orion kernel: [  110.099662] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
Sep 11 20:03:50 orion kernel: [  111.107911] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
Sep 11 20:03:52 orion kernel: [  112.144229] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x202f8100
Sep 

[Desktop-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

2020-09-11 Thread Gilbertf
syslog

** Attachment added: "syslog.gz"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894881/+attachment/5409904/+files/syslog.gz

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

2020-09-11 Thread Gilbertf
Just booted my machine from being off. No sound.
Messages filling kern.log and syslog.

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-09-11 Thread Joy Latten
pcsc-lite source package provides pcscd and libpcsclite1 and thus is
needed for smartcard deployment.

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

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

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

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

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

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

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

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

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

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

  Quilt packaging.

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

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

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

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

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

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

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

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

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

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

  Otherwise appears to satisfy FHS and Debian policy.

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

  

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

2020-09-11 Thread Joy Latten
pcscd is required. When removed, I am not able to get any info from the
driver about the reader or the smartcard. pcscd loads the smartcard
driver and coordinates communications.

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

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

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

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

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

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

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

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

  Has a debian/watch file.
  Quilt packaging.

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

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

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

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

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

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

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

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

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

  Quilt packaging.

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

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

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

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

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

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

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

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

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

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

  Otherwise appears to satisfy FHS and Debian policy.

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

[Desktop-packages] [Bug 1004829] Re: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all

2020-09-11 Thread dinar qurbanov
mic connected to front is not working with this motherboard in ubuntu
20.04.

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

Title:
  [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Mic doesn't work on Ubuntu 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  srinivas   2967 F pulseaudio
   /dev/snd/controlC0:  srinivas   2967 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,1458a002,00100302'
 Controls  : 42
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 19'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100200'
 Controls  : 24
 Simple ctrls  : 4
  Date: Sat May 26 14:20:32 2012
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   2967  2967  srinivas  F pulseaudio
   /dev/snd/controlC0:  srinivas  F pulseaudio
  Symptom_Jack: Pink Mic, Front
  Symptom_Type: No sound at all
  Title: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all
  UpgradeStatus: Upgraded to precise on 2012-04-27 (29 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-MA74GMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA74GMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1004829] Re: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all

2020-09-11 Thread dinar qurbanov
i think i should say: does not work. i cannot test that computer now.

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

Title:
  [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Mic doesn't work on Ubuntu 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  srinivas   2967 F pulseaudio
   /dev/snd/controlC0:  srinivas   2967 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,1458a002,00100302'
 Controls  : 42
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 19'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100200'
 Controls  : 24
 Simple ctrls  : 4
  Date: Sat May 26 14:20:32 2012
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   2967  2967  srinivas  F pulseaudio
   /dev/snd/controlC0:  srinivas  F pulseaudio
  Symptom_Jack: Pink Mic, Front
  Symptom_Type: No sound at all
  Title: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all
  UpgradeStatus: Upgraded to precise on 2012-04-27 (29 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-MA74GMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA74GMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

2020-09-11 Thread Hugh Ingram
This affect me too. /var/log/syslog fills up until my disk runs out of
space.

Steps to recreate:
- open a video in VLC
- pause the video
- suspend computer
- un-suspend computer

I see these errors in syslog:

Sep 11 19:01:04 SOL Thunar.desktop[12293]: [7f04e809acb0] vdpau_chroma 
filter error: video mixer features failure: An invalid handle value was 
provided.
Sep 11 19:01:04 SOL Thunar.desktop[12293]: [7f04e809acb0] vdpau_chroma 
filter error: video mixer attributes failure: An invalid handle value was 
provided.

The errors stop after closing VLC.

My .xsession-error file is very short, ~20 lines and several years old.


* OS: Ubuntu 18.04
* kernel: x86_64 Linux 4.15.0-115-generic
* VLC 3.0.8
* gpu: Nvidia GTX 970
* nvidia driver installed: 450.66

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

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

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

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

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


[Desktop-packages] [Bug 1895324] Re: Ubuntu Dock not visible after updates

2020-09-11 Thread corrado venturini
Also changing Settings->Appearance Auto-hide or Position dock does not
reappear.


** Summary changed:

- Dock not visible after updates
+ Ubuntu Dock not visible after updates

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

Title:
  Ubuntu Dock not visible after updates

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

Bug description:
  After today updates Ubuntu dock is no longer displayed.
  see attachment

  corrado@corrado-n4-gg-0905:~/Desktop$ inxi -SCMGx
  System:Host: corrado-n4-gg-0905 Kernel: 5.8.0-18-generic x86_64 bits: 64 
compiler: N/A Desktop: N/A 
 Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 
 
 Mobo: Dell model: 0C1PF2 v: A00 serial:  
UEFI: Dell v: 1.5.0 date: 12/17/2019 
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 L2 cache: 6144 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046 
 Speed: 2404 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 3136 
2: 2974 3: 3429 4: 2837 5: 2519 6: 3084 7: 2206 
 8: 3602 
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus ID: 00:02.0 
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus ID: 1-6:3 
 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
20.1.5 direct render: Yes 
  corrado@corrado-n4-gg-0905:~/Desktop$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 18:46:01 2020
  InstallationDate: Installed on 2020-09-05 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200905)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1895324] Re: Ubuntu Dock not visible after updates

2020-09-11 Thread corrado venturini
Problem with both X11 and Wayland session
Also adding an app to favorites has no effect

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

Title:
  Ubuntu Dock not visible after updates

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

Bug description:
  After today updates Ubuntu dock is no longer displayed.
  see attachment

  corrado@corrado-n4-gg-0905:~/Desktop$ inxi -SCMGx
  System:Host: corrado-n4-gg-0905 Kernel: 5.8.0-18-generic x86_64 bits: 64 
compiler: N/A Desktop: N/A 
 Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 
 
 Mobo: Dell model: 0C1PF2 v: A00 serial:  
UEFI: Dell v: 1.5.0 date: 12/17/2019 
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 L2 cache: 6144 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046 
 Speed: 2404 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 3136 
2: 2974 3: 3429 4: 2837 5: 2519 6: 3084 7: 2206 
 8: 3602 
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus ID: 00:02.0 
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus ID: 1-6:3 
 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
20.1.5 direct render: Yes 
  corrado@corrado-n4-gg-0905:~/Desktop$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 18:46:01 2020
  InstallationDate: Installed on 2020-09-05 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200905)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1895325] [NEW] driver does not detect usb-printer

2020-09-11 Thread Masha Mariia
Public bug reported:

masha@masha-Lenovo-G50-80:~$ lsmod | grep usb
rtsx_usb_ms24576  0
memstick   20480  1 rtsx_usb_ms
btusb  57344  0
btrtl  24576  1 btusb
btbcm  16384  1 btusb
btintel24576  1 btusb
usblp  24576  0
bluetooth 581632  31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
rtsx_usb_sdmmc 32768  0
usbhid 57344  0
hid   131072  3 hid_a4tech,usbhid,hid_generic
rtsx_usb   28672  2 rtsx_usb_sdmmc,rtsx_usb_ms
masha@masha-Lenovo-G50-80:~$ tail -f /var/log/syslog
Sep 11 19:35:55 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: 
Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00106.
Sep 11 19:35:55 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: 
Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c0010a.
Sep 11 19:36:04 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: 
Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00114.
Sep 11 19:36:23 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: 
Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c0011b.
Sep 11 19:36:23 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: 
Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c0011f.
Sep 11 19:36:28 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: 
Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00129.
Sep 11 19:36:37 masha-Lenovo-G50-80 kernel: [13784.532617] usb 1-3: USB 
disconnect, device number 11
Sep 11 19:36:37 masha-Lenovo-G50-80 kernel: [13784.533279] usblp0: removed
Sep 11 19:36:39 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181143 was not 
found when attempting to remove it
Sep 11 19:36:47 masha-Lenovo-G50-80 gnome-shell[1854]: Window manager warning: 
Invalid WM_TRANSIENT_FOR window 0x2c8 specified for 0x2c00130.
Sep 11 19:37:16 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181573 was not 
found when attempting to remove it
Sep 11 19:37:21 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181611 was not 
found when attempting to remove it
Sep 11 19:37:24 masha-Lenovo-G50-80 gnome-shell[1854]: Source ID 181625 was not 
found when attempting to remove it
Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.671345] usb 1-3: new 
high-speed USB device number 12 using xhci_hcd
Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824523] usb 1-3: New USB 
device found, idVendor=04a9, idProduct=181e, bcdDevice= 1.01
Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824530] usb 1-3: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824534] usb 1-3: Product: 
E410 series
Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824537] usb 1-3: 
Manufacturer: Canon
Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.824540] usb 1-3: 
SerialNumber: D22179
Sep 11 19:40:01 masha-Lenovo-G50-80 kernel: [13988.834767] usblp 1-3:1.1: 
usblp0: USB Bidirectional printer dev 12 if 1 alt 0 proto 2 vid 0x04A9 pid 
0x181E
Sep 11 19:40:01 masha-Lenovo-G50-80 systemd[1]: Started Configure Plugged-In 
Printer.
Sep 11 19:40:01 masha-Lenovo-G50-80 udev-configure-printer: add usb-001-012
Sep 11 19:40:02 masha-Lenovo-G50-80 udev-configure-printer: device devpath is 
/devices/pci:00/:00:14.0/usb1/1-3
Sep 11 19:40:02 masha-Lenovo-G50-80 udev-configure-printer: Device already 
handled
Sep 11 19:40:02 masha-Lenovo-G50-80 systemd[1]: 
configure-printer@usb-001-012.service: Main process exited, code=exited, 
status=1/FAILURE
Sep 11 19:40:02 masha-Lenovo-G50-80 systemd[1]: 
configure-printer@usb-001-012.service: Failed with result 'exit-code'.
Sep 11 19:40:04 masha-Lenovo-G50-80 kernel: [13991.650602] usb 1-3: USB 
disconnect, device number 12
Sep 11 19:40:04 masha-Lenovo-G50-80 kernel: [13991.651070] usblp0: removed
Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.451332] usb 1-3: new 
high-speed USB device number 13 using xhci_hcd
Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607883] usb 1-3: New USB 
device found, idVendor=04a9, idProduct=181e, bcdDevice= 1.01
Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607889] usb 1-3: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607893] usb 1-3: Product: 
E410 series
Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607896] usb 1-3: 
Manufacturer: Canon
Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.607899] usb 1-3: 
SerialNumber: D22179
Sep 11 19:40:05 masha-Lenovo-G50-80 kernel: [13992.619190] usblp 1-3:1.1: 
usblp0: USB Bidirectional printer dev 13 if 1 alt 0 proto 2 vid 0x04A9 pid 
0x181E
Sep 11 19:40:05 masha-Lenovo-G50-80 systemd[1]: Started Configure Plugged-In 
Printer.
Sep 11 19:40:05 masha-Lenovo-G50-80 udev-configure-printer: add usb-001-013
Sep 11 19:40:05 masha-Lenovo-G50-80 udev-configure-printer: device devpath is 

[Desktop-packages] [Bug 1895324] [NEW] Ubuntu Dock not visible after updates

2020-09-11 Thread corrado venturini
Public bug reported:

After today updates Ubuntu dock is no longer displayed.
see attachment

corrado@corrado-n4-gg-0905:~/Desktop$ inxi -SCMGx
System:Host: corrado-n4-gg-0905 Kernel: 5.8.0-18-generic x86_64 bits: 64 
compiler: N/A Desktop: N/A 
   Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 
 
   Mobo: Dell model: 0C1PF2 v: A00 serial:  
UEFI: Dell v: 1.5.0 date: 12/17/2019 
CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 L2 cache: 6144 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046 
   Speed: 2404 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 3136 2: 
2974 3: 3429 4: 2837 5: 2519 6: 3084 7: 2206 
   8: 3602 
Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus ID: 00:02.0 
   Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus ID: 1-6:3 
   Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
   OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
20.1.5 direct render: Yes 
corrado@corrado-n4-gg-0905:~/Desktop$

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 11 18:46:01 2020
InstallationDate: Installed on 2020-09-05 (6 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200905)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

** Attachment added: "Screenshot from 2020-09-11 18-35-36.png"
   
https://bugs.launchpad.net/bugs/1895324/+attachment/5409875/+files/Screenshot%20from%202020-09-11%2018-35-36.png

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

Title:
  Ubuntu Dock not visible after updates

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

Bug description:
  After today updates Ubuntu dock is no longer displayed.
  see attachment

  corrado@corrado-n4-gg-0905:~/Desktop$ inxi -SCMGx
  System:Host: corrado-n4-gg-0905 Kernel: 5.8.0-18-generic x86_64 bits: 64 
compiler: N/A Desktop: N/A 
 Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 
 
 Mobo: Dell model: 0C1PF2 v: A00 serial:  
UEFI: Dell v: 1.5.0 date: 12/17/2019 
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 L2 cache: 6144 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046 
 Speed: 2404 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 3136 
2: 2974 3: 3429 4: 2837 5: 2519 6: 3084 7: 2206 
 8: 3602 
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus ID: 00:02.0 
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus ID: 1-6:3 
 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: 
fbdev,vesa resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
20.1.5 direct render: Yes 
  corrado@corrado-n4-gg-0905:~/Desktop$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 18:46:01 2020
  InstallationDate: Installed on 2020-09-05 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200905)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1894452] Re: shutdown delay because of cups

2020-09-11 Thread Till Kamppeter
cups-filters 1.28.2 uploaded to Ubuntu.

** Changed in: cups-filters (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  shutdown delay because of cups

Status in cups-filters package in Ubuntu:
  Fix Committed

Bug description:
  Both my desktop and laptop running 20.10 have a 90 second delay
  shutting down (power off or restart).  Getting message;

  A stop job is Running for Make remote CUPS printers available locally

  After 90 seconds the shutdown continues to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups 2.3.3-2ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Sep  6 18:10:20 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  KernLog:
   
  Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
  MachineType: CLEVO CO. W35_37ET
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

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

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


[Desktop-packages] [Bug 1892783] Re: [SRU] libreoffice 6.4.6 for focal

2020-09-11 Thread Heather Ellsworth
Upgraded libreoffice from 1:6.4.5-0ubuntu0.20.04.1 to
1:6.4.6-0ubuntu0.20.04.1 from focal-proposed in a clean and up-to-date
focal amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

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

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

Title:
  [SRU] libreoffice 6.4.6 for focal

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 
6.4.5 is currently in focal.
 For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs
 (that's a total of 106 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 106 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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


[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

2020-09-11 Thread Tim Passingham
Any chance this will get into focal soon?  It's still making a mess of
my spreadsheets.

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Triaged

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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


[Desktop-packages] [Bug 1895317] Re: Intel driver not working

2020-09-11 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Intel driver not working

Status in xorg package in Ubuntu:
  New

Bug description:
  i upgraded my sony vaio model VPCEB1E0E from windows 7 to ubuntu but
  lost my intel driver before i upgraded. problem caused is a black dead
  screen on my laptop but i have access to a monitor which im currently
  using to use ubuntu. i need the driver for my laptop screen (primary
  screen) to work. please give me a solution. thanks in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.4.0-050400-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 17:06:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 450.66, 5.4.0-050400-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Core Processor Integrated Graphics Controller 
[104d:9071]
  InstallationDate: Installed on 2020-09-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Sony Corporation VPCEB1E0E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic 
root=UUID=700fef99-f312-4e95-a170-69e4f1a09494 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0230Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0230Y8:bd01/26/2010:svnSonyCorporation:pnVPCEB1E0E:pvrC603YD6R:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEB1E0E
  dmi.product.sku: N/A
  dmi.product.version: C603YD6R
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102+git2009040630.77687f~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009101930.2f62a4~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1895309] Re: No task bar, no applications on gnome shell

2020-09-11 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895309

** Tags added: iso-testing

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

Title:
  No task bar, no applications on gnome shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is just gnome-shell but I have to start
  somewhere. This is what Ubuntu looks like to the end user after the
  OEM setup. No task bar on the left, no applications in the shell
  unless you search for them knowing they're there.

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

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


[Desktop-packages] [Bug 1895317] [NEW] Intel driver not working

2020-09-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

i upgraded my sony vaio model VPCEB1E0E from windows 7 to ubuntu but
lost my intel driver before i upgraded. problem caused is a black dead
screen on my laptop but i have access to a monitor which im currently
using to use ubuntu. i need the driver for my laptop screen (primary
screen) to work. please give me a solution. thanks in advance

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.4.0-050400-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 11 17:06:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 450.66, 5.4.0-050400-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Core Processor Integrated Graphics Controller 
[104d:9071]
InstallationDate: Installed on 2020-09-10 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Sony Corporation VPCEB1E0E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic 
root=UUID=700fef99-f312-4e95-a170-69e4f1a09494 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/26/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0230Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0230Y8:bd01/26/2010:svnSonyCorporation:pnVPCEB1E0E:pvrC603YD6R:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEB1E0E
dmi.product.sku: N/A
dmi.product.version: C603YD6R
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102+git2009040630.77687f~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3~git2009101930.2f62a4~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu
-- 
Intel driver not working
https://bugs.launchpad.net/bugs/1895317
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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


[Desktop-packages] [Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions

2020-09-11 Thread Launchpad Bug Tracker
This bug was fixed in the package mutter - 3.37.91-1ubuntu1

---
mutter (3.37.91-1ubuntu1) groovy; urgency=medium

  * Merge with debian, including new upstream stable release, remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refresh as per upstream changes

mutter (3.37.91-1) experimental; urgency=medium

  * New upstream release
- Support unredirecting fullscreen wayland surfaces
- Support area screencasts
- Allow inhibiting remote access
- Drive each monitor by its own frame clock (LP: #1730460)
- Fix copy/paste failures on X11 (LP: #1879968)
- Make window-aliveness checks less aggressive
- Limit mipmap levels when rendering background (LP: #1862308)
- Remove more long-deprecated Clutter APIs
- Support custom keyboard layouts in $XDG_CONFIG_HOME/xkb
- Optimize resource scale computation for wayland fractional scaling
- Support tap-button-map and tap-drag-lock touchpad settings
- Fix wine copy & paste
- Add API to launch trusted wayland clients
- Invalidate offscreen effect cache on video memory purge (LP: #1855757)
  * debian: Update package and file names to mutter API version
  * debian/control: Bump dependencies to match upstream requirements
  * debian/clean: Remove as HOME and XRD are managed now by dh
  * debian/copyright: Avoid redundant globbing patterns
  * debian/gbp.conf: target upstream/latest branch
  * debian/libmutter-7-0.symbols: Update symbols file
  * debian/patches: Refresh
  * d/p/debian/tests-Tag-closed-transient-no-input-tests-as-flaky.patch:
- Renamed into d/p/debian/tests-Tag-unstable-tests-as-flaky.patch
- Reduced the number of "flaky" tests to the ones time-dependent only
  * debian/rules:
- Compute and generate a MUTTER_API_VERSION and replace it everywhere
- Remove XDG_RUNTIME_DIR wrapper workaround
- Don't run tests at all in riscv64
- Don't set again default configuration values (it makes the delta clearer)
- Never ignore test failures in amd64
- Remove test num processes re-configuration
- Run tests in s390x, no failures currently
- Don't test in alpha hppa powerpc sparc64 x32 (Closes: #959415)
  * debian/with-temp-xdg-runtime-dir: Dropped, new dh will handle it for us
  * debian/watch: Scan for all versions, not just the stable-branch
  * debian/*.install: Use dh variable substitution in install files

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

 -- Marco Trevisan (Treviño)   Fri, 28 Aug 2020
01:10:32 +0200

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

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

Title:
  Very poor multi-monitor performance in Wayland sessions

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Upstream bug:
  https://gitlab.gnome.org/GNOME/mutter/issues/3

  ---

  When dragging a window between displays, I can see cpu usage increase
  while framerate drops dramatically to single numbers.

  Desktop scaling is 1.0, one is a WXGA screen and another FHD.

  Ubuntu session (wayland), 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:09:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

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

[Desktop-packages] [Bug 1886592] Re: Add support for VMware Horizon SSO to gnome-shell

2020-09-11 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-shell - 3.37.91-1ubuntu1

---
gnome-shell (3.37.91-1ubuntu1) groovy; urgency=medium

  * Merge with debian, including new upstream release, remaining changes:
- Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
- Add some Recommends:
  + ubuntu-session (| gnome-session) to have the ubuntu session available
  + xserver-xorg-legacy
  + yaru-theme-gnome-shell for the default ubuntu theming
- Update debian/gbp.conf with Ubuntu settings
- gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
- ubuntu/desktop_detect.patch:
  + add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
- ubuntu/smarter_alt_tab.patch:
  + quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
- ubuntu/lightdm-user-switching.patch:
  + Allow user switching when using LightDM.
- ubuntu/lock_on_suspend.patch
  + Respect Ubuntu's lock-on-suspend setting.
- ubuntu/background_login.patch
  + Change default background color as we modified the default GDM color
for our ubuntu session.
- ubuntu/gdm_alternatives.patch
  + Add support for GDM3 theme alternatives
- optional-hot-corner.patch
  + enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
- main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  + Improve debug JS tracing for crash reports
- st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
  + Fix crash on theme changes
- ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  + stop searches when requested from UI
- magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  + Show monitor scaled cursor when magnifier is enabled
- Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
  * debian/patches: Refreshed
  * debian/control:
- Set breaks on upcoming core extensions. This update is going to break
  them, so we need extensions updates before migra
- Set breaks on upcoming yaru theme.
  There are not big deals using the current yaru, but better to wait for a
  suynced one.

gnome-shell (3.37.91-1) experimental; urgency=medium

  * New upstream release:
- Inhibit remote access when disabled by session mode
- Remove Frequent view from app picker
- Allow rearranging items in app picker
- Add support for parental controls filtering
- Support pre-authenticated logins in vmware environments (LP: #1886592)
- Update microphone icon on input volume changes
- Support prepending workspace with horizontal layouts
- Move calendar events out of notifications list
- Expose actor tree in looking glass
- Add support for "PrefersNonDefaultGPU" desktop key
- Move screencasting into a separate service (needs pipewire)
- Default to not installing updates on low battery
- Refactor and clean up app picker pagination (LP: #1873725)
- Misc fixes and memory improvements
  * debian/control:
- Depend on debhelper-compat = 13
- Remove useless dependency on mutter (the binary)
- Test depend on gir1.2-upowerglib-1.0
- Update build dependencies to match upstream
- Remove leading space in gnome-shell-extension-prefs description
  * debian/patches: Drop them all
  * debian/rules:
- Don't manually set --fail-missing (included in dh 13)
- Remove uneeded test environment variables overrides (included in dh 13)
  * debian/sources/lintian-override:
- Override some desktop files related warnings
  * debian/gbp.conf: Point to upstream/latest
  * debian/watch: Monitor unstable versions

gnome-shell (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Fix password briefly showing on login dialog during logout if it
  was previously made visible (CVE-2020-17489, Closes: #968311)
  * Drop most patches, applied upstream

 -- Marco Trevisan (Treviño)   Thu, 27 Aug 2020
23:14:01 +0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-17489

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

2020-09-11 Thread Launchpad Bug Tracker
This bug was fixed in the package mutter - 3.37.91-1ubuntu1

---
mutter (3.37.91-1ubuntu1) groovy; urgency=medium

  * Merge with debian, including new upstream stable release, remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refresh as per upstream changes

mutter (3.37.91-1) experimental; urgency=medium

  * New upstream release
- Support unredirecting fullscreen wayland surfaces
- Support area screencasts
- Allow inhibiting remote access
- Drive each monitor by its own frame clock (LP: #1730460)
- Fix copy/paste failures on X11 (LP: #1879968)
- Make window-aliveness checks less aggressive
- Limit mipmap levels when rendering background (LP: #1862308)
- Remove more long-deprecated Clutter APIs
- Support custom keyboard layouts in $XDG_CONFIG_HOME/xkb
- Optimize resource scale computation for wayland fractional scaling
- Support tap-button-map and tap-drag-lock touchpad settings
- Fix wine copy & paste
- Add API to launch trusted wayland clients
- Invalidate offscreen effect cache on video memory purge (LP: #1855757)
  * debian: Update package and file names to mutter API version
  * debian/control: Bump dependencies to match upstream requirements
  * debian/clean: Remove as HOME and XRD are managed now by dh
  * debian/copyright: Avoid redundant globbing patterns
  * debian/gbp.conf: target upstream/latest branch
  * debian/libmutter-7-0.symbols: Update symbols file
  * debian/patches: Refresh
  * d/p/debian/tests-Tag-closed-transient-no-input-tests-as-flaky.patch:
- Renamed into d/p/debian/tests-Tag-unstable-tests-as-flaky.patch
- Reduced the number of "flaky" tests to the ones time-dependent only
  * debian/rules:
- Compute and generate a MUTTER_API_VERSION and replace it everywhere
- Remove XDG_RUNTIME_DIR wrapper workaround
- Don't run tests at all in riscv64
- Don't set again default configuration values (it makes the delta clearer)
- Never ignore test failures in amd64
- Remove test num processes re-configuration
- Run tests in s390x, no failures currently
- Don't test in alpha hppa powerpc sparc64 x32 (Closes: #959415)
  * debian/with-temp-xdg-runtime-dir: Dropped, new dh will handle it for us
  * debian/watch: Scan for all versions, not just the stable-branch
  * debian/*.install: Use dh variable substitution in install files

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

 -- Marco Trevisan (Treviño)   Fri, 28 Aug 2020
01:10:32 +0200

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

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Triaged

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1862308] Re: Desktop wallpaper is slightly blurry

2020-09-11 Thread Launchpad Bug Tracker
This bug was fixed in the package mutter - 3.37.91-1ubuntu1

---
mutter (3.37.91-1ubuntu1) groovy; urgency=medium

  * Merge with debian, including new upstream stable release, remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refresh as per upstream changes

mutter (3.37.91-1) experimental; urgency=medium

  * New upstream release
- Support unredirecting fullscreen wayland surfaces
- Support area screencasts
- Allow inhibiting remote access
- Drive each monitor by its own frame clock (LP: #1730460)
- Fix copy/paste failures on X11 (LP: #1879968)
- Make window-aliveness checks less aggressive
- Limit mipmap levels when rendering background (LP: #1862308)
- Remove more long-deprecated Clutter APIs
- Support custom keyboard layouts in $XDG_CONFIG_HOME/xkb
- Optimize resource scale computation for wayland fractional scaling
- Support tap-button-map and tap-drag-lock touchpad settings
- Fix wine copy & paste
- Add API to launch trusted wayland clients
- Invalidate offscreen effect cache on video memory purge (LP: #1855757)
  * debian: Update package and file names to mutter API version
  * debian/control: Bump dependencies to match upstream requirements
  * debian/clean: Remove as HOME and XRD are managed now by dh
  * debian/copyright: Avoid redundant globbing patterns
  * debian/gbp.conf: target upstream/latest branch
  * debian/libmutter-7-0.symbols: Update symbols file
  * debian/patches: Refresh
  * d/p/debian/tests-Tag-closed-transient-no-input-tests-as-flaky.patch:
- Renamed into d/p/debian/tests-Tag-unstable-tests-as-flaky.patch
- Reduced the number of "flaky" tests to the ones time-dependent only
  * debian/rules:
- Compute and generate a MUTTER_API_VERSION and replace it everywhere
- Remove XDG_RUNTIME_DIR wrapper workaround
- Don't run tests at all in riscv64
- Don't set again default configuration values (it makes the delta clearer)
- Never ignore test failures in amd64
- Remove test num processes re-configuration
- Run tests in s390x, no failures currently
- Don't test in alpha hppa powerpc sparc64 x32 (Closes: #959415)
  * debian/with-temp-xdg-runtime-dir: Dropped, new dh will handle it for us
  * debian/watch: Scan for all versions, not just the stable-branch
  * debian/*.install: Use dh variable substitution in install files

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

 -- Marco Trevisan (Treviño)   Fri, 28 Aug 2020
01:10:32 +0200

** Changed in: mutter (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  Desktop wallpaper is slightly blurry

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  Desktop wallpaper is slightly blurry in Gnome 3.34 and 3.36

  Upstream fix pending:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Feb  7 16:08:58 2020
  DisplayManager:

  InstallationDate: Installed on 2020-02-03 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  RelatedPackageVersions: mutter-common 3.34.3-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/1862308/+subscriptions

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


[Desktop-packages] [Bug 1873725] Re: Folder under applications menu doesn't show text below last line of icons.

2020-09-11 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-shell - 3.37.91-1ubuntu1

---
gnome-shell (3.37.91-1ubuntu1) groovy; urgency=medium

  * Merge with debian, including new upstream release, remaining changes:
- Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
- Add some Recommends:
  + ubuntu-session (| gnome-session) to have the ubuntu session available
  + xserver-xorg-legacy
  + yaru-theme-gnome-shell for the default ubuntu theming
- Update debian/gbp.conf with Ubuntu settings
- gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
- ubuntu/desktop_detect.patch:
  + add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
- ubuntu/smarter_alt_tab.patch:
  + quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
- ubuntu/lightdm-user-switching.patch:
  + Allow user switching when using LightDM.
- ubuntu/lock_on_suspend.patch
  + Respect Ubuntu's lock-on-suspend setting.
- ubuntu/background_login.patch
  + Change default background color as we modified the default GDM color
for our ubuntu session.
- ubuntu/gdm_alternatives.patch
  + Add support for GDM3 theme alternatives
- optional-hot-corner.patch
  + enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
- main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  + Improve debug JS tracing for crash reports
- st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch:
  + Fix crash on theme changes
- ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  + stop searches when requested from UI
- magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  + Show monitor scaled cursor when magnifier is enabled
- Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814)
  * debian/patches: Refreshed
  * debian/control:
- Set breaks on upcoming core extensions. This update is going to break
  them, so we need extensions updates before migra
- Set breaks on upcoming yaru theme.
  There are not big deals using the current yaru, but better to wait for a
  suynced one.

gnome-shell (3.37.91-1) experimental; urgency=medium

  * New upstream release:
- Inhibit remote access when disabled by session mode
- Remove Frequent view from app picker
- Allow rearranging items in app picker
- Add support for parental controls filtering
- Support pre-authenticated logins in vmware environments (LP: #1886592)
- Update microphone icon on input volume changes
- Support prepending workspace with horizontal layouts
- Move calendar events out of notifications list
- Expose actor tree in looking glass
- Add support for "PrefersNonDefaultGPU" desktop key
- Move screencasting into a separate service (needs pipewire)
- Default to not installing updates on low battery
- Refactor and clean up app picker pagination (LP: #1873725)
- Misc fixes and memory improvements
  * debian/control:
- Depend on debhelper-compat = 13
- Remove useless dependency on mutter (the binary)
- Test depend on gir1.2-upowerglib-1.0
- Update build dependencies to match upstream
- Remove leading space in gnome-shell-extension-prefs description
  * debian/patches: Drop them all
  * debian/rules:
- Don't manually set --fail-missing (included in dh 13)
- Remove uneeded test environment variables overrides (included in dh 13)
  * debian/sources/lintian-override:
- Override some desktop files related warnings
  * debian/gbp.conf: Point to upstream/latest
  * debian/watch: Monitor unstable versions

gnome-shell (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Fix password briefly showing on login dialog during logout if it
  was previously made visible (CVE-2020-17489, Closes: #968311)
  * Drop most patches, applied upstream

 -- Marco Trevisan (Treviño)   Thu, 27 Aug 2020
23:14:01 +0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-17489

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

2020-09-11 Thread Launchpad Bug Tracker
This bug was fixed in the package mutter - 3.37.91-1ubuntu1

---
mutter (3.37.91-1ubuntu1) groovy; urgency=medium

  * Merge with debian, including new upstream stable release, remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refresh as per upstream changes

mutter (3.37.91-1) experimental; urgency=medium

  * New upstream release
- Support unredirecting fullscreen wayland surfaces
- Support area screencasts
- Allow inhibiting remote access
- Drive each monitor by its own frame clock (LP: #1730460)
- Fix copy/paste failures on X11 (LP: #1879968)
- Make window-aliveness checks less aggressive
- Limit mipmap levels when rendering background (LP: #1862308)
- Remove more long-deprecated Clutter APIs
- Support custom keyboard layouts in $XDG_CONFIG_HOME/xkb
- Optimize resource scale computation for wayland fractional scaling
- Support tap-button-map and tap-drag-lock touchpad settings
- Fix wine copy & paste
- Add API to launch trusted wayland clients
- Invalidate offscreen effect cache on video memory purge (LP: #1855757)
  * debian: Update package and file names to mutter API version
  * debian/control: Bump dependencies to match upstream requirements
  * debian/clean: Remove as HOME and XRD are managed now by dh
  * debian/copyright: Avoid redundant globbing patterns
  * debian/gbp.conf: target upstream/latest branch
  * debian/libmutter-7-0.symbols: Update symbols file
  * debian/patches: Refresh
  * d/p/debian/tests-Tag-closed-transient-no-input-tests-as-flaky.patch:
- Renamed into d/p/debian/tests-Tag-unstable-tests-as-flaky.patch
- Reduced the number of "flaky" tests to the ones time-dependent only
  * debian/rules:
- Compute and generate a MUTTER_API_VERSION and replace it everywhere
- Remove XDG_RUNTIME_DIR wrapper workaround
- Don't run tests at all in riscv64
- Don't set again default configuration values (it makes the delta clearer)
- Never ignore test failures in amd64
- Remove test num processes re-configuration
- Run tests in s390x, no failures currently
- Don't test in alpha hppa powerpc sparc64 x32 (Closes: #959415)
  * debian/with-temp-xdg-runtime-dir: Dropped, new dh will handle it for us
  * debian/watch: Scan for all versions, not just the stable-branch
  * debian/*.install: Use dh variable substitution in install files

mutter (3.36.5-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Screencast fixes and improvements
- Fix glitches when subsurfaces extend outside the toplevel
- Improve background display in overview workspace switcher
- Fix wine copy & paste
- Plug memory leaks
  * Drop patches that were applied upstream

 -- Marco Trevisan (Treviño)   Fri, 28 Aug 2020
01:10:32 +0200

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

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 

[Desktop-packages] [Bug 1891815] Re: Multi-seat stopped working in Ubuntu 20.04

2020-09-11 Thread Launchpad Bug Tracker
This bug was fixed in the package gdm3 - 3.37.90-1ubuntu1

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

  [ Marco Trevisan (Treviño) ]
  * Merge with debian, containing new upstream release
  * debian/patches: Refresh
  * d/p/nvidia_prime.patch,
d/p/config_error_dialog.patch,
d/p/gdm3.service-wait-for-drm-device-before-trying-to-start-i.patch:
- Update to use meson as build system
  * d/p/meson-Fix-Xsession-input-file-name.patch:
- Rename input file from the wrong XSession to Xsession
  * d/p/ubuntu/XSession-Use-x-terminal-emulator-as-fallback-instead-of-x.patch:
- Use x-terminal-emulator as the fallback terminal instead of xterm,
  so that the user configured (very likely gnome-terminal) is used
  * Remaining changes with debian:
+ README.Debian: update for correct paths in Ubuntu
+ control.in:
  - Don't recommend desktop-base
  - Build depend on libgudev-1.0-dev
  - Depend on bash for config_error_dialog.patch
  - Update Vcs field
  - Recomends libpam-fprintd (instead of Suggests)
+ rules:
  - Don't override default user/group
  - -Dgdm-xsession=true to install upstream Xsession script
  - override dh_installinit with --no-start to avoid session being killed
+ rules, README.Debian, gdm3.8.pod:
  Use upstream custom.conf instead of daemon.conf
+ gdm3.{postinst,postrm}: rename user and group back to gdm
+ gdm3.postinst, gdm3.prerm: don't kill gdm on upgrade
+ gdm3.*.pam: Make pam_env read ~/.pam_environment
+ gdm3.install:
  - Stop installing default.desktop. It adds unnecessary clutter
("System Default") to the session chooser.
  - Don't install debian/Xsession
+ Add run_xsession.d.patch
+ Add xresources_is_a_dir.patch
  - Fix loading from /etc/X11/Xresources/*
+ Add nvidia_prime.patch:
  - Add hook to run prime-offload (as root) and prime-switch if
nvidia-prime is installed
+ Add revert_override_LANG_with_accountservices.patch:
  - On Ubuntu accountservices only stores the language and not the
full locale as needed by LANG.
+ Add dont_set_language_env.patch:
  - Don't run the set_up_session_language() function, since it
overrides variable values set by ~/.pam_environment
+ Add config_error_dialog.patch:
  - Show warning dialog in case of error in ~/.profile etc. and
don't let a syntax error make the login fail
+ Add debian/patches/revert_nvidia_wayland_blacklist.patch:
  - Don't blacklist nvidia for wayland
+ Add gdm3.service-wait-for-drm-device-before-trying-to-start-i.patch:
  - Wait for the first valid gdm device on pre-start
+ Add debian/default.pa
  - Disable Bluetooth audio devices in PulseAudio from gdm3.
+ debian/gdm3.install
  - Added details of the default.pa file
+ debian/gdm3.postinst
  - Added installation of default.pa and creation of dir if it doesn't
exist.
+ debian/greeter.dconf-defaults: Don't set Debian settings in the
  greeter's dconf DB
  * debian/patches: Fix patch not to patch debian/patches/series

  [ Simon McVittie ]
  * Add patch to remove deprecated StandardOutput=syslog from systemd unit
  * Build-Depend on systemd, for /usr/share/pkgconfig/systemd.pc.
This should fix FTBFS on the buildds.

  [ Iain Lane ]
  * debian/control: Bump depends on gnome-{session,settings-daemon,shell}
We require the newly rearranged systemd units that are in these
versions.
  * debian/control: Make gdm depend on gnome-session-common ≥ 3.37.0-2~
This is where the systemd units live now.

gdm3 (3.37.90-1) experimental; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * New upstream release:
- Updates to systemd integration
- Support killling X on login even when wayland support is disabled
- Fix multi-seat support (LP: #1891815)
- Don't keep login screen running in background on Xorg
- Fixes for when GDM isn't started on its configured initial VT
- Don't hardcode path to plymouth
- Enable wayland on cirrus
- Chrome remote desktop fix
- Always use separate session bus for greeter sessions
  This runs dbus-run-session, so the binary needs to be available
  * debian/rules:
- Build with meson
- Use --fail-missing if not in library-only mode
- Expose to meson only X bin path
  * debian/control:
- Depend on debhelper-compat = 13
- Cleanup the Build-Depends: Remove dependencies that are not required
  explicitly by gdm
  * debian/libgdm1.symbols: Remove various (private) symbols.
- They were wrongly exported as there's no trace of them in the
  public API.
  * debian/patches: Refresh as per meson port
  * d/p/16_xserver_path.patch:
- Make meson read the X bin path from environment
  * d/p/meson-Fix-keyutils-pkg-config-name.patch,
d/p/meson-Obey-at-Dcustom-conf-option-when-installing-custom..patch,

[Desktop-packages] [Bug 1895312] [NEW] Network Manager network configuration pages showing compressed, overlap of text fields

2020-09-11 Thread Thomas Ward
Public bug reported:

Originally reported on Ask Ubuntu
(https://askubuntu.com/questions/1266039/networkmanager-gui-problem)

The network manager screen for editing network configuration data in
Ubuntu 20.04 is compressed and overlapping text fields incorrectly,
resulting in Bad UI.

The attached screenshot is an example of this behavior on a wifi network
settings page.

This is a recent issue, it's possible an update to either the theme or
some other component of 20.04 resulted in this compressed page view
area.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager-gnome 1.8.24-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 11 11:16:35 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-11-21 (659 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to focal on 2020-08-23 (18 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-09-11 11-18-39.png"
   
https://bugs.launchpad.net/bugs/1895312/+attachment/5409821/+files/Screenshot%20from%202020-09-11%2011-18-39.png

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

Title:
  Network Manager network configuration pages showing compressed,
  overlap of text fields

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Originally reported on Ask Ubuntu
  (https://askubuntu.com/questions/1266039/networkmanager-gui-problem)

  The network manager screen for editing network configuration data in
  Ubuntu 20.04 is compressed and overlapping text fields incorrectly,
  resulting in Bad UI.

  The attached screenshot is an example of this behavior on a wifi
  network settings page.

  This is a recent issue, it's possible an update to either the theme or
  some other component of 20.04 resulted in this compressed page view
  area.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager-gnome 1.8.24-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 11:16:35 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-21 (659 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to focal on 2020-08-23 (18 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

2020-09-11 Thread RdT
Hi Cagnulein - thank you so much for making this patch!  I am having
trouble installing it however on MX Linux 19.2, which is based on Debian
10. Your file name says your patch is for Onboard version 1.3.1-5,
however when you unzip the file the version of Onboard contained within
is 1.4.1-5.  I am trying to install Onboard 1.4.1-5 and your .deb files
onto my Debian 10 Buster system, but it won't let me install any version
of Onboard newer than 1.4.1-4.  How did you install your patched version
to your Debian 10 system?  Thank you!

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in onboard package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

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

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


[Desktop-packages] [Bug 1895309] Re: No task bar, no applications on gnome shell

2020-09-11 Thread Guilherme Campos
** Attachment added: "Clipboard02.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1895309/+attachment/5409820/+files/Clipboard02.png

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

Title:
  No task bar, no applications on gnome shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is just gnome-shell but I have to start
  somewhere. This is what Ubuntu looks like to the end user after the
  OEM setup. No task bar on the left, no applications in the shell
  unless you search for them knowing they're there.

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

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


[Desktop-packages] [Bug 1895309] [NEW] No task bar, no applications on gnome shell

2020-09-11 Thread Guilherme Campos
Public bug reported:

I'm not 100% sure this is just gnome-shell but I have to start
somewhere. This is what Ubuntu looks like to the end user after the OEM
setup. No task bar on the left, no applications in the shell unless you
search for them knowing they're there.

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

** Attachment added: "Clipboard01.png"
   
https://bugs.launchpad.net/bugs/1895309/+attachment/5409819/+files/Clipboard01.png

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

Title:
  No task bar, no applications on gnome shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm not 100% sure this is just gnome-shell but I have to start
  somewhere. This is what Ubuntu looks like to the end user after the
  OEM setup. No task bar on the left, no applications in the shell
  unless you search for them knowing they're there.

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

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


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

2020-09-11 Thread Dimitar Kotsev
On my machine the touchpad is recognized and even the click events are
registered but moving produces clicking instead of moving the cursor.

Legion 5 15ARH05, kernel Linux 5.8.6-1-MANJARO,

dmesg | grep MSFT
[  162.390501] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy 
regulator
[  162.390521] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy 
regulator
[  162.670737] input: MSFT0001:00 06CB:7F28 Mouse as 
/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0003/input/input17
[  162.670910] input: MSFT0001:00 06CB:7F28 Touchpad as 
/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0003/input/input18
[  162.671186] hid-generic 0018:06CB:7F28.0003: input,hidraw2: I2C HID 
v1.00 Mouse [MSFT0001:00 06CB:7F28] on i2c-MSFT0001:00
[  162.813553] input: MSFT0001:00 06CB:7F28 Mouse as 
/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0003/input/input20
[  162.813965] input: MSFT0001:00 06CB:7F28 Touchpad as 
/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0003/input/input21
[  162.814182] hid-multitouch 0018:06CB:7F28.0003: input,hidraw2: I2C HID 
v1.00 Mouse [MSFT0001:00 06CB:7F28] on i2c-MSFT0001:00


cat /proc/bus/input/devices

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

I: Bus=0018 Vendor=06cb Product=7f28 Version=0100
N: Name="MSFT0001:00 06CB:7F28 Touchpad"
P: Phys=i2c-MSFT0001:00
S: 
Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:06CB:7F28.0004/input/input24
U: Uniq=
H: Handlers=event13 mouse2 
B: PROP=5
B: EV=1b
B: KEY=e520 1 0 0 0 0
B: ABS=2e08003
B: MSC=20

When `blacklist hid_multitouch` the coursor is moving with absolute
coordinates and hangs which makes it unusable.

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-09-11 Thread Andreas Hasenack
I filed https://bugs.launchpad.net/ubuntu/+source/base-
files/+bug/1895302 for that. Do you happen to know a good way to test
the first-time installation of base-files with debootstrap? It would be
awesome if I could give it a ppa to consider, in addition to the
archive, and it would then just pick my test base-files instead of the
one from the archive.

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in base-files source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.

  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction 

[Desktop-packages] [Bug 1722229] Re: "Some title" notification displayed when there is no network

2020-09-11 Thread Ken VanDine
** Also affects: snap-store-desktop
   Importance: Undecided
   Status: New

** Changed in: snap-store-desktop
   Importance: Undecided => Medium

** Changed in: snap-store-desktop
   Status: New => Triaged

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

Title:
  "Some title" notification displayed when there is no network

Status in snap-store-desktop:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  gnome-software 3.26.1-0ubuntu1~ppa1

  Test Case:
  1. Without network (no network link or behind a captive portal) a 
notification with the message "Some Title" is displayed

  Expected result
  Nothing is displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 14:44:23 2017
  InstallationDate: Installed on 2013-09-03 (1496 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store-desktop/+bug/179/+subscriptions

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


[Desktop-packages] [Bug 1102001] Re: CUPS recommends incorrect driver for Samsung ML-1670

2020-09-11 Thread Nitin Mirg
For seven Days i banged my  head to print from Samsung 1676p laser
printer, i was about to switch to Windows but read this post, CLP 310
works absolutely fine so THANK YOU

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

Title:
  CUPS recommends incorrect driver for Samsung ML-1670

Status in splix package in Ubuntu:
  Incomplete
Status in splix package in Unity Linux:
  New

Bug description:
  STR:

  1) From the Printers dialogue, select Add Printer.
  2) Select "Samsung ML-1670" from the devices list (connected via USB)
  3) Select "Select printer from database" and "Samsung (recommended)"
  4) Select "ML-1660 (recommended)" from the Models, and "Samsung ML-1660, 
2.0.0 [en] (recommended)" from Drivers
  5) Click through and Apply
  6) Print a test page

  The test page isn't printed. Instead a plain text page is printed that
  says:

  INTERNAL ERROR - Please use the proper driver.

   POSITION : 0x0 (0)
   SYSTEM   : h6fw_5.49/xl_op
   LINE : 180
   VERSION  : SPL 5.49 10-20-2010

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11.3
  ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  CheckboxSubmission: dd3689fa6394f60ec14dbe98d0bab891
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Sun Jan 20 10:25:54 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-08-23 (880 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  KernLog:
   Jan 20 09:59:31 sixtymilesmile kernel: [54885.307388] ata1.00: ACPI cmd 
f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
   Jan 20 09:59:31 sixtymilesmile kernel: [54885.308453] ata1.00: ACPI cmd 
f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
  Lpstat:
   device for Phaser-6100: usb://Xerox/Phaser%206100?serial=REP167734...
   device for Samsung-ML-1670-Series: 
usb://Samsung/ML-1670%20Series?serial=Z6GEBKFB502893V.
   device for Xerox-Phaser-6100: ipps://xerox/printers/raw
   device for Xerox-Xerox-Phaser-6100DN: 
dnssd://Xerox%20Phaser%206100DN%20(XRXf0ae4d08)._printer._tcp.local/
  MachineType: Sony Corporation VPCF11J0E
  MarkForUpload: True
  Papersize: a4
  PpdFiles:
   Samsung-ML-1670-Series: Samsung ML-1660, 2.0.0
   Xerox-Xerox-Phaser-6100DN: Xerox Phaser 6100, 2.0.0
   Phaser-6100: Xerox Phaser 6100 Foomatic/Postscript
   Xerox-Phaser-6100: Xerox Phaser 6100, 2.0.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic 
root=/dev/mapper/hostname-root ro acpi_sleep=nonvs splash quiet nomodeset 
xbmc=autostart,nodiskmount loglevel=0
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-11-05 (75 days ago)
  dmi.bios.date: 02/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0260Y6
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0260Y6:bd02/26/2010:svnSonyCorporation:pnVPCF11J0E:pvrC604LLNJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF11J0E
  dmi.product.version: C604LLNJ
  dmi.sys.vendor: Sony Corporation

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

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


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

2020-09-11 Thread Franck VAISSIERE
Tested on last manjaro k5.8, and currently on debian sid unstable
(k5.8.0-1)and same issue with touchpad.

Same results as above...
Lenovo Gaming 3 15ARH05

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

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

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

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

[Desktop-packages] [Bug 1893484] Re: Google Chrome 85.0.4183.83 crahses with SIGSEGV

2020-09-11 Thread David Williams
C#8

I tried removing ~/.config/chromium but it did not change the empty
window problem.

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

Title:
  Google Chrome 85.0.4183.83 crahses with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After an Update, the new version Google Chrome 85.0.4183.83  crashes
  with SIGSEGV.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  google-chrome-stable   85.0.4183.83-1 
  amd64The web browser from Google

  3) What you expected to happen
  Load the initial page or load my themes and configurations

  4) What happened instead
  It show the initial page, ask for Restore pages? when clicked it freezes for 
a moment and then a crash with:
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
  +++ killed by SIGSEGV (core dumped) +++

  
  Previous version was working fine.

  I de-installed, removed all configurations and themes and tried again.
  Same issue.

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

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


[Desktop-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card

2020-09-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
  detect card

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  kernel 5.4.0-47-generic #51
  upgraded today to this new kernel
  sound is now totally broken
  kern.org and syslog are filling with those messages every second, in loop, 
with no end to it :

  Sep  8 19:42:34 orion kernel: [  147.398030] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20970500
  Sep  8 19:42:35 orion kernel: [  148.410043] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20a70500
  Sep  8 19:42:36 orion kernel: [  149.413955] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20b70500
  Sep  8 19:42:37 orion kernel: [  150.421890] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x201f0500
  Sep  8 19:42:38 orion kernel: [  151.453799] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:39 orion kernel: [  152.461793] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:41 orion kernel: [  153.473734] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:42 orion kernel: [  154.477653] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:43 orion kernel: [  155.481576] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:44 orion kernel: [  156.489620] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015
  Sep  8 19:42:45 orion kernel: [  157.497553] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x2043b000
  Sep  8 19:42:46 orion kernel: [  158.509530] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x20470740
  Sep  8 19:42:47 orion kernel: [  159.513471] snd_hda_intel :00:1f.3: No 
response from codec, resetting bus: last cmd=0x204f0015

  Because of this, machine has become very slow and response time is awful
  Login into the machine, even trying to launch a simple program can take up to 
30 seconds of wait before anything happens.

  Sound was working fine with previous kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gf 1758 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 19:42:19 2020
  InstallationDate: Installed on 2020-08-29 (9 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

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


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

2020-09-11 Thread Marcio
The impression that I get is that will never be fixed

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

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

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

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

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

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

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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


[Desktop-packages] [Bug 1895292] Re: package sane-utils 1.0.29-0ubuntu5.1 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 2

2020-09-11 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package sane-utils 1.0.29-0ubuntu5.1 failed to install/upgrade:
  installed sane-utils package post-installation script subprocess
  returned error exit status 2

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I'm installing ubuntu for the first time. 
  I downloaded the iso from Deluge torrent.
  I then burned the iso to a bootable usb using rufus.
  I restarted my computer and tried to install from the usb and was stopped by 
an error message.
  It said usb-partman exit code: 10, but I couldn't copy the error at that 
point in the process.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sane-utils 1.0.29-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445.1
  Date: Fri Sep 11 07:29:48 2020
  ErrorMessage: installed sane-utils package post-installation script 
subprocess returned error exit status 2
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: sane-backends
  Title: package sane-utils 1.0.29-0ubuntu5.1 failed to install/upgrade: 
installed sane-utils package post-installation script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1895292] [NEW] package sane-utils 1.0.29-0ubuntu5.1 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 2

2020-09-11 Thread Bret Fanning
Public bug reported:

I'm installing ubuntu for the first time. 
I downloaded the iso from Deluge torrent.
I then burned the iso to a bootable usb using rufus.
I restarted my computer and tried to install from the usb and was stopped by an 
error message.
It said usb-partman exit code: 10, but I couldn't copy the error at that point 
in the process.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: sane-utils 1.0.29-0ubuntu5.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
Date: Fri Sep 11 07:29:48 2020
ErrorMessage: installed sane-utils package post-installation script subprocess 
returned error exit status 2
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: sane-backends
Title: package sane-utils 1.0.29-0ubuntu5.1 failed to install/upgrade: 
installed sane-utils package post-installation script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package sane-utils 1.0.29-0ubuntu5.1 failed to install/upgrade:
  installed sane-utils package post-installation script subprocess
  returned error exit status 2

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I'm installing ubuntu for the first time. 
  I downloaded the iso from Deluge torrent.
  I then burned the iso to a bootable usb using rufus.
  I restarted my computer and tried to install from the usb and was stopped by 
an error message.
  It said usb-partman exit code: 10, but I couldn't copy the error at that 
point in the process.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sane-utils 1.0.29-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.445.1
  Date: Fri Sep 11 07:29:48 2020
  ErrorMessage: installed sane-utils package post-installation script 
subprocess returned error exit status 2
  LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: sane-backends
  Title: package sane-utils 1.0.29-0ubuntu5.1 failed to install/upgrade: 
installed sane-utils package post-installation script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1893484] Re: Google Chrome 85.0.4183.83 crahses with SIGSEGV

2020-09-11 Thread alex-mobigo
C#4

Maybe sudo rm -rf ~/.config/chromium/ would fix the empty window too

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

Title:
  Google Chrome 85.0.4183.83 crahses with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After an Update, the new version Google Chrome 85.0.4183.83  crashes
  with SIGSEGV.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  google-chrome-stable   85.0.4183.83-1 
  amd64The web browser from Google

  3) What you expected to happen
  Load the initial page or load my themes and configurations

  4) What happened instead
  It show the initial page, ask for Restore pages? when clicked it freezes for 
a moment and then a crash with:
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
  +++ killed by SIGSEGV (core dumped) +++

  
  Previous version was working fine.

  I de-installed, removed all configurations and themes and tried again.
  Same issue.

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

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


[Desktop-packages] [Bug 1893484] Re: Google Chrome 85.0.4183.83 crahses with SIGSEGV

2020-09-11 Thread alex-mobigo
Removing everything from:

sudo rm -rf ~/.config/google-chrome/

fixed the issue, but lost history, password, configurations, etc...

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

Title:
  Google Chrome 85.0.4183.83 crahses with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  After an Update, the new version Google Chrome 85.0.4183.83  crashes
  with SIGSEGV.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ii  google-chrome-stable   85.0.4183.83-1 
  amd64The web browser from Google

  3) What you expected to happen
  Load the initial page or load my themes and configurations

  4) What happened instead
  It show the initial page, ask for Restore pages? when clicked it freezes for 
a moment and then a crash with:
  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x34ff40} --
  +++ killed by SIGSEGV (core dumped) +++

  
  Previous version was working fine.

  I de-installed, removed all configurations and themes and tried again.
  Same issue.

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

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


[Desktop-packages] [Bug 1895284] Re: Some issues...

2020-09-11 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Some issues...

Status in xorg package in Ubuntu:
  New

Bug description:
  Mozilla would not respond to closing windows. Took a long time to respond.
  Screen could not be awoken after going to sleep. Stayed black. HD kept 
running.
  Forced shut down. Rebooted fine. Launched Mozilla and it got stuck on program 
startup.
  Forced shut down again. Reooted fne. Ran Xdiagnose. Got redirected here after 
bug reporting.
  Mozilla works fine now!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
  Uname: Linux 4.15.0-117-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: i386
  CompositorRunning: None
  Date: Fri Sep 11 12:48:35 2020
  DistUpgraded: 2020-05-29 12:17:15,420 DEBUG /openCache(), new cache size 62484
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1043:14e2]
 Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1043:14e2]
  InstallationDate: Installed on 2017-07-12 (1156 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: ASUSTeK Computer Inc. A8E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=8064a5cd-fa12-4277-a7b0-317979a30b37 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-05-29 (105 days ago)
  dmi.bios.date: 03/24/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: A8E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr302:bd03/24/2008:svnASUSTeKComputerInc.:pnA8E:pvr1.0:rvnASUSTeKComputerInc.:rnA8E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: A8E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Aug 17 10:23:03 2018
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17476 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

2020-09-11 Thread x
Happens only when I plug the wireless mouse in. Presses ALT key non
stop/randomly.

Description:Ubuntu 20.04.1 LTS
Release:20.04
Linux 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 
x86_64 GNU/Linux


Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[3072]: (II) event4  - MOSART 
Semi. 2.4G Keyboard Mouse: is tagged by udev as: Mouse
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[3072]: (II) event4  - MOSART 
Semi. 2.4G Keyboard Mouse: device is a pointer
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[3072]: (II) config/udev: 
Adding input device MOSART Semi. 2.4G Keyboard Mouse (/dev/input/event7)
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[3072]: (II) No input driver 
specified, ignoring this device.
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[3072]: (II) This device may 
have been added with another device file.
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (II) config/udev: 
Adding input device MOSART Semi. 2.4G Keyboard Mouse (/dev/input/event4)
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (**) MOSART Semi. 
2.4G Keyboard Mouse: Applying InputClass "evdev pointer catchall"
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (**) MOSART Semi. 
2.4G Keyboard Mouse: Applying InputClass "libinput pointer catchall"
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (II) Using input 
driver 'libinput' for 'MOSART Semi. 2.4G Keyboard Mouse'
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (II) systemd-logind: 
got fd for /dev/input/event4 13:68 fd 26 paused 1
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (II) systemd-logind: 
releasing fd for 13:68
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (II) config/udev: 
Adding input device MOSART Semi. 2.4G Keyboard Mouse (/dev/input/event7)
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (II) No input driver 
specified, ignoring this device.
Sep 11 07:59:43 TIS-PC /usr/lib/gdm3/gdm-x-session[1890]: (II) This device may 
have been added with another device file.
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 39 with keysym 39 (keycode 12).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 39 with keysym 39 (keycode 12).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
Sep 11 07:59:43 TIS-PC gnome-shell[3269]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
Sep 11 07:59:43 TIS-PC 

[Desktop-packages] [Bug 1895284] [NEW] Some issues...

2020-09-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Mozilla would not respond to closing windows. Took a long time to respond.
Screen could not be awoken after going to sleep. Stayed black. HD kept running.
Forced shut down. Rebooted fine. Launched Mozilla and it got stuck on program 
startup.
Forced shut down again. Reooted fne. Ran Xdiagnose. Got redirected here after 
bug reporting.
Mozilla works fine now!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: i386
CompositorRunning: None
Date: Fri Sep 11 12:48:35 2020
DistUpgraded: 2020-05-29 12:17:15,420 DEBUG /openCache(), new cache size 62484
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1043:14e2]
   Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1043:14e2]
InstallationDate: Installed on 2017-07-12 (1156 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: ASUSTeK Computer Inc. A8E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=8064a5cd-fa12-4277-a7b0-317979a30b37 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-05-29 (105 days ago)
dmi.bios.date: 03/24/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: A8E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr302:bd03/24/2008:svnASUSTeKComputerInc.:pnA8E:pvr1.0:rvnASUSTeKComputerInc.:rnA8E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: A8E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Aug 17 10:23:03 2018
xserver.configfile: default
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17476 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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


[Desktop-packages] [Bug 1894452] Re: shutdown delay because of cups

2020-09-11 Thread Till Kamppeter
I have released cups-filters 1.28.2 upstream yesterday:

https://openprinting.github.io/cups-filters-1.28.2-released/

It also got already uploaded into Debian and I will sync it to Ubuntu as
soon as it got processed at Debian.

** Changed in: cups-filters (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  shutdown delay because of cups

Status in cups-filters package in Ubuntu:
  In Progress

Bug description:
  Both my desktop and laptop running 20.10 have a 90 second delay
  shutting down (power off or restart).  Getting message;

  A stop job is Running for Make remote CUPS printers available locally

  After 90 seconds the shutdown continues to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups 2.3.3-2ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Sep  6 18:10:20 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  KernLog:
   
  Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
  MachineType: CLEVO CO. W35_37ET
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

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

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


[Desktop-packages] [Bug 997934]

2020-09-11 Thread Heiko-tietze-g
*** Bug 136303 has been marked as a duplicate of this bug. ***

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

Title:
  [Upstream]  Spell checking doesn't warn users if the selected
  dictionary isn't installed, but rather returns a potentially incorrect
  result

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  This has been the case since Beta 2.

  To reproduce:

  1) Type out a load of rubbish on the keyboard as well as a few correctly 
spelled words. I used "vmw;qbjk aoeuasnth aoeu house in the street"
  2) Press F7 to initiate the spell check.

  Actual Result: The spell check notifies the user of completion without any 
recognition of errors.
  Expected Result: The spell check should highlight each misspelled word and 
offer alternatives.

  WORKAROUND: Open the dash and run Language Support
  2) Under the 'Language' tab, choose another variant of English and drag it 
above the US English so it takes precedence.
  3) Click "Apply System-wide" and log out.

  On logging back in, spell check will work.

  Not reproducible in Xubuntu 32-bit.

  lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

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

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Fri May 11 08:53:51 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  ProcEnviron:
   LANGUAGE=en_IE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/997934/+subscriptions

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


[Desktop-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)

2020-09-11 Thread Till Kamppeter
*** This bug is a duplicate of bug 1894452 ***
https://bugs.launchpad.net/bugs/1894452

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

** This bug has been marked a duplicate of bug 1894452
   shutdown delay because of cups

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups-filters package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1894336] Re: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-k

2020-09-11 Thread Kai Kasurinen
*** This bug is a duplicate of bug 1768499 ***
https://bugs.launchpad.net/bugs/1768499

** This bug has been marked a duplicate of bug 1768499
   package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade:
  intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está
  también en el paquete nvidia-kernel-common-390
  390.138-0ubuntu0.20.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  instalando driver de nvidia-340, la ultima actualización tiene
  problemas de resolución gráfica

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep  4 20:56:57 2020
  ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', 
que está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1
  InstallationDate: Installed on 2020-05-12 (115 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: 
intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también 
en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1
  UpgradeStatus: Upgraded to focal on 2020-05-13 (114 days ago)

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

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


[Desktop-packages] [Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles

2020-09-11 Thread Pavel Zyukin
Same issue here.

Zyxel NAS326
Linux Mint 20

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

Title:
  gvfsd-afp consumes 100% of processor cycles

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Happens on an irregular basis on 12.04 and I think I've experienced it
  on 11.10.

  For no reason gvfsd-afp starts up. Cooling fan kicks in, system
  becomes laggy. Easily cured using system monitor and killing the
  process. Someone on the Ubuntu Forum asked if I have a Mac on the
  network and the answer is yes, an iMac and there are shares on that
  machine I can access.

  Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110

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

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


[Desktop-packages] [Bug 1894596] Re: Night Light stays on

2020-09-11 Thread Daniel van Vugt
The fix appears to be in mutter 3.36.7, but beware; it's not in 3.37
yet.

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1392
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1392

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

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

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

** Tags added: fixed-in-3.36.7 fixed-upstream

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

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

Title:
  Night Light stays on

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  I have "Night mode" set to turn on every day at 10pm and off at 6 am.
  However, at 6, the "Night mode" icon disappears but my screen remaine 
orangeish as when "Night mode" is on.
  Logging off and on again restores color temperature back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Sep  7 07:43:43 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (148 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1885744] Re: HIde im-config in application menus/searches

2020-09-11 Thread Gunnar Hjalmarsson
On 2020-09-11 07:36, gongbing wrote:
> It's reproduced on thor-T (ThinkPad T15p)

What is reproduced? This bug is closed.

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

Title:
  HIde im-config in application menus/searches

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Focal:
  Fix Released

Bug description:
  [Impact]

  I'm refering to this conversation:
  
https://discourse.ubuntu.com/t/improve-presentation-of-input-method-as-search-result-in-all-applications/17031/2

  Current situation:
  ===
  - Settings of im-config can be accomplished by "Language Support" ( see 
https://ubuntucommunity.s3.dualstack.us-east-2.amazonaws.com/original/2X/4/43cc792173e336454a8d38e3c35b950fbfb48975.png
 )
  - im-config is difficult to understand for "normal users"

  Suggestion:
  ===
  Hide im-config from application menu / searches

  [Test Case]

  * Open Activities and find that "Input Method" is found

  * Install im-config from focal-proposed

  * Open Activities and find that "Input Method" is no longer found

  [Regression Potential]

  Minimal; only a tiny change in the .desktop file.

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

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


[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-09-11 Thread dgoosens
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Hard to believe there is no kernel developer impacted by this issue...
Am about to have to buy a wired headset just to make calls on Teams.

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Desktop-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)

2020-09-11 Thread Martin
Those log files are from kernel 5.4.0; I had selected that kernel
manually in grub a while ago and didn't remember. Anyways, I just tested
this stuff again running the current 20.10 kernel (5.8.0-18-generic),
and the same thing happens there.

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] ProcCpuinfoMinimal.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409685/+files/ProcCpuinfoMinimal.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] UdevDb.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1895265/+attachment/5409689/+files/UdevDb.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] ProcInterrupts.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409687/+files/ProcInterrupts.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Lsusb-v.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409682/+files/Lsusb-v.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] acpidump.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409690/+files/acpidump.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] ProcEnviron.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409686/+files/ProcEnviron.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Lsusb-t.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409681/+files/Lsusb-t.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] ProcCpuinfo.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409684/+files/ProcCpuinfo.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] PrintingPackages.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409683/+files/PrintingPackages.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Lsusb.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1895265/+attachment/5409680/+files/Lsusb.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] ProcModules.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409688/+files/ProcModules.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] CurrentDmesg.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409674/+files/CurrentDmesg.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Lspci-vt.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409679/+files/Lspci-vt.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Lspci.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1895265/+attachment/5409678/+files/Lspci.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Locale.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1895265/+attachment/5409677/+files/Locale.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Dependencies.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409675/+files/Dependencies.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] KernLog.txt

2020-09-11 Thread Martin
apport information

** Attachment added: "KernLog.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409676/+files/KernLog.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-11-26 (289 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat:
   device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
   device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
   device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
  MachineType: Dell Inc. XPS 15 9575
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  wayland-session groovy
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)

2020-09-11 Thread Martin
apport information

** Tags added: apport-collected groovy wayland-session

** Description changed:

  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a
  SIGTERM signal.
  
  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:
  
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root
  
  As you can see, I run the command at 10:17:26, then nothing happens for
  90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56.
  
- This problem hangs shutdown for 90 seconds, so it quite badly affects
- the user experience of Ubuntu as a whole, even for users who never use
- cups.
+ This problem hangs shutdown for 90 seconds, so it quite badly affects the 
user experience of Ubuntu as a whole, even for users who never use cups.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu45
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2019-11-26 (289 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Lpstat:
+  device for EPSON_XP_312_313_315_Series_2_ms_jgb_air: ///dev/null
+  device for HP_Color_LaserJet_MFP_M477fdw_0E34F7_: 
implicitclass://HP_Color_LaserJet_MFP_M477fdw_0E34F7_/
+  device for Samsung_CLX_3300_Series_Heidi_MacBook_Pro: ///dev/null
+ MachineType: Dell Inc. XPS 15 9575
+ Package: cups 2.3.3-3ubuntu1
+ PackageArchitecture: amd64
+ Papersize: a4
+ PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw_0E34F7_.ppd: 
Permission denied
+ ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60c00fb1-a65f-4908-898e-0cd30e291b96 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ Tags:  wayland-session groovy
+ Uname: Linux 5.4.0-42-generic x86_64
+ UpgradeStatus: Upgraded to groovy on 2020-09-09 (1 days ago)
+ UserGroups: adm cdrom dialout dip disk docker lpadmin lxd plugdev sambashare 
sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 05/25/2020
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.12.1
+ dmi.board.name: 0C32VW
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd05/25/2020:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 15 9575
+ dmi.product.sku: 080D
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/bugs/1895265/+attachment/5409673/+files/CupsErrorLog.txt

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user 

[Desktop-packages] [Bug 1895265] [NEW] cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)

2020-09-11 Thread Martin
Public bug reported:

The cups-browsed service fails to exit when systemd tries to stop it,
seemingly because /usr/sbin/cups-browsed fails to exit when it's sent a
SIGTERM signal.

Here are all the relevant logs in journald when trying to stop cups-
browsed using `sudo systemctl stop cups-browsed`:

Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

As you can see, I run the command at 10:17:26, then nothing happens for
90 seconds, until systemd gives up and sents a SIGKILL at 10:18:56.

This problem hangs shutdown for 90 seconds, so it quite badly affects
the user experience of Ubuntu as a whole, even for users who never use
cups.

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

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects
  the user experience of Ubuntu as a whole, even for users who never use
  cups.

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

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


[Desktop-packages] [Bug 1895265] Re: cups-browsed fails to exit when systemd tries to shut it down (SIGTERM)

2020-09-11 Thread Martin
Sorry, I forgot to mention that this issue affects cups-browsed 1.28.1-1
from Ubuntu 20.10 Groovy.

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

Title:
  cups-browsed fails to exit when systemd tries to shut it down
  (SIGTERM)

Status in cups package in Ubuntu:
  New

Bug description:
  The cups-browsed service fails to exit when systemd tries to stop it,
  seemingly because /usr/sbin/cups-browsed fails to exit when it's sent
  a SIGTERM signal.

  Here are all the relevant logs in journald when trying to stop cups-
  browsed using `sudo systemctl stop cups-browsed`:

  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Sep 11 10:17:26 ubun sudo[3370]:   martin : TTY=pts/2 ; PWD=/home/martin ; 
USER=root ; COMMAND=/usr/bin/systemctl stop cups-browsed
  Sep 11 10:17:26 ubun sudo[3370]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Sep 11 10:17:26 ubun systemd[1]: Stopping Make remote CUPS printers available 
locally...
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: State 'stop-sigterm' 
timed out. Killing.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1471 
(cups-browsed) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Killing process 1521 
(gdbus) with signal SIGKILL.
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=9/KILL
  Sep 11 10:18:56 ubun systemd[1]: cups-browsed.service: Failed with result 
'timeout'.
  Sep 11 10:18:56 ubun systemd[1]: Stopped Make remote CUPS printers available 
locally.
  Sep 11 10:18:56 ubun sudo[3370]: pam_unix(sudo:session): session closed for 
user root

  As you can see, I run the command at 10:17:26, then nothing happens
  for 90 seconds, until systemd gives up and sents a SIGKILL at
  10:18:56.

  This problem hangs shutdown for 90 seconds, so it quite badly affects
  the user experience of Ubuntu as a whole, even for users who never use
  cups.

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

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


[Desktop-packages] [Bug 1895262] [NEW] Installer windows do not fit on screen, when live-CD only boots with 800x600 screen resolution

2020-09-11 Thread Karl Kastner
Public bug reported:

I recently got a new laptop, ThinkPad E14 G2 with AMD Ryzen 7 4700U with
Radeon Graphics. The live-system boots only with a screen resolution of
800x600, which cannot be increased. The problem is that the windows of
the installer do not fit the screen so that the buttons for "cancel",
"back" and, most importantly, "continue" are not visible on the screen.
Thus any novice trying to install Ubuntu/Linux on a recent laptop with
AMD hardware will surely despair and be turned off from using
Ubuntu/Linux. I suggest that the windows of the installer get a scroll
bar to make it feasible to install Ubuntu in such cases.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-desktop (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 11 16:01:52 2020
InstallationDate: Installed on 2015-11-05 (1771 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to focal on 2020-09-10 (0 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Installer windows do not fit on screen, when live-CD only boots with
  800x600 screen resolution

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I recently got a new laptop, ThinkPad E14 G2 with AMD Ryzen 7 4700U
  with Radeon Graphics. The live-system boots only with a screen
  resolution of 800x600, which cannot be increased. The problem is that
  the windows of the installer do not fit the screen so that the buttons
  for "cancel", "back" and, most importantly, "continue" are not visible
  on the screen. Thus any novice trying to install Ubuntu/Linux on a
  recent laptop with AMD hardware will surely despair and be turned off
  from using Ubuntu/Linux. I suggest that the windows of the installer
  get a scroll bar to make it feasible to install Ubuntu in such cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 11 16:01:52 2020
  InstallationDate: Installed on 2015-11-05 (1771 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-09-10 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024

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

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


[Desktop-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2020-09-11 Thread valentin cozma
Wait, there's more

If I do multiple CTRL-z + Enter in gnome-calculator, the CPU goes HIGHER
, and it stays there until ANY action is made ( either opening an app (
mouse or kbd shortcut, doesn't matter ) , or switch window by alt-tab or
mouse )


Seems like an ibus (big?) problem .

Also seems ibus is running on multiple processes/cores ( and hangs on
all of them in the end ) , is this intended ?

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

Title:
  ibus-* randomly use high CPU

Status in GNOME Shell:
  Unknown
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Opinion
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2020-09-11 Thread valentin cozma
Just after finished previous comment, gnome-calculator crashed ( most
probably related to CTRL-z ) .

>From syslog :

Sep 11 10:44:58 valyelitebook kernel: [1645692.175240] traps: 
gnome-calculato[9355] trap int3 ip:7f302aceeea1 sp:7ffca1a8ae90 error:0 in 
libglib-2.0.so.0.5600.4[7f302ac9d000+114000]
Sep 11 10:44:58 valyelitebook systemd[1]: Started Process Core Dump (PID 
13784/UID 0).
Sep 11 10:44:58 valyelitebook systemd-coredump[13785]: Process 9355 
(gnome-calculato) of user 1002 dumped core.#012#012Stack trace of thread 
9355:#012#0  0x7f302aceeea1 n/a (libglib-2.0.so.0)#012#1  
0x7f302acf1819 g_log_writer_default (libglib-2.0.so.0)#012#2  
0x7f302acefa8e g_log_structured_array (libglib-2.0.so.0)#012#3  
0x7f302acf04ce g_log_structured_standard (libglib-2.0.so.0)#012#4  
0x7f3029eabc41 n/a (libgdk-3.so.0)#012#5  0x7f3029eb8ac3 n/a 
(libgdk-3.so.0)#012#6  0x7f30279068fa _XError (libX11.so.6)#012#7  
0x7f302790382b n/a (libX11.so.6)#012#8  0x7f30279038d5 n/a 
(libX11.so.6)#012#9  0x7f3027904830 _XReply (libX11.so.6)#012#10 
0x7f30276ba004 XIGetClientPointer (libXi.so.6)#012#11 0x7f3029ea7030 
n/a (libgdk-3.so.0)#012#12 0x7f3029ea85a4 n/a (libgdk-3.so.0)#012#13 
0x7f3029eb3810 n/a (libgdk-3.so.0)#012#14 0x7f3029eb3329 n/a 
(libgdk-3.so.0)#012#15 0x7f3029e7dd70 gdk_display_get_event 
(libgdk-3.so.0)#012#16 0x7f3029eb2f82 n/a (libgdk-3.so.0)#012#17 
0x7f302ace9417 g_main_context_dispatch (libglib-2.0.so.0)#012#18 
0x7f302ace9650 n/a (libglib-2.0.so.0)#012#19 0x7f302ace96dc 
g_main_context_iteration (libglib-2.0.so.0)#012#20 0x7f3029928efd 
g_application_run (libgio-2.0.so.0)#012#21 0x5613cd84fbd3 n/a 
(gnome-calculator)#012#22 0x7f30286c9b97 __libc_start_main 
(libc.so.6)#012#23 0x5613cd84de3a n/a (gnome-calculator)#012#012Stack trace 
of thread 9358:#012#0  0x7f30287bccf9 __GI___poll (libc.so.6)#012#1  
0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2  0x7f302ace96dc 
g_main_context_iteration (libglib-2.0.so.0)#012#3  0x7f30173bc36d n/a 
(libdconfsettings.so)#012#4  0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5  
0x7f302821e6db start_thread (libpthread.so.0)#012#6  0x7f30287c9a3f 
__clone (libc.so.6)#012#012Stack trace of thread 9356:#012#0  
0x7f30287bccf9 __GI___poll (libc.so.6)#012#1  0x7f302ace95c9 n/a 
(libglib-2.0.so.0)#012#2  0x7f302ace96dc g_main_context_iteration 
(libglib-2.0.so.0)#012#3  0x7f302ace9721 n/a (libglib-2.0.so.0)#012#4  
0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5  0x7f302821e6db 
start_thread (libpthread.so.0)#012#6  0x7f30287c9a3f __clone 
(libc.so.6)#012#012Stack trace of thread 9357:#012#0  0x7f30287bccf9 
__GI___poll (libc.so.6)#012#1  0x7f302ace95c9 n/a (libglib-2.0.so.0)#012#2  
0x7f302ace9962 g_main_loop_run (libglib-2.0.so.0)#012#3  0x7f3029955276 
n/a (libgio-2.0.so.0)#012#4  0x7f302ad11175 n/a (libglib-2.0.so.0)#012#5  
0x7f302821e6db start_thread (libpthread.so.0)#012#6  0x7f30287c9a3f 
__clone (libc.so.6)

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

Title:
  ibus-* randomly use high CPU

Status in GNOME Shell:
  Unknown
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Opinion
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1895135] Re: GFS Didot Classic Wrong Glyphs in Writer

2020-09-11 Thread Beluga
Lubuntu needs to switch away from defaulting to qt5. According to
LibreOffice developers, "using plain "qt5" VCL plugin in production is
something we don't recommend". Even the readme says it's "under
construction": https://docs.libreoffice.org/vcl.html

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

Title:
  GFS Didot Classic Wrong Glyphs in Writer

Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice Writer 6.4.5.2 on Lubuntu 20.04 displays wrong glyphs for
  GFS Didot Classic that look identical to those of GFS Artemisia.

  This bug doesn't occur if I start Libreoffice from command line with
  this option: SAL_USE_VCLPLUGIN=gen libreoffice

  Also see here:
  https://bugs.documentfoundation.org/show_bug.cgi?id=133049

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

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


[Desktop-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2020-09-11 Thread valentin cozma
Hi,

I'm using Mint 19.2 , I noticed if I do CTRL-z ( undo ) either in xed or
gnome-calc , this will trigger high usage in ibus-daemon, ibus-x11 and
xed

However, in pluma it does not .

After some seconds the CPU goes down . I noticed it in the CPU monitor
applet .


100% reproductible .

xed is 2.2.3+tina
gnome-calculator is 1:3.28.2 ~ubuntu 18.04.3
ibus is 1.5.17-3ubuntu5.3


pluma is 1.20.1-3ubuntu1


lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description:Linux Mint 19.2 Tina
Release:19.2
Codename:   tina


uname -a
Linux valyelitebook 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux


Hope it helps, it's really frustrating , and I think it affects more 
applications

( Idea IDE and Android Studio also have strange behaviours - they did
not on 18.x )

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

Title:
  ibus-* randomly use high CPU

Status in GNOME Shell:
  Unknown
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Opinion
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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